Our team has created a status called released for our JIRA cards. During the sprints someone will mark the cards as 'released' and then the fix version also be marked as released in the Releases section. But it when we close a sprint and move to a new sprint all the 'Released' cards still carry over into the new sprint. How can we set up a rule so that when we close and create a new sprint, only the non-released cards will be in our new sprints?
Unfortunately this is not true. Our board has 'Ready to Release' as the 'most right column', these also move from one sprint to another. I suspect this has to do with the definition of Done. So I need to determine where our Admin can change the rules that will define the 'done' rules.
It may be that your issues that are moving have sub-tasks that are not in the 'most right column'. In that case, it doesn't matter if the Story is "ready to release", it's not considered 'done' because parts of it are not, and it's nonsense to complete something that's not complete.
As @Alexey Matveev _cPrime_ says, there are no "done" rules other than 'it is in the most right column'
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events