You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a task in JIRA that was added to a sprint already in the Done status (the farthest right column), and it didn't transition to any other statuses during the sprint. According to my understanding, this task should be considered as completed outside of the sprint. However, in the JIRA sprint report for sprint 5, it is categorized as unplanned.
Sprint start date: 04/09/2023 12:19:28
Sprint end date: 14/09/2023 12:02:59
Interestingly, when I replicate this scenario in my private JIRA instance, the task correctly appears in the completed outside of the sprint section of the sprint report, as expected.
Why is the task considered unplanned instead of completed outside of the sprint?
Can you provide a screenshot of the sprint report and the different sections, for reference?
From the above it looks like...
Or, if that's in reverse order - it was moved to Done and added to the Sprint at the same time.
No, the order was first Done and then added to Sprint 5. Here is the info taken from API task changesets, as you can see all changes happened within a minute but the order is correct, and should be considered as completed outside of the sprint. We suspect that the rapid changes may have caused an issue with JIRA's correct ordering of changes, something similar to: https://community.atlassian.com/t5/Jira-Software-questions/Jira-Issues-are-showing-transition-history-in-incorrect-order/qaq-p/2057131
The sprint report is difficult to provide as there were many tasks completed in this sprint but the task in the Completed Issues table, marked as unplanned
For a simple test, have you tried replicating this with a longer time gap inbetween closing the issue, and adding it to the sprint?