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.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot