Best Pratcies for Jira workflow for tickets that move from dev to qa

Question

We develop software and our jira tickets start out with PM who create user stories, then are assigned to DEV who work on them and once they're done with the work they assign the jiras to QA.

Our practice has been that when DEV completes work on a ticket they change the Status to Resolved.  QA tests Resolved tickets.

The problem we now have is that we are using the PORTFOLIO plugin.  Portfolio will only estimate based on tickets that don't have a Resolution - only those with a value of Unresolved.  But when you Resolve a ticket, Resolution is automatically updated.

So i'm interested in understanding the workflow others use to track a ticket's movement from DEV to QA.

Is a jira set to Resolved ONLY after all work is done on it?

Thanks.

Warren_mz9b4z · Answer

Hi @Javier Bastante

If you're using a Next Gen project (I think it's now called Team Managed?) that's a totally different story, I haven't ever used them.

Javier Bastante · Answer

Thank you @Warren for your fast and thorough reply. Very helpful!

Tried to create an additional "releases board" and tie it to our project, but the system won't let me do that. It doesn't give me any projects to choose from.

Will do further research.

Cheers.

Warren_mz9b4z · Answer

Hi @Javier Bastante

It's all set up via Board settings -> Columns.

If you look at the screenshot below of our main board, you'll see that there are numerous statuses lumped into the Resolved column

Whereas, on what we call our "Releases board", those statuses each have their own column to give better visibility into what stage we are with the release.

You'll need to be a Jira Admin to create the extra statuses and adjust the workflow as required, then from within each board, click on the 3 dots at the top right, select Board settings and click into the Columns tab