JIRA v6.2.4 comes with 6 Resolutions:
Long ago, I added two additional resolutions and JIRA numbered them 10100 and 10101. Some time later, I added four more, and JIRA numbered them 10200, 10201, 10202, and 10203. I just added 11 more, and JIRA numbered them 10300, 10301, ..., 10310.
What event causes JIRA to skip to the next batch of 100?
The reason I ask is that we have to hardcode the Resolution IDs in the
jira.field.resolution.include property of the workflow transitions , and I have a new instance of JIRA and I don't want to redo all the properties in my workflows if I can avoid it. I'd rather enter two resolutions (10100, 10101), <do something to make JIRA jump to the next batch>, enter the next four resolutions, <do whatever it is again>, and then enter the remaining 11 resolutions.
What causes JIRA to start a new batch of Resolution IDs?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Rachel Wright (Jira Genie), @Billy Poggi (AUG NOVA, DC), and @Dana Jansen (Confluence Queen) are just some of the folks that lead one of the world's most active Atlassian User Group (AUG)....
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!
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