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

When issue is cloned, existing resolution date is copied over

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Highest
    • Issue - Backend
    • None

    Description

      Issue Summary

      When cloning an issue, if the Resolution field is already set, its value is copied into the new issue that was just created. This happens both for Classic and Next-Gen project.

      Steps to Reproduce

      1. When accessing any issue, clicks on "..." and then on Clone
      2. The status of the just created issue will be set as the very first of the workflow, but its Resolution will be copied from the clone issue

      Expected Results

      The Resolution value should be cleared

      Actual Results

      The Resolution value is copied from the clone issue. This problem happens both in Next-Gen project AND Classic projects.

      https://share.getcloudapp.com/Qwu0nPD9

      Workaround

      Both Next-Gen and Classic projects

      Access the board and transition the issue to another status that is not Done/Resolved/Closed. Then, move the issue back to the very first status of the applied workflow:

      https://share.getcloudapp.com/6quezd5z

      For Classic projects

      It's possible to add a post-function in the Create transition (right before the Create the Issues Originally post-function) in order to clear the Resolution field, as shown below:

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              itrojahn@atlassian.com Ilenice
              Votes:
              54 Vote for this issue
              Watchers:
              74 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: