#121 Task Heirarchy

Chris J

Each task should be able to "sprout" children tasks for
related events. Eg PC fault requires ends up with new
PC purchase required, new installation and software
purchase. Installation and purchases could be subtasks
allowing the reassignmnet of particular parts of a
"fix" to staff with differing roles.

Each task would need two extra fields: parent and
children. The parent task would link back to the job
it was created from. The children would be all the
tasks this current task has invoked. A new button on
each task screen would allow creation of a new child
task with the parent ID already filled in. A task with
children defined would have a list of links to each
child task or a single button to open all child tasks
on the same page.

We currently just create new unlinked tasks for this
but it would be nice to have some structure to it so
that we can see which staff are creating the most work.
At the moment a member of staff can make one request
which results in us having to create multiple extra
requests none of which are attributable to them.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks