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

Different Resolution options according to issue type

GilK

Hi,

I have few issue types that are splitted into 3 families (different workflows):

defects: Bug, Sub-Bug, Fire

tickets: Task, Story, Epic

releases: Release to QA, Release to Integration

All of the should have a 'Resolution' field, but each one of them should have different resolutions

defects: Fixed, Won't Fixed, Invalid, etc.

tickets: Done, Not Done, Cancelled, On Hold

releases: On Hold, Pass, Failed

How do I achieve that with JIRA?

Accepted answers

Joe Pitt

Check out restricting resolutions visible at transition at http://confluence.atlassian.com/display/JIRA/Workflow+Properties I suggest using the include option. If you use the exclude the transition has to be updated whenever you decide to add another resolution value. This doesn't limit the resolutions visible in the issue search however.

All comments

Colin Goudie

This isn't supported in JIRA

You can vote here - https://jira.atlassian.com/browse/JRA-3821

Nic Brough -Adaptavist-

Resolutions are global, so you can't really.

There is a workaround - you can have variable resolution lists, but it's a pigging nightmare to configure. The short story is that you can have different workflows for each issue type, and it is possible to set up workflows so that you can limit the resolutions at that level, by using workflow properties. But it really is counter-intuitive and ugly.

GilK

Thanks,

So how you handle the different issue types resolution?

What would be the best practice for it?

Thanks,

Nic Brough -Adaptavist-

I use the workaround I mentioned.

I desperately avoid it whenever I can - best practice is "educate the users not to ask"

Vishnukumar Vasudevan

Nic

Small doubt.

I it was a custom field, is there a way we can achieve this ?

I use JIRA 4.4.1

Thanks for your time

Regards, Vishnu.

Joe Pitt

GilK

Thanks Joe,

How did you use it to achieve different resolutions for different issue types?

Thanks,

Jobin Kuruvilla [Adaptavist]

by having different workflows for different issuetypes and restricting the resolutions as apprpriate on each of them

GilK

Do you use

jira.field.resolution.exclude or

jira.field.resolution.include for the resolution field

Why?

Thanks so much !

Jeremy Gaudet

I came up with a way to do this without having to use multiple workflows. Instead, I created multiple transitions, one per set of resolution options. So, for example, I have "Close Bug" and "Close Issue", where "Close Bug" only allows "Fixed, Not a Bug, Duplicate, etc", and "Close Issue" allows "Completed, Abandoned, Duplicate".

To make it work such that only one "Close" transition is available per type, I added conditions based on the value of field "IssueType"; for example, "Close Issue" has an OR condition on "Story", "Task", "Sub-task", and probably 5 others, while "Close Bug" is just "Bug".

Because some of the buttons couldn't be described easily, I set the properties of each transition (jira.i18n.title and jira.i18n.submit) such that they all show up in the UI as "Close Issue", giving the illusion that they are all the same transition.

It's obviously not fully ideal; a scheme to manage this would be best as then you don't have to, say, copy validation scripts between workflows, but it's much better than having different workflows, as that makes it harder to change issue type on the fly, and seriously complicates making changes to the workflow elsewhere.

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

issue

jira

resolution