nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Set next issue number

dmoroff

We have conflicts in issue numbers of two jira instances, one instance is located in our company, the other at the vendor of our software. Unfortunately both jira instances using the same project id (i.e. XYZ-). Both are referenced in our GIT repositories.

Where is an idea to manipulate the next issue id to get XYZ-1001234 instead of XYZ-1234. Is there a way to do this? I assume there is an internal database entry containing the next issue number per project.

Accepted answers

Payne

Here is some guidance on that. I've not tried it, so I cannot personally vouch for it.

https://confluence.atlassian.com/jirakb/how-to-set-the-starting-issue-number-for-a-project-318669643.html

All comments

Payne

Here is some guidance on that. I've not tried it, so I cannot personally vouch for it.

https://confluence.atlassian.com/jirakb/how-to-set-the-starting-issue-number-for-a-project-318669643.html

Kevin Paulus

I tried it: It worked exactly as advertised.

Michael Roldan

The referenced link is very clear detailed. Thank you

Unfortunately, it did not work for us. We just imported about 15000 issues into a new project. The last issue imported was ID-31540.

Following the instructions, we imported an extra ticket as described with id ID-31541, which was created without problems, but new tickets afterwards didn't follow the sequence and started at ID-105276765.

Reference: Screen Capture of key list:

Is it something that we have to request from Atlassian Support directly?
Thank you

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server