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

Do not override existing resolutions in a bulk transition

XMLWordPrintable

    • 1
    • 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.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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:
            5 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: