It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA-CLI cloneProject, keep issue key numbers?

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? =)



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.

FOO-1 > BAR-1

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


1 answer

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) 


@Bob Swift [Bob Swift Atlassian Add-ons]

Hi, thanks for your answer. Perhaps you can help once again

The source of the problem i'm trying to get around is that cloneProject (and i assume cloneIssue) does not copy the issue (entity) properties. We are using issue-checklist plugin that stores its data in issue/${issue}/properties/cachedchecklist but i have not found any way to make jira-cli include these properties upon cloning. 

Is there something i have overlooked?


Sam Caldwell Atlassian Team Aug 17, 2016

Test comment in response to a report that the editor is not working.  Please disregard.  

Marcel, clone issue does not copy properties yet. I opened JCLI-1032 to track this request. Thanks for the requirement.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

1,933 views 8 2
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you