[Topic] More levels of sub-tasks

I have been pondering the idea of allowing more levels of sub-tasks to be created. For example, right now, a task can have sub-tasks, but sub-tasks themselves cannot have subtasks. Technically, sub-tasks can be associated to any depth, but the interface doesn't facilitate it.

Imagine having a story which has some sub-tasks. Then imagine that you want to define some test cases for those sub-tasks. Right now, the interface would prevent that.

I'd be interested in knowing if others would find it useful to be able to create deeper trees of sub-tasks. Any thoughts?

—Posted by Adam Lane on Jan 30, 2007
Forum
AgileTrack Client
Reply

I think it'd be useful. you're right about the interface. it's clumsy when it comes to support sub-tasks. I think it's possible to add a view or two to make it easy browse and watch sub-tasks.

I think the biggest problem right now is that issues list is separated from the issue details. I have to click several times to select an issue, then click back on the list, etc. too much clicking and information is disconnected for me. it would be helpful to support a view that shows list of issues and current issue details together.

for example, you could add a view you that splits the screen between a tree on one side (I prefer on the left) and details for the selected task on the other side.

see http://www.codeproject.com/tools/todolist2.asp for an example of what I'm talking about.

—Posted by slava on Feb 20, 2007 at 4:36:41 PM


You may post a reply to this topic, but you must be logged in. If you already have an account, you may login now. If you need to create an account, you may also register now.