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

Problem with resolution and status

Chethana Hashani

Hi,

Can't I find out a way to map resolutions to status. For an instance,

If status == TODO

resolution == open

if status == In-progress

resolution == analyzing/fixing

if status == Done

resolution == fixed/won't fix/duplicate

if status == Verified

resolution == done

Accepted answers

Pete Singleton

While your issues are 'In Progress' the resolution field should be left blank, so it will show as 'unresolved' in searches. You should not be setting Resolution until the issue is actually resolved, whether that is Fixed, Duplicate, Done etc. You can have multiple resolved States, allowing different resolution options if you wish, but any In Progress states should remain unresolved.

Chethana Hashani

Hi Pete,

Thanks for the information. But the problem is, at the very begging of ticket creation (when I create a ticket), it asks me to set the resolution and it is mandatory field in each and every ticket. How can I overcome this?

Nic Brough -Adaptavist-

This is a classic mistake by new administrators.

Never put the resolution on any screen other than a "transition" screen.

To fix this problem now, go to the project affected's configuration, find the issue type screen scheme and descend into it. You should see it maps different issue types on to different screen schemes (there might only be one though). Go into each screen scheme and look at each screen named in them, removing the resolution from Create or Edit screens (don't worry about view, Jira handles that for you)

Next, go to Admin -> Issues -> Screens and add a new screen, with just "resolution" on it.

Finally, go to the workflow, find the transition for "verify" and add the new resolution screen to it.

This will fix the problem, but still offer you Done, won't fix etc. That can be fixed by the use of workflow properties, but get the resolution working correctly first.

All comments

Yogesh Mude_u145qk

HI @Chethana Hashani

We can map/set the status to resolution using the Update issue field post function.

Let say when the issue will create ..you need to apply the update issue field post function on create issue transition with Issue field (resolution ) and the field value (Open) and so on.

But normally we can use/set the Resolution while resolving the issue. i don't know what you are going to achieve with this.

Alexey Matveev

Hello,

Where do you write this script? What is the status variable?

Chethana Hashani

Hi,

I didn't write this script anywhere yet and I wrote this to give a better idea about my problem to readers

Alexey Matveev

Ah, I see. Then I guess the answer of @Yogesh Mude is correct

Pete Singleton

Chethana Hashani

Hi Pete,

Chethana Hashani

Can you please clarify more

Pete Singleton

This is because the Screens and Field Configurations have been incorrectly set up. You should not have the Resolution field present on the Create screen. And to stop it being mandatory you will need to edit the Field Configuration.

You may need to define a new screen for when the issue moves to a Resolved state, prompting the user to set the resolution. This screen would be used in the workflow only (not on Create). You can read more here: https://confluence.atlassian.com/jira063/configuring-fields-and-screens-683542633.html

Nic Brough -Adaptavist-

This is a classic mistake by new administrators.

Never put the resolution on any screen other than a "transition" screen.

Next, go to Admin -> Issues -> Screens and add a new screen, with just "resolution" on it.

Finally, go to the workflow, find the transition for "verify" and add the new resolution screen to it.

This will fix the problem, but still offer you Done, won't fix etc. That can be fixed by the use of workflow properties, but get the resolution working correctly first.

Chethana Hashani

Hi Nic,

I did it and it worked !

Thanks a ton !

Welcome!

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

Quick Links

Find more posts tagged with

jira