nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I force a resolution is selected when issue is closed?

Angie Goodman

Often when an issue is closed, the user forgets to set a resolution, so the issue is closed, yet remains unresolved. Is there a way to either:

1) (Preferred) Select a resolution prior to closing.

2) Set a post function for setting the resolution status. I know I can do this, but I want to make sure that if a resolution was selected, this will not overwrite it.

Thanks!

Accepted answers

All comments

Randy_dyxb6i

If you dont care about the type of resolution that's set. Just add a post function to the final transition to set the resolution to a value like "Done" and then remove the resolution field from the screen on the transition or disable the screen altogether.

If you DO care about the type of resolution that's set, then add a condition on the transition that the resolution must be set. This will prevent the transition from happening if the resolution is not set.

As an additional tip, make sure any transitions out of your "Done" status clear the resolution field with a post fuction. This will prevent the ticket from looking like it's done if it's ever reopened.

Nic Brough -Adaptavist-

It sounds like you are using a custom field for "resolution status" rather than the system "resolution". Is that true?

Steven F Behnke

The Resolution field is required no matter what if it's on a screen. If they are able to not-set a Resolution, that implies you've done something custom to your JIRA.

Nic Brough -Adaptavist-

Or what Steven said too. A customisation could do that

Randy_dyxb6i

Resolution requirement is set at the workflow level and i dont believe the default JIRA agile workflows have it set as required by default. At least that hasn't been the case in our instance.

Nic Brough -Adaptavist-

Not really.

The system resolution is optional throughout. But, the resolution field, when put on an edit-type screen (create, edit or transition) does not offer an empty option, and nor does it allow your to clear it. As soon as it's put on a screen that a user goes through, it is set to something (this is subtly different to "being mandatory" - it's optional, but set automatically).

So, the posting is describing either a hacked JIRA or a field that is not the system resolution.

I don't remember seeing a change of this being mentioned in the Cloud release notes since JIRA 7.2 came out, and I don't think Atlassian would have silently slipped in a significant change like that without mentioning it to the community.

Randy_dyxb6i

Ah i think we're talking about the same thing. I understand now what steven said. If you put it on the screen, a value will be set. I wonder if they have a workflow transition that doesnt surface the screen on closing.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud