Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-34902

Do not override existing resolutions in a bulk transition

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • None
    • 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.

      When we transition to Closed, one of the required fields is resolution.
      However, in most all cases, resolution is already populated when it is Resolved - it could be fixed, complete, answered, cannot reproduce,etc.

      However, since it is required, you have to input something and the transition then changes everything in that bulk action to the one selected.

      Consequently, you have to filter out by resolution before doing a bulk transition which is inefficient.

      Either don't make resolution required (and if it's not done, those issues don't complete the transition); or, only override the resolution if one doesn't exist (it is currently unresolved).

      Else the integrity of the data is affected.

            Unassigned Unassigned
            4f4250feead3 Karie Kelly
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: