With the introduction of the workflow feature in 0.19.0, there have
been a number of bug reports on the feature. I was planning to address
these as follows:
1) Re-introduce "re-open" as a separate entity in terms of
configuration. The current workflow implementation treats re-open and
feedback (or what ever status is used for reopening issues) as the same
thing. The workflow definition could exclude the re-open arcs (these
would be hidden paths from any state between the "resolved" (as defined
in the config) and closed to the re-open status). I would also bring
back the re-open button.
2) Arcs from a status to itself are redundant and won't need to be in
the workflow. The current status won't be shown in the list under the
"Change Status To:" button. It will be the default under the
3) A workflow checker is needed, as it is possible to mis-capture the
workflow to end up with status' without a way into or out of them. I
was planning to add this to admin/check.php, but this still doesn't
guarantee that the workflow will be checked or functional. When a
status is missing, the next status' will default to any other status.
4) The "allow_reporter_reopen" and "allow_reporter_close" will override
the access rights settings in "set_status_threshold". (This is mostly
Comments are welcome.
Altera Ottawa Technology Center
Phone: (613) 591-6702 Email: ghenshaw@...
Get latest updates about Open Source Projects, Conferences and News.