Is there a low risk way to add new resolution types to a company managed project?

[Barbara Shaw]

Hi! We have a project where the users would like to have additional choices included in the resolution field. I'm seeing documentation for editing workflow properties in the project using jira.field.resolution.include but also viewing a warning:

We do not recommend using all of these types of workflow properties as we cannot guarantee that some data and operations (e.g. bulk operations) will not be broken. Hence, use these types of workflow properties at your own risk!

What is the easiest way to add resolution types for an active workflow in a project? 

[Ash Yadav - VMotion IT Solutions · Accepted solution]

Hey @Barbara Shaw , 

It really depends, personally for production company managed projects it is always best practice to use a test-environment before pushing anything to production.

You could also make a backup of the existing workflow and start working on it directly and can restore it later if anything goes wrong but again, be very careful as the risk is dependent on a lot of factors such as: 

• Is this a production environment? 
• Are critical businesses operations dependent on it? 
• How many users are actively using it? 
• If in the event of a downtime, is there a process in place to deal with this situation? 

Hope this helps. 

Kind Regards, 

Ash 

[Kelly Arrey · Accepted solution]

@Barbara Shaw Apologies Barbara for being late to the party but the documentation you're referring to is about adding restrictions of what Resolution values will be available on a particular transition.

The more general question of how to add a new value to the list of Resolution values is described here, and it's not fraught with risk - adding a new resolution value is a very simple thing for a Jira admin to do.

HTH,

Kel

[Barbara Shaw]

@Kelly Arrey thanks, I am comfortable with adding resolution values to the global list