#1689: Correct TracTickets diagram (reassign -> new)
----------------------------------+-----------------------------------------
Reporter: anonymous | Owner: jonas
Type: defect | Status: closed
Priority: low | Milestone: 0.10
Component: wiki | Version: 0.8.4
Severity: normal | Resolution: fixed
Keywords: documentation review |
----------------------------------+-----------------------------------------
Changes (by cboos):
* resolution: => fixed
* status: new => closed
Comment:
The proposed diagram is more correct, I'm not sure it's less confusing
though,
because of the "assigned -> (reassign) -> new" transition, which
seems at first counter-intuitive. But that's not the diagram's fault.
This is because "assigned" state would have been better named "accepted",
as the transition "new -> (accept) -> assigned" suggests.
Also the "assigned" and "reopened" states are different ones,
and the transition "new -> (reassign) -> new" is still missing.
See also the related discussion about accept/assigned/accepted on #2045.
In milestone:0.11, with the WorkFlow merge, we will probably pick a
better/clearer default scheme (at least rename "assigned" to "accepted").
But the particular (reassign -> new) issue that this ticket wanted to
address is fixed, yes.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/1689>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
