Permission to Stop Adding Tickets to Open Sprint - but still add to Sprint Backlogs

[Umer Saeed]

Hey guys.

I know in the permission scheme, if I block a group to execute the Schedule Issues permission, this will stop them from adding tickets to the open sprint. However, I want these people to be able to add tickets from the backlog to the various sprint backlog's I've opened underneath the current open one.

Is there a way I can do this?

[Gabriel Senna]

Hi Umer,

If this backlogs are not schedule yet, if the users have the "Move Issues" permission, they should be able to move the issues between the backlog. 

Otherwise, the "Schedule Issues" will be needed. 

[Umer Saeed]

Hi Gabriel

Sorry for the late reply. The "Move Issues" permission also prevents the user from moving tickets from the product backlog into the sprint backlogs, in addition to open sprint.

I want to only prevent them from adding to a current open sprint, but allow them to drag tickets from backlog to future sprints.

Can this be done in any way? I've played around with various permission options, but no luck. 

Thanks

Umer

[Jeremy Sloan]

I definitely have a use case for this. I want to setup a planning role, which I would like to allow the user to move tickets anywhere except the current sprint.

[Josh Wexler]

This didn't answer the question.  There is a specific need to block moving tickets into an active sprint.  We go through an extensive planning, sizing tickets and fill each developers capacity. Then after kicking off the sprint, someone outside the team will create a ticket and move it into the active sprint which should be an obvious thing to block from happening. We also want stakeholders to be able to move tickets into future sprints freely.  

This seems to be an obvious need that you don't provide for.