Re: [feature] update note log

I think the dependencies are more for prerequisites then they are for
tracking the granular parts of a task. I have tried using them like
this and the interface doesnt tie them together well enough for this
to be effective.

The TODO list would be more of a personal organization tool instead of
something that would be used in the overall scope of the bug tracking.
However you could use this data to do effective time tracking, create
gantt, charts etc. (all of which I vote should be exceptions)

Thanks

On Sat, May 12, 2012 at 1:39 PM, Murugan <katir@...> wrote:
> Ok I will try the dependency option for some sub tasks, but really, Scott,
> you nailed it here.  For "minute" to do's right now I feel "stuck"  Brian's
> idea would solve it.
>
> Yesterday, I spent a day working on a new site area and got it 99% done,  I
> don't want to have to create new tasks for little things like "update the
> urls for PDF downloads on the visit and faq pages" "set the call-to-action
> link destination on the home page when team decides where it should go" i.e.
> I just have to edit three "a href"'s on three pages... to create a task for
> this, even as a sub task of a "meta task" seems way over kill.
>
>
> On Saturday, May 12, 2012 7:49:59 AM UTC-10, Scott H wrote:
>>
>> Well FS does dependency tasks, so i can make a task A and then make Task B
>> and tell task A depends on B which is basically a subtask now. I think what
>> we would really like is a way to have a task log where when a user updates
>> the progress he/she can specify what they have done without having to put in
>> a comment or edit that task. Brian had the idea of allows a task have a
>> simple todo type list that can be checked off as the progress happens. I
>> know when i make a task its basically like, 'put in sliders instead of text
>> fields', this is broad because i have about x pages to do this task on. I
>> dont want to make x tasks but a todo list for this task would be awesome.
>>
>> On Saturday, May 12, 2012 7:26:38 AM UTC-6, Julien N wrote:
>>>
>>> What I did on another tracker, but I think it would work on FS is
>>> creating meta tasks clearly identified that depend on several other tasks.
>>> This meta task lists in its description the various tasks it contains and as
>>> those tasks are closed, the tasks in that list are striked through
>>> automatically (this feature already exist).
>>> So the developer (or whatever user) always start from the metatask he
>>> wants to work on and just follow the links of the subtasks.
>>>
>>>
>>>
>>>
>>> On Fri, May 11, 2012 at 9:19 PM, Murugan <katir@...> wrote:
>>>>
>>>> I also struggle with the level of granularity of tasks. Do you make
>>>> multitude of small tasks? if so how do you aggregate them? I do this
>>>> sometimes now and put a keyword at the beginning of the Summary (Title?)  of
>>>> the task, so then you can sort the tasks and they appear together
>>>>
>>>> But I found that having too many "small" tasks becomes an issue as users
>>>> "go blind" seeing the long lists...things get missed easily. Now I tend to
>>>> define a task as mini-project within a project and then in the main
>>>> description field I'll make a list of todo's keep editing this, put "DONE:
>>>> on front of some and move them to the bottom, that kind of thing. this way
>>>> the assignee only has to think of logging in and finding 1 or two tasks and
>>>> then his TODO lists is in the description field
>>>>
>>>> So, yes, any better approach to this will be useful (someday)
>>>>
>>>>
>>>>
>>>>
>>>> On Wednesday, May 9, 2012 12:57:42 PM UTC-10, Bryan T wrote:
>>>>>
>>>>> I was thinking, that instead of having just a raw percentage change
>>>>> for the progress bar. Maybe it could be done either combined with a
>>>>> comment or just a quick note. So you can then list out the history of
>>>>> a task and see that it was
>>>>>
>>>>> 25% done at xx/xx/xxxx xx:xx:xx by btong "installed webserver".
>>>>> 40% done at xx/xx/xxxx xx:xx:xx by btong "imported source code".
>>>>> 75% done at xx/xx/xxxx xx:xx:xx by btong "configured stuff".
>>>>>
>>>>> It would also be cool to maybe combine this with maybe a todo list
>>>>> that is part of a task. I know that I have always been torn to
>>>>> granularize tasks vs having one that takes longer. I think having
>>>>> TODO's would make it a bit more granular. And then with the todo items
>>>>> we could eventually do some kind of gantt chart generation based on
>>>>> the project data.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Wed, May 9, 2012 at 4:53 PM, Scott H <scott.harpster@...>
>>>>> wrote:
>>>>> > I have another idea. I seem to update my tasks, such as percentage
>>>>> > changes
>>>>> > etc...it could be cool to add another tab on the comments,
>>>>> > notifications box
>>>>> > an update box that allows the updater to add update notes on maybe
>>>>> > whats
>>>>> > been worked on in the progress....thoughts? It might look nice after
>>>>> > that UI
>>>>> > gap is fixed up.
>>>>> >
>>>>> > --
>>>>> > You received this message because you are subscribed to the Google
>>>>> > Groups
>>>>> > "flyspray" group.
>>>>> > To view this discussion on the web visit
>>>>> > https://groups.google.com/d/msg/flyspray/-/xbIl6ZfQfMkJ.
>>>>> > To post to this group, send email to flyspray@...
>>>>> > To unsubscribe from this group, send email to
>>>>> > flyspray+unsubscribe@...
>>>>> > For more options, visit this group at
>>>>> > http://groups.google.com/group/flyspray?hl=en.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --------------------
>>>>> Bryan Tong
>>>>> Nullivex LLC | eSited LLC
>>>>> (507) 298-1624
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "flyspray" group.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msg/flyspray/-/oZ2_ibEaf5oJ.
>>>>
>>>> To post to this group, send email to flyspray@...
>>>> To unsubscribe from this group, send email to
>>>> flyspray+unsubscribe@...
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/flyspray?hl=en.
>>>
>>>
> --
> You received this message because you are subscribed to the Google Groups
> "flyspray" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/flyspray/-/RqMeTbr5qykJ.
>
> To post to this group, send email to flyspray@...
> To unsubscribe from this group, send email to
> flyspray+unsubscribe@...
> For more options, visit this group at
> http://groups.google.com/group/flyspray?hl=en.

-- 
--------------------
Bryan Tong
Nullivex LLC | eSited LLC
(507) 298-1624

--

-- 
You received this message because you are subscribed to the Google Groups "flyspray" group.
To post to this group, send email to flyspray@...
To unsubscribe from this group, send email to flyspray+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/flyspray?hl=en.