Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-16207

Issue history has no original value for Sprint when a Sprint is deleted

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 7.5.1, 7.5.2, 8.20.9, 9.4.1, 9.6.0
    • AgileBoard
    • None

      Summary

      Deleting a sprint add a change history item to issues that were in the sprint. These items have no Original Value or New Value

      Environment

      • Jira Software 7.x and later

      Steps to Reproduce

      1. Create a sprint in a Scrum Board backlog
      2. Add issues to a sprint
      3. Delete the sprint
      4. Check the history tab if an issue that was in the sprint

      Expected Results

      The Change History shows an Original Value of the sprint that was deleted and no New Value

      Actual Results

      The Change History shows no Original Value and no New Value

            [JSWSERVER-16207] Issue history has no original value for Sprint when a Sprint is deleted

            Please solve this as soon as possible. This is causing to many problems.

            Fábio Ferreira added a comment - Please solve this as soon as possible. This is causing to many problems.

            Aleksei Ulianov added a comment - - edited

            It also can affect work with changes of issue history in your own plugins. I voted for this issue and hope to see correction of this bug in next releases.

            Aleksei Ulianov added a comment - - edited It also can affect work with changes of issue history in your own plugins. I voted for this issue and hope to see correction of this bug in next releases.

            Because Sprint names are globally visible and we have a large user base, we periodically run into problems where someone will rename someone else's sprint. I'm afraid that this new ability to delete sprints is going to result in more serious cases, where someone will delete someone else's sprint. Without a complete and correct history record, it will be very difficult to determine which issues were affected by the sprint deletion and recreate the lost data.

            Please fix as soon as possible.

            Wendy Fergusson added a comment - Because Sprint names are globally visible and we have a large user base, we periodically run into problems where someone will rename someone else's sprint. I'm afraid that this new ability to delete sprints is going to result in more serious cases, where someone will delete someone else's sprint. Without a complete and correct history record, it will be very difficult to determine which issues were affected by the sprint deletion and recreate the lost data. Please fix as soon as possible.

              Unassigned Unassigned
              dmcmorris@atlassian.com Douglas McMorris (Inactive)
              Affected customers:
              10 This affects my team
              Watchers:
              18 Start watching this issue

                Created:
                Updated: