Here's the scenario:
Without this, when looking back at Sprints, it makes it hard (almost impossible) to track progress across sprints in regards to story points completed.
Hoping someone can help!
Hello @Rochelle Driver
Welcome to the community.
We do not see this behavior in our JIRA Cloud instance. Setting a Version to Released does not automatically change the Sprint field for the issues, and it is the Sprint field that dictates how an issue shows up in a Sprint Report and Velocity Chart. Do you have some custom automation set up that might be doing this
I'm honestly not sure! I feel its the act of release moving the status from done/complete to closed that is causing the issue. Something to do with the Closed status that removed the sprint tag to none. It must be some customisation somewhere, just can't figure out what! I also don't have full access to all board settings so that might be why I cannot figure out where the error is occurring.
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