Projects, milestones, tickets improvement
|Reported by:||Owned by:|
I've had a look at the proposals for sub-tickets, or sub-milestones & thought it might be an idea to put down on paper (so to speak) some ideas that I've come up with to solve these issues.
Basically, the way I see it, if it was possible to have sub-tickets, then milestones just become a special case of having a parent ticket. Also, if a ticket was classified as a milestone, then milestones could have sub-milestones.
Also, it'd be possible to group milestones into a per project, or even a per component basis. Whatever a user chose.
My theory is that the status for a project, milestone & ticket could be specified separately. To clarify: a "project" would have a selection of statuses that applied only to projects (discussions, spec'ing, in progress, complete) etc, and milestones would also have their own as well as tickets having their own.
So, to simplify:
Projects could contain milestones, and would have their own statuses; Milestones could contain milestones o&/or tickets, and have their own statuses; Tickets would remain as they are, except they could also have sub-tickets.
It's basically an enhancement of the current ticketing system to support sub-tickets, as well as different types of tickets. Special types (ie. projects & milestones) would have some other metadata that allows the current displays in the Roadmap.
In addition, some of the changes mentioned in GenericTrac could be done by using different views or the ticket changes (ie. history & discussion).
Just throwing it out there, maybe it'll land on fertile ground. Unfortunately I don't know Python, so can't work on it myself.