+1 please implement. We're using Scrumban with an 'always on' active sprint so we're frequently changing scope, by design.

+1. Incredibly annoying. We are all adults here  

+1

Please do it !

+1

+1 PLEASE!!!!

+1

+1 this is so ridiculous, if you have permission to move issues, you should not have to acknowledge this kind of "warning" which by the way is tied to how the team decides to work, not some universal law.

Super duper pretty please can we have this?

Agreed, this message is incredibly annoying, especially when trying to move around a ton of tickets. 

+1 Please create an admin tab to disable this message.  

+1 because of the wrong message this warning may represent: I have seen people scared of adjusting the sprint because they worried about breaking something in Jira, or do something against company policies. No one should scare of doing the right thing. Another suggestion is rephrase the actual warning: it should state that the change is somehow in contrast with Agile principles, but not a dangerous operation.

+1

+1

How on earth did this "feature" even get past UAT. It's instantly, egregiously frustrating. 

+1

+1

No news about this???

+1

+100

+1

+1

+1

+1

Should be renamed 'Make "Sprint scope will be affected by this action" message optional'.

Great solution. Cannot happen soon enough.

+1

+1

+1

+1

Don't need to disable overall, but please add a setting to optionally remove the message.

+1 I would really like to have this feature!

+1

This is likely going to be a non-starter for our team using Jira. There is literally no point to having a sprint mgmt meeting using Jira backlog, if you can't move items between sprints.

This is super annoying, agree with all of the above, just want to add my name to the list. I've never NOT wanted the scope to change, and if I did it on accident, I can always just move the issue back.

I agree with all of the above:

Please help. This confirmation dialog is super annoying.

Please make this confirmation dialog optional. It makes something which would otherwise be a very smooth and quick process cumbersome and clunky and slow.

This is just ridiculous that it cannot be suppressed. SUPER annoying. This is probable the 30th time a get really frustrated with this. I have now started looking for alternative software since this has not been fixed in 3 years and gets me annoyed on a regular basis.

3 years running. no action. come on kids

Please help. This confirmation dialog is super annoying.

Please make this confirmation dialog optional. It makes something which would otherwise be a very smooth and quick process cumbersome and clunky and slow.

This is just ridiculous that it cannot be suppressed. SUPER annoying. This is probable the 30th time a get really frustrated with this. I have now started looking for alternative software since this has not been fixed in 3 years and gets me annoyed on a regular basis.  

This needs to be a setting. I searched for it a bunch before googling a way to suppress. In 99% of the cases, when I move the issue to a sprint I want the scope to change. Not sure why I need to confirm an action that I intend to take 99% of the time. Very annoying as of now. In fact, to justify a mandatory scope change message in the first place, it makes sense to some research to see how many times users unintentionally change scope. 

3 years running. no action. come on kids

Please let us decide based on permission scheme. Maybe add option "Sprint Updated" or just let us choose to exclue the Sprint value as a specific field when that has been updated. So suppress if edit of the fields selected to be excluded.

This behaviour reminds me of Windows Vista and its endless and annoying "Are you sure you want to ... ?". Terrible UX.

Totally agree with this.  Yes, I know that adding tickets or removing them affects the scope.  Please just tell me once and let me turn this prompt off and avoid any prompt that pops up every time you do something. Always give the user the option to "don't show this again". 

Is there any traction on this?  I'm a big fan and a long-time user of Jira across every team I've worked on, and this is one of the most annoying and pointless (IMO) features of the system.  While some may find it helpful, a setting to disable it would be simplest and easiest.  Enable by default, but allow the team to turn off if so desired, as many others have mentioned.  Thank you!

This is just an annoying useless popup. If you add an issue to a sprint of cause you will be changing the scope, no need to be nazi scrum about it. We like to add subtasks to our sprints as we go, and this popup is just annoying.

This just reminded me of something I noticed the other day. In the Android cloud app you can add issues directly into the In Progress section of a sprint board with no warning. So much for protecting the scope of the sprint! I assume this particular issue is just very low priority for Atlassian, unfortunately.

+1 for this. mega annoying to confirm each time.

Just wanted to share that there is a (partial) workaround I did not realize. So I was wrong!

If you add subtasks to an issue in an existing sprint, you will not be warned about sprint scope. You could therefore have an issue called "Being Amazingly Flexible" and subtask there. Whether that's easier than saying OK to the sprint scope warning, I'll leave you to decide. Just wanted to come back and admit that I was wrong about no workarounds.

Admittedly it'd just be better to have this issue addressed, though

@Patryk: As stated in the "Workarounds" section, there are none. This issue is a vote for an option to turn off the warning, thus creating a workaround. Make sure that all the users you know who care about this issue vote for it. Alternatively you could consider not using the scrum template for your project. Or, like some scrum-but organizations I know, if your sprints never actually end (I call these "marathons") then don't start them. Leave them in sprint planning. That allows you to move issues in and out without the warning.

Scope changes are potentially a big deal for many teams, but I do agree there should be an option to toggle this warning and give teams more flexibility with their workflow. I voted for it long ago

Any workarounds?

Agreed, Different workflow for different projects exist for a reason. Some are more fluid with sprint scope, some aren't. I don't want to have to approve adding new work to an open sprint every time.

You allow us to define our own workflows so this message looks redundant. It's really annoying. Please, let us suppress it.