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

Next challenges

Recent achievements


  • Give kudos
  • My kudos


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Scope change Warning not appearing after migration to JIRA Cloud

Hi All,


We have recently migrated to  JIRA cloud, when adding a storyto a current sprint , the warning message we would normally see stating there is a scope change, no longer occurs in JIRA cloud.

Has this warning message been removed from JIRA cloud, or does it need to be toggled on and if so how do I do that?


Thank you

1 answer

0 votes
Jack Community Leader Jul 25, 2019

how are you adding to the sprint? I just tested by dragging an issue from backog and it worked.

scope change.jpg

Hi, it is when we are trying to create a new issue in the sprint. Which now starts to make perfect sense as to why creating a new ticket in a sprint does not produce the warning but dragging something in does. 

You would have thought I would have tested it that way first!


Just did some more testing and it appears the warning message only appears if you drag from the backlog. If you create a ticket for that sprint, or change a current issue in the backlog by opening the issue and selecting the current sprint you do not get the warning message. This was the part that concerns us as it is easily done and would like a warning to show that it is going into a current sprint.

Jack Community Leader Jul 26, 2019

TBH, I have never added an issue to an active sprint from outside of the backlog as I haven't had the need and am in the habit of working w/in the backlog. Did you used to get warnings when doing it in that manner? If so you might reach out to Atlassian Support to get their take on this. You might also consider removing the sprint field from the edit screen so that users must use the backlog means. Personally, I restrict who can add/remove issues from sprints.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

How to create Jira issus from Excel file?

When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...

4,549 views 22 32
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you