nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Workflow with statuses after "Fixed" resolution

Eshan Salpadoru

Hi All,

Our dev and test teams have adapted Agile pretty nicely and have been completing sprints. But we have this situation where we are not always able to deploy the deliverable due to various compliance/policy requirements related to deployment which we have no control over.

While the stories are essentially "Done" when it is ready deploy, we would still like to monitor the stories until they are deployed to prod.

I am contemplating changing the "Resolution" to "FIxed" when it passes "Test" and then having a few more statuses to monitor the story outside of the sprints.

Any thoughts?

Thanks

Eshan

Accepted answers

Nic Brough -Adaptavist-

My thoughts are that you've come up with a very good way of handling issues so that Jira works well for you.

I would have a set of status in my workflow that show me where everything is and then build my boards around it.

A developer board would be exactly what you describe - some columns showing "to do", "being developed" and "done" in general and with the "done" column containing status along the lines of "code done", "ready to go live" and "gone live" - your developers don't generally care about the live status.

I'd then have another board for the people looking after production, with "we developed stuff" as the left-hand to-do column, and the far-right one being "we deployed this"

All comments

Nic Brough -Adaptavist-

My thoughts are that you've come up with a very good way of handling issues so that Jira works well for you.

I would have a set of status in my workflow that show me where everything is and then build my boards around it.

I'd then have another board for the people looking after production, with "we developed stuff" as the left-hand to-do column, and the far-right one being "we deployed this"

Eshan Salpadoru

Thanks Nic. That makes sense. Can you also confirm the velocity/burn down charts work on the resolution field and as long as the resolution is set to "Fixed" when the developers are done with the story, the reporting will work correctly despite having more status afterwards?

Nic Brough -Adaptavist-

>Velocity/burn down charts

These work entirely on the "definition of done", which, in Jira Software, means "the far right hand column". For Jira Software, the resolution is irrelevant.

Eshan Salpadoru

Thanks. That seems critical to how JIRA is used but isn't obvious to people new to JIRA. You'd think Atlassian will make that very clear.

I have a follow up question. I am using a add-on called Epic Sum Up to give me a view of the Epics. This shows the number of completed issues in an Epic. This is displayed on an Epic and not on a board. So in this case, what does "Completed" mean?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

agile

sprint

workflow

resolution