Tasks
Page: 1, 2
Recent posts in this topic
Hi,
Just a quick suggestion:
Would it be possible to allow a title and description for each task item? Currently, the description is shown as the task, and this is annoying as it means I'm unable to write more detailed tasks.
If you were to implement this, I'd suggest that you show the title for each task item, and would show the description when the title is clicked.
Alternatively, have a task linked to a message - this would allow comments for each task, but the message would need to be hidden from the main Messages area.
Hope that makes sense!
Just a quick suggestion:
Would it be possible to allow a title and description for each task item? Currently, the description is shown as the task, and this is annoying as it means I'm unable to write more detailed tasks.
If you were to implement this, I'd suggest that you show the title for each task item, and would show the description when the title is clicked.
Alternatively, have a task linked to a message - this would allow comments for each task, but the message would need to be hidden from the main Messages area.
Hope that makes sense!
As far as I remember there was a discussion about sub-tasks somewhere in the forum *sorry no link*
IMHO your request will make aC more complicated. Why don't you create a task list for each major topic and add this to a milestone? There you can add messages too or add a more detailed description / resources for the task list (even I support the linking of task lists to messaged without the need of a milestone but this will be in the future ...).
For the single task there is enough room to enter a very detailed task description.
Did I miss something?
IMHO your request will make aC more complicated. Why don't you create a task list for each major topic and add this to a milestone? There you can add messages too or add a more detailed description / resources for the task list (even I support the linking of task lists to messaged without the need of a milestone but this will be in the future ...).
For the single task there is enough room to enter a very detailed task description.
Did I miss something?
Hi Rolando,
Here's how I imagine it:
Task List --> Task Item (task title, task description)
I don't think this would complicate things, as it's basically just adding another field (description) to the task item.
Alternatively, when creating a task item, choose from a drop-down box a message to associate that item with; similar to linking a task list to a milestone.
Hope that makes sense - the idea shouldn't complicate things, so I thought I'd try and explain it again in case it came across as too complicated.
Nick
Here's how I imagine it:
Task List --> Task Item (task title, task description)
I don't think this would complicate things, as it's basically just adding another field (description) to the task item.
Alternatively, when creating a task item, choose from a drop-down box a message to associate that item with; similar to linking a task list to a milestone.
Hope that makes sense - the idea shouldn't complicate things, so I thought I'd try and explain it again in case it came across as too complicated.
Nick
Hi Nick,
ok, I understand but have another opinion. In my opinion you don't need a second DB / description field when using tasks as the smallest item to work on (think about a sheet of paper when doing to-do lists; a task should be doable in a small amount of time like hours or 1-2 days).
If you need a description to add some information - or sub-tasks - then you don't have the workable items on the lowest level. As far as I see you can have the same functionality using the current setup (your wording from above in brackets):
milestone (tasks list) --> task list (task) *w/ associated messages when needed* --> task (description)
The single task can be described with lot of characters in the field. If you need more you might think about splitting that task in more than one.
Can this work for you? If yes, we can keep aC as simple as possible.
Cheers
Roland
PS: What I would like to see is a simple way to set dependencies/linking between milestones to structure the project (a new feature).
ok, I understand but have another opinion. In my opinion you don't need a second DB / description field when using tasks as the smallest item to work on (think about a sheet of paper when doing to-do lists; a task should be doable in a small amount of time like hours or 1-2 days).
If you need a description to add some information - or sub-tasks - then you don't have the workable items on the lowest level. As far as I see you can have the same functionality using the current setup (your wording from above in brackets):
milestone (tasks list) --> task list (task) *w/ associated messages when needed* --> task (description)
The single task can be described with lot of characters in the field. If you need more you might think about splitting that task in more than one.
Can this work for you? If yes, we can keep aC as simple as possible.
Cheers
Roland
PS: What I would like to see is a simple way to set dependencies/linking between milestones to structure the project (a new feature).
Hi Rolando,
Yes, that makes perfect sense :)
You're right about breaking one task up into multiple tasks, but I was really thinking about _describing_ that task - for example, instead of:
Task: Fix bug which occurs on X page under Y conditions
Have:
Task: Bug (short descriptive name) --link-to--> message #1 (full description).
Basically to allow task lists to have short titles, but to link to further information. Although a task might be small, the information which it represents may not necessarily be short enough to fit on the task line.
I hope that makes sense - I'm really just thinking out loud, so I appreciate your opinions :)
Milestone dependencies would be an excellent addition -- hasn't someone already requested this here?
EDIT: Doesn't this forum support Textile formatting?
Yes, that makes perfect sense :)
You're right about breaking one task up into multiple tasks, but I was really thinking about _describing_ that task - for example, instead of:
Task: Fix bug which occurs on X page under Y conditions
Have:
Task: Bug (short descriptive name) --link-to--> message #1 (full description).
Basically to allow task lists to have short titles, but to link to further information. Although a task might be small, the information which it represents may not necessarily be short enough to fit on the task line.
I hope that makes sense - I'm really just thinking out loud, so I appreciate your opinions :)
Milestone dependencies would be an excellent addition -- hasn't someone already requested this here?
EDIT: Doesn't this forum support Textile formatting?
Staff
Ilija Studen
on Dec 1. 2006. 8:14 pm
Description field will be added as part of tasks section reconstruction. It will be optional, but there will be no limit on amount of text that can be entered. In list only title will be displayed with link to task details page (description, comment and attachments for a given task will be shown on this page).
activeCollab Team Member
Staff
Ilija Studen
on Dec 1. 2006. 8:24 pm
That is exactly what *I* need and I was there first :p Just kidding of course.
This set of features will be added to support people who need ability to track issues (bug reports, complex tasks that required discussion, tasks that require screenshot to describe a behavior or problem etc). It makes things a bit more complicated, but if executed properly it can be made so it actually stays out of users way and can be used when such thing is required.
It is planned for 0.7.5.
This set of features will be added to support people who need ability to track issues (bug reports, complex tasks that required discussion, tasks that require screenshot to describe a behavior or problem etc). It makes things a bit more complicated, but if executed properly it can be made so it actually stays out of users way and can be used when such thing is required.
It is planned for 0.7.5.
activeCollab Team Member
Topic is locked. If you have something important to say about issues discussed on this page please write at hi@a51dev.com.
