Future Sprint Field Removed from Issue when Auto-Managing Sprints

[Scott Derderian]

We have upgraded to JIRA 9.12 relatively recently, so auto management of sprints is relatively new functionality to us.

I had a user today indicate that they had some issues that were assigned to future sprints, that had the sprint value removed during the sprint transition, thereby placing the issues in the backlog.

Has anyone else experienced this?   And if so, what guidance can I give my users as to what to watch out for so that this does not occur in the future.

Thanks in advance!

[Layssa Souza]

Natively, the sprint change happened as shown in the print below.

Is this behavior different for you? Would there be evidence of how the user performed the action?

[CJ Jang]

Hi, I'm the user. @Layssa Souza . Rather than manually completing the sprint like in your screenshot, I checked the box for "Start and complete sprint automatically" as in the screenshot below. For the sprint that completed automatically, it worked correctly, moving open issues to the backlog. However, it ALSO moved some issues out of future sprints (that had not started or completed yet) into the backlog as well, which was not expected.  

[Layssa Souza]

@CJ Jang 

I understand, I did some simulations in my environment, but I couldn't reproduce the same scenario.

Could you share 2 problems that experienced this scenario? And 1 problem that went through the change correctly?

Here it would be interesting to have the history of changes to questions, to be able to map possible problems.

1 issue that was in the sprint and was correctly moved to the backlog – issue history

2 issues that were in future sprints and were incorrectly moved to the backlog.

Thanks.

[CJ Jang]

@Layssa Souza Sprint DCP 2024Q4.5 completed on January 20th at 10am and open items from that sprint moved to the backlog as expected. However, nothing displays in the History where it worked correctly, as they are still part of the DCP 2024Q4.5 completed sprint. Below are examples in the history where items were moved out of future sprints.

[Layssa Souza]

Hello, @CJ Jang 

I carried out some more tests here, and I noticed that when it is removed from the sprint, no action is generated in the history.
I was able to observe that the execution of the anonymous user may have something to do with external automation. That said, is there any automation aimed at sprints? Is it removing issues from the sprint that are linked, or that have some component that causes issues to be considered as peers?

Furthermore, the version I was able to perform the tests on is version 10.3.2, which could even be a version bug. It might be interesting to open an issue with Atlassian support for evaluation.

Best regards.