You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I was to prevent inserting a ticket to a sprint if the ticket is not in a certain Status (e.g. ready for development.
In https://jira.atlassian.com/browse/JSWSERVER-13214 it says you can achieve this by using a condition in the workflow but I am not sure how. My case is not condition on the transition but rather on the 'add to sprint' action.
Any ideas?
Thanks.
Hi @Mark Segall
Thanks for the interesting suggestion. However, since we are a startup, I don't want to slow down the work for the teams by using 2 boards.
Is indeed there nothing else beside user permission to prevent adding issues to sprints?
Hi @Iris Gal - I think the response to that suggestion was either misleading or misunderstanding the request. Conditions are intended to prevent issues from transitioning until the conditions are met (i.e. Do not transition if the sprint field is empty vs. Do not add sprint value until the issue is in status x).
Your best bet for this scenario is to split the board:
OR (status = "Ready for Development" and status changed AFTER -5d)
Hope this helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Mark Segall
Thanks for the interesting suggestion. However, since we are a startup, I don't want to slow down the work for the teams by using 2 boards.
Is indeed there nothing else beside user permission to prevent adding issues to sprints?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You may be able to do something with a workflow property on the statuses you don't want users to be able to add to sprint:
This Denying the schedule issue permission on those statuses would prevent users from being able to drag into sprint or adding a due date.
Note - This would also mean that they cannot add to future sprints either
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.