Correcting Closed Tickets to Update Missing Resolution Field

I've seen several threads about the need to have a status in the Resolution Field in order for a closed ticket to be considered truly closed.

I've also seen a number of members suggest we simply remove the "RESOLUTION" field to avoid having duplicate statuses or tickets that are both open and closed.

Given I'm only learning this now, and now I already have closed tickets with empty resolutions, I need help on HOW to close those tickets and go back update the resolution field to get them to show closed/crossed out in the backlog.

1 answer

0 votes

It's the same answers you've found elsewhere -

First, Correct the workflow so that it sets resolution correctly (either by asking the user in a transition screen, or setting itin a post function

Second, either

  1. re-open and re-close the issues
  2. create a transition from closed to closed that sets the resolution and use it

Bulk edit is your friend in both of these

Whereever you found the advice to ignore the resolution field, they are utterly, totally and completely wrong.  Because an issue with no resolution is NOT closed, and ALL the reporting in JIRA Core and most of it in Agile, Portfolio and Service desk will not work.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

369 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you