Plugin for Resolution Field Values

I need to customize the resolution field values on Resolve Issue Screen based on the Issue Type.

If Bug is type I want only fix,won't fix and soon.

Otherwise for Remaining Issue Types, some other resolution field values need to be displayed.

Please provide any plugin somewhat related to only this issue.

2 answers

1 accepted

1 votes
Mizan Community Champion Dec 30, 2012

Did you try Behaviours plugin and the script I provided you here https://answers.atlassian.com/questions/118834/is-there-any-plugin-for-customizing-resolutions-based-on-the-issue-type ?

I dont think there is any other way of achieving this , you will need to do it either using javascript or groovy script in behaviours plugin .

But using scripts may lead to incompatibility to some browsers

Mizan Community Champion Dec 30, 2012

Depends on the script you are using ... You will need to do a good testing on the browsers JIRA is compatible ... Even JIRA requires Javascript to be enabled on the browser .

I cant think of anyway this can be done via a plugin , If you dont want to use a script you might have to make changes in the JIRA source/files . Also note that these changes will have to be manually made during every upgrade of your JIRA

How can I get JIRA source files?

There is the option C. Faysal gave as well. Everything else requires code, whether that's injecting javascript or hacking core code. I don't think this is something that's possible in a plugin (although a plugin might be one way to get your javascript in)

Mizan Community Champion Dec 30, 2012

This is a duplicate question of https://answers.atlassian.com/questions/118834/is-there-any-plugin-for-customizing-resolutions-based-on-the-issue-type where i had suggested the use of Workflow properties but i guess here all the issuetypes share a single workflow

Yes Mizan, but by using workflow properties, need to define the workflow for each issue type.

Also the Behaviours Plugin involves a lot of groovy scripting & it make me to learn groovy script which is time consuming.

Mizan Community Champion Dec 30, 2012

Separate workflows and using workflow properties is a very good option because some day you will define a separate workflow for each issuetype. Also there can be more customization done to the workflows. And no coding needed. No worries during upgrades.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,811 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot