Fix the issue sequence in jira

Edimara March 22, 2024

Hi, I have a problem:

I have a project that "lose" the sequence of issues after a csv importation.
Is there any way to fix this?


My issues "jump" from the XXX-6075 to XXX-520222070

 

 

index.png

3 answers

1 accepted

0 votes
Answer accepted
Benjamin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 22, 2024

Hi @Edimara 

 

Welcome. Don't think you can manually tweak this since the sequence and numbering is auto-generated. The other option is start fresh and reimport all the issues.

 

 

0 votes
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 22, 2024

Hi @Edimara 

Just to clarify, the numeric value "jumps" from...

  • 6,075, to...
  • 52,022,070

So there's >50mil issues been created via CSV?

Are you sure those aren't two separate Project Keys? (eg. ABC-6075, and DEF-52022070)

If not, what's the search (JQL) parameters you used to get this list? Is ORDER BY in key order? Or created date order? It could be sorted another way?

Ste

Edimara March 25, 2024

Hi Stephen

 

I believe that when we were updated issues through CSV, at any moment we we concatenate an issue key and because of this, we created issues starts with "52022...."

I am sure that is the same project. Look at the print without censorship

frpeeeeee.png

Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 25, 2024

Hi @Edimara 

If you haven't uploaded 50mil issues, then I'd contact Atlassian - this is not normal behaviour, and you can't usually skip numbers or merge them like that.

Contact them here: https://support.atlassian.com/contact/#/

Ste

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 22, 2024

Hello @Edimara 

It is possible to force the next sequence number to be used to be reset by creating a new issue through the CSV import while assigning the issue a specific issue key (i.e. XXX-5202070) and mapping that import field to Issue Key. Refer to this article:

https://confluence.atlassian.com/jirakb/how-to-change-the-issue-key-counter-to-a-desired-number-1251410572.html

It is possible that is what occurred with a recent import to the target project.

As per the above article it is not advisable to use the same trick to reset the issue key sequence number to a number less than the largest sequence number currently in use.

 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 25, 2024

Hello @Edimara 

In your last message to @Stephen Wright _Elabor8_ you said:

I believe that when we were updated issues through CSV, at any moment we we concatenate an issue key and because of this, we created issues starts with "52022...."

Can you explain that more? Did you build up a value by concatenating text and then insert that value into a column in your CSV that you mapped to the Issue Key field during the import?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events