Increment Jira ticket numbers

[Emerico Vespucci]

Hello.  We have a Jira project with a prefix of CLS.  We have an issue where some of the past story numbers have gotten reused. This is impacting our smart commits for Bitbucket.

I am trying to find out if its possible to bump up the current numbering counter for new tickets by 1000 to avoid any conflict with old tickets.

For example, there are no current or historic tickets above CLS-400. We would like to have Jira start creating the next ticket as CLS-1000 and so forth. 

Thanks

[Trudy Claspill · Accepted solution]

Hello @Emerico Vespucci 

A Jira Administrator can use the External System Import feature to import an issue from a CSV file, explicitly setting the imported issue's key value to CLS-1000. That will cause the next issue created in the project after that to get the key CLS-1001.

[Emerico Vespucci]

Hi Trudy. That was the fastest response I have ever seen. 

Makes sense. I import one story with CLS-1000 and the rest will start from there?

Can I do this with a post API instead of import?

[Trudy Claspill]

I have not tried forcing an issue key set/bump while creating an issue via the API. Give it a try and see what happens! 

[Emerico Vespucci]

I tried and was able to create an issue. However, it ignored the issue id in my CSV file. 

I used this link to prepare my CSV file.

I'm concerned the "Key" header in my CSV may not be the correct header?

[Emerico Vespucci]

It seems as if it ignored the key I added and simply create the next value. 

[Trudy Claspill]

Are you a Jira Administrator? Did you access the External System Import option available to Jira Administrators under the Jira Settings > System option?

What did you do in the field mapping screen of the CSV import? You have to map the key column to the Issue key field under the Issue Fields list.

[Emerico Vespucci]

Modified my header in the CSV file based on what I see in the Export and still ignored the issue key I have in my file .

[Emerico Vespucci]

I believe the problem is with the mapping. Notice the "Issue Key" header does not have a corresponding Jira Field to map. I chose Issue Id but that is the identifier for the issue and not the actual issue key. 

What is the appropriate Jira Field mapping? 

[Trudy Claspill]

Are you a Jira Administrator? Did you access the External System Import option available to Jira Administrators under the Jira Settings > System option?

This can be done only by a Jira Administrator using the External System Import option.

[Emerico Vespucci]

I figured it out. The Issue Key mapping is only available when performing the import through System

Admin >> System >> IMPORT AND EXPORT >> External System Import >> CSV  and under this import option the "CSV Importer"  the Issue Key is a valid option:

 

Click here to view article

[Trudy Claspill]

Yes, I said that first thing in my initial response:

A Jira Administrator can use the External System Import feature to import an issue from a CSV file, explicitly setting the imported issue's key value to CLS-1000.