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; } } }

Resolution flag not set for all states in "done" category

Jochen Betz

I'm in Jira cloud service management project which has it's own workflow and 2 final states. Both of these states belong to the category "Done". There is NO transition into any of this 2 states which explicitly sets the resolution flag.

But while transition into one of them does set the flag correctly to "done" the other does not.

My assumption, and from what I found so far in the FAQ is, that the flag gets set to "done" automatically when ever a transition happens into a state which is in the "Done" category - as long as the state it is coming from is not already a state which is in this "Done" category.

There is also NO automation which might reset the flag (History/Log does not show any)

Any hint on where else to look for?

Accepted answers

Jochen Betz

A automation which was triggered by another automation caused the field to be set in one case but not the other.

All comments

Dirk Ronsmans

Hi @Jochen Betz ,

I'm afraid your assumption might not be correct:

My assumption, and from what I found so far in the FAQ is, that the flag gets set to "done" automatically when ever a transition happens into a state which is in the "Done" category

The resolution is never set by default based on a category. The resolution is often "Done" but can be a lot of other values (https://support.atlassian.com/jira-cloud-administration/docs/add-edit-or-delete-resolutions/)

Most times the Resolution is set in 1 of 2 ways:

Through a transition screen, this allows you to select a specific value for each work item at the moment of transition
Automatically through a post function/action on the transiton.

Meaning you'll either need to add a transition screen OR a action on each transition in to the final state(s).

Jochen Betz

Thank you @Dirk Ronsmans for your feedback. Then, if it is never set automatically, where to look for why one of the states (or to be more correct transitions to it) DOES actually set the resolution flag? As I tried to explain: None of the transitions leading to any of these 2 states does anything explicitly, neither does a transition screen - which there is none. The only difference is, that one of the transitions askes for user input - but NOT the resolution flag!

Any hints where this magic is hidden?

Dirk Ronsmans

It could also be set through an automation. While this is less common, it is possible.

You might be able to find out what is setting it through the history tab of the work item. Can you look at that tab and see who/at what time the Resolution is set?

Jochen Betz

That's what I wrote above. There is no automation touching it, nothing visible in the log. So it must be somewhere else.
Also, the 2 states are both "custom" states, so no predefined which might do some jira magic behind the scene.

But still, I was not able to find any place which does this explicitly on one of the 2 states.

Jochen Betz

A automation which was triggered by another automation caused the field to be set in one case but not the other.

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-cloud