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

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

Auto-scheduling is removing values on issues assigned to active sprint. Is this a bug?


I am working within a Plan and seeing that when I Auto-Schedule my plan, Stories currently within an Active Sprint are having the sprint removed. I have the setting set to overwrite all Sprint values, but according to the support documents, this is not suppose to happen. 

Thank you.

1 answer

0 votes
Dave Atlassian Team Sep 15, 2020


In order to help understand what is happening it would be really useful to get some more information. First of all are you using Cloud or Server? If you're using Server, which version are you using?

Can you also confirm whether or not you have configured the plan to schedule dependant issues sequentially or concurrently (see the "Scheduling" section of the plan configuration) and whether or not the issues being scheduled have dependencies between them. It would also be useful to know what the workflow state of the issues are. In general some screenshots would be really helpful here.

We tried to reproduce the problem ourselves from the information that you've provided but were unable to do so, so any further information to help us reproduce this would be incredibly useful!

Many thanks,

Thanks for the response Dave. We are on Version 3.24 of Advanced Roadmaps for Jira Server. No dependencies between the issues - set to sequential - how does this impact Auto-scheduling?

The issues in the active sprint are in progress and defined status.

active sprint assignment cleared.png

Dave Atlassian Team Sep 15, 2020

Thanks for the update @Nayana Geddam this should at least give us the right environment to try and reproduce the problem on. This does seem to be unexpected behaviour as I don't believe that issues in an active sprint should be changed and it might be that we've fixed this on a release after 3.24.0 - we did make a number of changes to the auto-scheduling behaviour from 3.25.0 to 3.29.1 but I've been unable to identify anything specifically addressing this problem but I'll check further with the team.

Having sequential dependency scheduling means that a blocked issue will always be placed in a sprint *after* the blocking issue (regardless of whether the team velocity could accommodate both issues in the sprint). Using concurrent means that if both issues can be completed then they will be scheduled in the same sprint.

We'll continue to investigate this - I would recommend upgrading to a later version if possible though, not least because you'll be able to take advantage of some additional features!


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

🌐 BigPicture-Marketplace Apps Atlympics

Hello Atlympics, here a market place app that's a game changer given the features and excellent support.  Link to the tool:  Bigpicture project management ppm plugin How did yo...

10 views 0 0
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