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

JIRA 4.1 Created issues conflicting Status vs Resolution

Annette Bernard

We recently made changes to screens and workflow. Newly created issues are being opened with Status=Open and Resolution=Fixed.

I cannot find how the resoltion field is automatically being set to Fixed. Need serious help on this one. Filters are not returning correct data as a result of this situation. How is a Resolution being set when an issue is not resolved? How do I rectify this? HELP!

THANKS!

Accepted answers

All comments

Jobin Kuruvilla [Adaptavist]

Setting resolution can be done at any transition in a post function. Can you check your workflow's Open transition and see if it is done in the post function?

Open transition is the one used when an issue is Created!

Annette Bernard

Our Open transition (named Create Issue) only has 3 post functions. 1) Create issue, 2)re-index, 3) fire Issue Created event.

We've always shown the Resolution field, but it normally defaulted to Unresolved. After the last workflow changes, a re-index was done and the Resolution field was defaulting to Unresolved. This "completed" behavior only began days ago. We did make some screen changes since the last reindex, but no changes to workflow.

Jobin Kuruvilla [Adaptavist]

You shouldn't have resolution on screen. I guess it is probably defaulting to some value on screen now? If not, there must be a listener that sets the resolution!

Annette Bernard

Thank you Jobin. I'll go back through and compare everything to the older version of the workflow. There's clearly something I'm missing.

Nic Brough -Adaptavist-

Yup, as the others say, you must *not* put the resolution field on screen on transitions (or edit screen) that do not end in a status that you want to consider as "resolved". Or you've got workflow post-functions doing it.

Adam Saint-Prix

We had this problem recently where someone absolutely had to have 'Resolution' field on an edit screen, despite my warning against this. We noticed that if we clicked 'Edit', the Resolution field would default to 'Done' even without us making changes, which caused status and resolution to be out of sync. I've seen this before and I'm just guessing Jobin's probably right in this case. my 2 cents.

Annette Bernard

Thank you Adam. We did recently have someone ask about having the Resolution field on the edit screen. We advised against it as well. That may be part of the issue. Thank you for your 2 cents.

Annette Bernard

Thank you everyone. In comparing with two other workflows and screens, it appears that the Resolution field was added to the wrong screen. The issue has been fixed! Thanks again for the help.