Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90397

Incorrect issue status in Sprint reports if a completed Jira issue moved to an active sprint

XMLWordPrintable

      Issue Summary

      Jira generates incorrect Sprint reports with different issue-status when a completed Jira ticket is moved into an active sprint.

      Steps to Reproduce

      Let's reproduce it with an example:

      Sprint start and end time 30/Jun/23 4:40 AM - 14/Jul/23 7:48 AM
      Jira ticket moved to Done 7 July 2023 at 04:01
      Jira ticket moved to Sprint (already done at this point) 11 July 2023 at 01:51

      Expected Results

      Sprint report should show the correct status when Jira ticket moved to the sprint(in this case it's Done and remained in Done status)

      Actual Results

      Per the current design, the sprint report considers that Jira issues should only be added to the sprint before the start of the sprint and in a not-done state. 
      Since a Jira ticket has moved to Done before it was moved to the sprint. It would be inaccurate to mention it as done in the report for that sprint. Hence, the report shows the status of the issue at the time the sprint started ( It was in backlog and in a not-done state). 

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JRACLOUD-90397] Incorrect issue status in Sprint reports if a completed Jira issue moved to an active sprint

            Matthew Hunter added a comment -
            Atlassian Update - October 16, 2024

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - October 16, 2024 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              msood@atlassian.com MonaS
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: