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; } } }

Custom Workflow - Prevent issues from moving to next sprint.

Lindsay Hunt

I have a custom workflow set up (see below)Screen Shot 2016-02-10 at 11.11.07 AM.png

When a sprint ends, I don't want issues in the Closed / Ready for Release or Released state to move to the next sprint. Right now, these issues are all transitioning to the new sprint, but aren't showing up in the backlog or swim lane boards.

How do I fully close these issues so they don't move on after the sprint is complete?

Screen Shot 2016-02-10 at 11.11.07 AM.png

Accepted answers

All comments

Nic Brough -Adaptavist-

It sounds like they are not being "closed" properly. I'd check that a resolution is being set correctly, and then put done, closed, ready for release and released into the "done" column on the board.

Lindsay Hunt

How would I edit the resolution so that any issues marked as Closed, Done (or any of the flow after Done-In Regression, Ready for Released or Released ) do not carry over into the next sprint?

Nic Brough -Adaptavist-

You just need a resolution set (any resolution), and the four status you've mentioned in the done column

Lindsay Hunt

I'm about to close another sprint and I'm still seeing issues. I have a resolution set to "Fixed" or "Done" for all the issues in the Done Status or Released Status.

In spite of this, when I go to close the sprint, it tells me that there are 41 issues that are incomplete.

Is there any way for me to fix this?

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-core