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? 

[Alexey Matveev · Accepted solution]

Hello,

There is no such limit. Try to use the POST /rest/api/2/issue/bulk. This Rest call will let you add multiple issues. You can find more info here:

https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/issue-createIssues

[Danyal Iqbal]

It's difficult to say anything without having a look at the PS script, the for loop and the response from Jira.

I believe your for loop is incorrect.

Is JIRA have some threshold to prevent calling its API too frequency?

Not really, the requests to REST endpoints are queued. Any reasonable frequency should not be an issue. We had no issues with 1000 request per minute (nginx+tomcat+jira). You can alway add a delay in your for loop to eliminate this issue, but I doubt it will help.

[Mark]

Thanks. I found there is a bug in PowerShell old version. It cannot clear the old connection properly.