Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,555,479
Community Members
 
Community Events
184
Community Groups

Prevent an issue to enter a sprint on a certain Status

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.

2 answers

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?

0 votes
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 17, 2023

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:

  • Board 1:  Planning/Refinement (Kanban)
    This board will show everything from the point of creation with the final column being "Ready for Development"
    • Filter: status IN (a, b, c)
      NOTE - You may want to add something like this to drop off Ready for Development after a period of time to keep the Kanban clean:
      • OR (status = "Ready for Development" and status changed AFTER -5d)
  • Board 2: Development/QA
    This board will show everything from Ready for Development to Closed
    • Filter: Status IN (x, y, z)

Hope this helps

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?

Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 01, 2023

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:

  • jira.permission.scheduleissue.denied

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 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events