The "resolved" status and the UX workflow...

[Tony Atkins]

Hi, All:

I wanted to follow up on a second discussion point around the use of the
"resolved" field on issues.gpii.net, which came up in last night's
meeting.  In reviewing the use of the "resolved" status in the GPII
project, I discovered what I consider to be another problem.  The UX
project allows transitioning to "resolved" without requiring a resolution:

https://issues.gpii.net/issues/?jql=project%3DUX%20and%20status%3Dresolved%20and%20resolution%20is%20empty

Although the open and flexible nature of the workflow (see attached) makes
it difficult to confirm the "end points" of the process, it seems like
"Resolved" and then "Done" are the expected destination for most issues.
In any case, the point is that when an issue reaches a state where there is
an outcome, it should be clear what the outcome is.

This is important so that everyone, from the reporter to the parties
involved can see that a decision was taken and what that decision was.   An
issue that has been closed with the resolution "Fixed" is obviously very
different than an issue that has been closed with the resolution "Won't
Fix".   As it stands, there is no indication of the outcome, at least for a
small group of issues.

As far as I can see, to change this, I would simply need to update a few
workflow transitions and screens to require the "resolution" field when
transitioning UX issues to the "Resolved" state.  I am perfectly willing to
take care of this, but wanted to review with Bern and the larger group
first.

Please comment.  I will not take any action until I've at least heard from
Bern.

Cheers,



Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20170209/48cc6d0d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-02-09 at 11.03.53 AM.png
Type: image/png
Size: 70777 bytes
Desc: not available
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20170209/48cc6d0d/attachment.png>