JIRA-CLI cloneProject, keep issue key numbers?

Marcel Montel3

I am using JIRA Cli from Bob Swift. When i try to clone a project with cloneProject it succeeds but i expected the issuenumbers to be the same in the cloned project. Is this possible? Can Bob Swift answer if he's around?

 

eg:

java -jar jira-cli/lib/jira-cli-5.5.0.jar --server $JIRA_SERVER --user $JIRA_USER --password $JIRA_PASSWORD \
--action cloneProject --project $PROJECTKEY --toProject $NEW_PROJECTKEY --name "$NEW_PROJECTNAME" --cloneIssues \
--continue --verbose

now FOO-1 is not the same issue as BAR-1, FOO-2 is not the same issue as BAR-2 and so forth.

 

Edit: The original project had lots of subtasks which are now deleted so FOO-2 to FOO-6 does not exist, so the skew appears whenever a issuekey is not avaible in sequence in the first project.

eg.
FOO-1 > BAR-1

FOO-2 to FOO-6 does not exist so FOO-7 is then BAR-2..

 

Bob Swift

No, not without doing additional scripting to fill in holes in the number sequence. I have done this as part of a migration many years ago. It is pretty straight forward. The logic is something like the following assuming the target project does not have issues:

1. Use getIssueList to get the source project's issue in ascending order
2. Loop through each issue from the list
   1. If there is a hole in the issue number sequence, then create a dummy issue and then delete it
   2. If there isn't a hole, just create the new issue (probably using cloneIssue)