Prevent an issue to enter a sprint on a certain Status

[Iris Gal]

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.

[Casey]

Hi @Iris Gal , I have been searching for a solution to this exact problem, and I agree that having 2 boards is inefficient for startups. It appears that folks have requested this feature a number of times in the past, but each feature request gets Closed by Jira due to "lack of interest". It's hard to believe that others are not interested in having the ability to disable the "Start Sprint" button until certain conditions are met. Seems like a very basic feature to me

[Iris Gal]

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]

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

[Iris Gal]

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]

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 

[Iris Gal]

Hi Mark
This doesn't really work and there is a bug opened to Atlassian about this https://jira.atlassian.com/browse/JSWCLOUD-20511