If an issue belonging to a sprint is in a specific JIRA workflow state, its removal from the sprint must be prohibited.
In this condition, even the sprint must be prevented from being closed.
How can I do that?
To achieve this behaviour you can do the following:
This will create a condition in the workflow where the transition can only be performed if the sprint field is not empty. Please notice that this will restrict issues that aren't in any sprints to be transitioned, so this will only work as expected if you have one specific workflow for issues being used in JIRA Agile.
Hope this helps!
Thanks for the clues, but I think this will not help. Let me explain better the behavior I'm looking for:
I am looking at my Agile board, and it is in the Plan Mode. In this situation, I am free to manually take ANY issue that belongs to a Sprint and slide it down in the screen, removing it from the Sprint and putting it in the Backlog situation.
As an example, one of my issues in this sprint, is in my custumized JIRA Workflow state named "Waiting-for-client-answer".
In this situation, if I try to take this issue out of the Sprint to put it back in the Backlog situation, this should not be allowed. Only issues that aren't in the "Waiting-for-client-answer" state can be removed from the sprint.
Note that this situation is not related to any specif transition in my workflow, so the "Conditions" clause cannot help me in this case...
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...challenges organisation’s experience in their efforts to adopt and scale agile. Many people associate agility with complete flexibility. And that’s not necessarily true, as demonstrated by this finding....
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs