Workflow Post "Done"

[Karri Adkins]

We are implementing a new process, however, struggling on how to create a proper workflow. Right now, we do not move anything off of the sprint board until it is PO Reviewed and then set to Done. At which point it is sent to release candidacy. The problem is, the PO isn't reviewing everything in a timely fashion and Sprints are getting jacked up with all the rollover. I would like Jiras to be considered done on QA approval so we can actually close sprints. However, I need the tickets to be able to continue on in the workflow, until we release to production, and can then be closed.

How do I clear a sprint board, w/o roll over, and not use 'Done'?

[Petter Gonçalves · Accepted solution]

Hello Karri,

I'm not sure if I properly understand your question, but JIRA Software will consider that an issue is "Done" when it moves to the last column of the board, as you can see in this documentation:

• The single right-most column will always be green, representing items in a 'successful' state.

That being said, you would only need to map the QA approval in the last column, so it would be considered done and you will still be able to keep your workflow as it is.

If I didn't properly understand your question, could you please elaborate it a little bit more?

[Karri Adkins]

Yes that makes sense, however, technically the issue still isn't done as it hasn't been approved to roll into Customer Test (customer facing environment) or approved to deploy to Prod, when then it is considered "Done".  Those steps are not part of the sprint cycle.

In simple terms, the workflow is something like this:

Backlog  > To Do > In progress > Test > Deploy to Customer Test > Deploy to Prod > Done

But the sprint is only To Do > In Progress > Test > Done

I need to reach a state where the sprint can closed but the issue can move forward through the remaining workflow and not be done/closed until it is release to Prod.

[Petter Gonçalves]

Hello Karri,

Per your question:

How do I clear a sprint board, w/o roll over, and not use 'Done'?

If you perform the steps I mentioned, the issue will be considered Done in the Sprint (It will be cleared), but you will still be able to keep it in the workflow as Open and create a new release to add the issues.

For example, let's suppose that you add the status "Deploy to Customer Test" in the last column (Done).

The Sprint will consider the issues as completed, however, you will still be able to add it to releases and transition it through the status Deploy to Prod > Done posteriorly.

I'm not sure how the reports will work since this is not the conventional path intended by JIRA, however, I believe that it should work properly once you will not set the resolution in the status Deploy to Customer Test (the last status of the Sprint).

[Karri Adkins]

OK, I think I understand what you are saying.  I will see what I can do to test this and see what happens.  Thank you.

[Petter Gonçalves]

You are welcome, Karri.

Please, let me know if you find any blockers performing those steps.

[Karri Adkins]

I reviewed a workflow today from another company, who was able to share with me what they did.  It was exactly what I suspected and what you stated above  "QA Acceptance" = Done by the status in something related to that next step.  In essence, we will be pushing a "Done" ticket through additional workflow steps until we release it to Prod, in which then it becomes "Prod Released" as Done.

Not conventional, but needed.  Work in processing ticket is not necessarily 'Done" just because the sprint is done.  In our case, the sprint being done only confirms the Development work is complete.

[Petter Gonçalves]

Thank you for your feedback, Karri. I'm glad to know my instructions has helped you.

Have a nice day!