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

Deleting a Version does not update issue history

XMLWordPrintable

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      When a version is deleted from the project, issues that used to be on this version do have fixVersion set to None, but the issue history does not display any entries related to this.

      It is a problem when users want to filter issues without versions on Agile boards. Issues that used to be on a version that has been deleted do not show up when we filter by Issues without version.

      Steps to reproduce:

      1. create an Agile project
      2. create an issue on this project
      3. create a version on this project
      4. add this version to the fixVersion field of the issue
      5. delete the version
      6. go to the Agile board, expand Versions tab and click on Issues without versions

      Expected Behaviour:

      the issue should be displayed on the Backlog

      Actual Behaviour:

      the issue is NOT displayed on the Backlog

        1. issues_without_version.png
          issues_without_version.png
          114 kB
        2. version_deleted.png
          version_deleted.png
          103 kB
        3. version_deleted.png
          version_deleted.png
          103 kB

            [JSWSERVER-12090] Deleting a Version does not update issue history

            Hoang Dong (Inactive) added a comment -

            Many thanks for raising this bug. Since there has not been any customer activity on this issue in over a year, we’re closing it as Timed out.
            If you feel that the bug is still relevant to your needs, please leave a comment and we'll reassess it.

            Kind regards,
            Dong Hoang
            JIRA Software

            Hoang Dong (Inactive) added a comment - Many thanks for raising this bug. Since there has not been any customer activity on this issue in over a year, we’re closing it as Timed out. If you feel that the bug is still relevant to your needs, please leave a comment and we'll reassess it. Kind regards, Dong Hoang JIRA Software

            Oswaldo Hernandez (Inactive) added a comment -

            The problem here is likely caused by JRA-22351

            Oswaldo Hernandez (Inactive) added a comment - The problem here is likely caused by JRA-22351

            Oswaldo Hernandez (Inactive) added a comment -

            This issue is about fixing agile not to rely on the change history and instead use the current value of the fields in the issue.

            The change history corruption is being tracked at JRA-43354.

            Cheers,
            Os.

            Oswaldo Hernandez (Inactive) added a comment - This issue is about fixing agile not to rely on the change history and instead use the current value of the fields in the issue. The change history corruption is being tracked at JRA-43354 . Cheers, Os.

              Unassigned Unassigned
              jraupp Jose Raupp (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: