Testing new CHEF ticket workflow


#1

The CHEF project on JIRA is using a new workflow that we’re planning on
using for most of our projects. We’ve gotten rid of the “Triaged” / “Code
Reviewed” custom field and instead created a true JIRA workflow that
progresses like so:

Open -> Confirmed -> [In Progress] -> Fix Provided -> [Reopened] -> Fix
Reviewed -> Fix Committed -> Closed.

The first new field is “Confirmed” and is intended for members of the
community to be able to review tickets, reproduce them, and mark them as
reproducible. This provides a great way for those who aren’t comfortable
providing patches to put their experience to use identifying the signal
from the noise in the ticketing system so that those who want to write
patches can more easily find tickets to work on.

“In progress” is an existing optional step that can be used to signal to
others that you are working on providing a fix for this issue.

“Fix Provided” replaces the former resolved status. When you provide a fix
you click “Fix Provided” and then it goes into a queue for the code review
meetings. If that team has feed back for you they will add it as a comment
and reopen the ticket. When you’re ready to have the code review team look
at your patch again, you simply click “Fix Provided” again to get it back
in the queue.

“Fix Reviewed” replaces the old custom field check box that was most
recently “Code Reviewed”. This step is much easier to search for and
easier to tell where that issue is in the workflow.

“Fix Committed” is the state the ticket will be in after Opscode merges
the fix into the code repository.

Ideally “Closed” will become “Fix Released” but I need to work with JIRA
more to see if I can trigger this.

Component is now a shorter list and required for filing a ticket. If you
don’t know you can just pick something, but it’s really helpful to know
what the ticket is against so the right resources can work on the issue.


Bryan McLellan | opscode | technical program manager, open source
© 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org

P.S. The mixlib and knife plugin projects on JIRA will soon be
consolidating into a single MIXLIB and KNIFE project respectively with
components to differentiate the separate libraries or plugins.


#2

Hurray! Thanks Bryan for explaining the procedure.

Excited to see this in action. Are there any shared Jira filters for these
states yet?

-Mike

On Tue, Nov 6, 2012 at 6:04 PM, Bryan McLellan btm@opscode.com wrote:

The CHEF project on JIRA is using a new workflow that we’re planning on
using for most of our projects. We’ve gotten rid of the “Triaged” / “Code
Reviewed” custom field and instead created a true JIRA workflow that
progresses like so:

Open -> Confirmed -> [In Progress] -> Fix Provided -> [Reopened] -> Fix
Reviewed -> Fix Committed -> Closed.

The first new field is “Confirmed” and is intended for members of the
community to be able to review tickets, reproduce them, and mark them as
reproducible. This provides a great way for those who aren’t comfortable
providing patches to put their experience to use identifying the signal
from the noise in the ticketing system so that those who want to write
patches can more easily find tickets to work on.

“In progress” is an existing optional step that can be used to signal to
others that you are working on providing a fix for this issue.

“Fix Provided” replaces the former resolved status. When you provide a fix
you click “Fix Provided” and then it goes into a queue for the code review
meetings. If that team has feed back for you they will add it as a comment
and reopen the ticket. When you’re ready to have the code review team look
at your patch again, you simply click “Fix Provided” again to get it back
in the queue.

“Fix Reviewed” replaces the old custom field check box that was most
recently “Code Reviewed”. This step is much easier to search for and
easier to tell where that issue is in the workflow.

“Fix Committed” is the state the ticket will be in after Opscode merges
the fix into the code repository.

Ideally “Closed” will become “Fix Released” but I need to work with JIRA
more to see if I can trigger this.

Component is now a shorter list and required for filing a ticket. If you
don’t know you can just pick something, but it’s really helpful to know
what the ticket is against so the right resources can work on the issue.


Bryan McLellan | opscode | technical program manager, open source
© 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org

P.S. The mixlib and knife plugin projects on JIRA will soon be
consolidating into a single MIXLIB and KNIFE project respectively with
components to differentiate the separate libraries or plugins.