We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-63100

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

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Issue - Fields
    • None
    • 1
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-63100

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

              • Icon: Suggestion Suggestion
              • Resolution: Unresolved
              • None
              • Issue - Fields
              • None
              • 1
              • 1
              • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

                NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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

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

                          Created:
                          Updated:

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

                              Created:
                              Updated: