#3003: milestone could be a ticket
---------------------------+------------------------------------------------
Reporter: ThurnerRupert | Owner: jonas
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: timeline | Version: 0.9.4
Severity: normal | Keywords:
---------------------------+------------------------------------------------
can milestones be implemented as tickets too, just by marking a ticket as
milestone? a milestone can depend on other milestones, they can be in
parallel, they have a responsible, they have an importance, and they
depend on the completion of tickets.
currently the milestone concept has a few weaknesses:
* changes are not tracked
* no responsible
* no dependencies (or just implicit by setting dates)
* consolidated view over multiple trac instances, i.e. have a big
milestone consisting of small ones stored in other trac instances.
mark a ticket as a milestone, intertrac, and ticket dependencies would
solve 95% of these issues. do you see any disadvantage in doing this?
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/3003>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
