When I move an issue from one project to another, is there a way to preserve the issue numbers?

For example: if I move task A-1 to project B, I would like for the task to have key B-1 in project B.

1 answer

1 accepted

Well, at least not out of the box or manipulation the database I guess since the keys are continuous. YOu might already have one issue with B-1 as issue key in your target project...

Thanks, that makes sense.

If the target project is empty, or I can otherwise guarantee non-overlap of the numbers, how do I get the issue numbering to be preserved? Must the query which fetches the source records impose an ordering on the records, so that they'll be moved into the target project in the same order as they were retrieved by the query? I suppose that for such a stunt to work, one must also find a way to force the target project issue number to start at a particular value?

Forcing the target project to start at a fixed value is relatively easy. There is a pcounter column in the project table and you can reset it to the value you want. You will have to do it when JIRA is offline.

Note that the issues created in the target project will still be continuous even if it is not in the source project.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

27,289 views 2 7
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you