refresher on status/resoulution workflow in jira

Justin Obara obara.justin at gmail.com
Mon Sep 16 10:01:13 EDT 2013


This is a simple refresher on how to use the jira status/resolution workflow in the fluid issue tracker http://issues.fluidproject.org


1) Create a jira

Initially it will be open and unresolved. You can assign the jira to someone in particular or leave it unassigned.


2) Starting work

Assign the issue to yourself and start progress. This will let others know that you are working on it.


3) Stop work - not complete

If you are no longer working on an issue and it hasn't been resolved, stop progress. You may also wish to unassign yourself. Also, leave a comment(s) with all of the relevant information you have collected along the way.


4) Stop work - pull request

If you have completed the work and submitted a pull request, change the status to Needs Commit and put a link to the pull request in the comments.


5) Work complete - resolved

Should only be marked when the work is complete (e.g. pull request merged into the project repo). However, this signifies that there is something more to be done, such as more testing or verification. Please leave a detailed comment about what is left and why it was resolved. If a pull request was merged, leave a comment detailing the revision it was merged in at. 


6) Work complete - closed

After all the work is complete (e.g. pull request merged into the project repo), mark the issue as closed. If a pull request was merged, leave a comment detailing the revision it was merged in at. Ensure that the fix for version is set to the upcoming release.


Thanks
Justin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20130916/f74ea162/attachment.html>


More information about the fluid-work mailing list