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

As an admin, I would like to be able to change the Resolution value without updating the Resolution Date

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Low Engagement
    • Issue - View
    • None
    • 3

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Problem Definition

      Whenever the Resolution field is updated, the Resolution Date is updated accordingly. This will mess up the statistics or reports especially for resolved cases.

      There are some situations where the Resolution value is set but the request is not closed yet, and when the request is closed, the Resolution value is updated. The Resolution Date will be updated twice but the first Resolution Date is the real date for a request to be 'resolved'. However, it's not possible to retain the first Resolution Date.

      Suggestion

      A way to update the Resolution field without affecting the Resolution Date

      Attachments

        Issue Links

          is related to

          Suggestion - JRACLOUD-7302 Bulk edit resolution

          • Gathering Interest

          Suggestion - JRACLOUD-69569 Set the Resolution Date without the need to Transition Issue

          • Gathering Interest

          Suggestion - JRASERVER-63100 As an admin, I would like to be able to change the Resolution value without updating the Resolution Date

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              michin Michelle Chin
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: