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 task resolution does not update according to post function

Elena-Alexandra Enache

Hello,

I have browsed other discussions related to resolution vs task status issues and still have not found the answer.

I don't have server admin rights, in case this info si important.

So, the issue is the following: I have a simplified workflow, with several transitions, a part of them being allowed from ALL statuses. The transition from 'IN UAT' to 'DONE' works just fine, the resolution being set as 'Resolved' as per post function. This is the only status in which the resolution is 'Resolved'. I have another transition from 'ALL' to 'PENDING ANALYSIS', in which the resolution is set to 'Unresolved'. When I switch the status from 'DONE' to 'PENDING ANALYSIS' the resolution remains 'Resolved', despite the post function attached to this transition, and I have no idea why or what to do in order to solve this issue. It affects all my reports.

Any ideas?

Thanks

Accepted answers

Nic Brough -Adaptavist-

>n which the resolution is set to 'Unresolved'.

Ok, this may be an interpretation, or it may be the root of the problem.

Could you look again at the workflow transition and tell us exactly how the post-function that sets the resolution is described? Is it literally "resolution will be set to Unresolved"?

All comments

Nic Brough -Adaptavist-

>n which the resolution is set to 'Unresolved'.

Ok, this may be an interpretation, or it may be the root of the problem.

Could you look again at the workflow transition and tell us exactly how the post-function that sets the resolution is described? Is it literally "resolution will be set to Unresolved"?

Elena-Alexandra Enache

Yes, this is exactly how the post function is defined: the Resolution field is set to Unresolved.

Nic Brough -Adaptavist-

Ok, I suspect you've had an inexperienced admin make an understandable mistake.

You should never set the resolution to unresolved, it should be cleared out completely. Jira thinks "resolution empty = unresolved, resolution has any value (including "unresolved") = resolved"

So, if I am right here, the fix is (as an admin):

Go to Admin -> Issues -> Resolutions
Find the resolution called "Unresolved" and rename it to something like "do not use this"
Now go to your workflow and edit that transition again
Remove the post-function that says "set resolution to unresolved" (it should now say "set resolution to do not use this")
Add a new post function in the same place, selecting
1. Update issue field
2. Resolution as the field to update
3. <none> as the value to set (it's the first entry on the selection list)
When you save this, the post-function description should be something similar to "the resolution will be cleared"

Save it

Note: step 2 is where it goes wrong if my guess is wrong. It looks like you have "Unresolved" on the list of resolutions. If you do not, then it's something else!

The fix I've given above will stop things getting worse, and if you re-open issues, it will fix the resolution too. But your existing issues now using "do not use me" may also need fixing.

Elena-Alexandra Enache

Hey,

So, if I understood correctly, null value for Resolution field is interpreted by JIRA automatically as UNRESOLVED so there is no need to explicitly set it like that, correct?

You are right, the JIRA admins have absolutely no experience related to resolutions, they set the post functions at my instructions so I will just give them new instructions.

Thank you very much!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server