Skip to end of banner
Go to start of banner

How to clone an issue that includes links to other Jira issues using CLI

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

This article explains how to clone an issue that has links to other Jira issues using the Jira CLI app in the Jira Cloud instance.

Instructions

For this scenario, we would need to use the cloneIssue and copyLinks CLI actions. 

  • cloneIssueCreate a new issue by copying an existing issue. By default, if the issue is a subtask, it is cloned to the same parent. Specifying the parent parameter will allow a subtask to be cloned to a different parent. By default, cloned issue is not linked to the original issue. For example, adding '--link Cloners' will add the normal clone link.
  • copyLinksCopy issue links when cloning an issue.
  1. Ensure that the issue that needs to be cloned has linked issues and subtasks. The below example shows an issue being cloned within the same project, T1, that has two linked issues T1-1 and DEMO-2. 

  2. Execute the below CLI action:

    --action cloneIssue --project "ZJIRACLICLONE" --issue "ZJIRACLICLONE-6" --copyLinks --copyComments --copySubtasks
  3. The result of the above code block is as follows:


    Output on the terminal:

    Output on the terminal:
    --action cloneIssue --project "T1" --issue "T1-6" --copyLinks --copyComments --copySubtasks
    
    1 comments copied to T1-9. 
    1 subtasks copied as children of T1-8. 
    Issues T1-8 and T1-1 linked with type 'is blocked by'.
    Issues T1-8 and DEMO-2 linked with type 'relates to'.
    2 links copied to T1-8. 
    1 comments copied to T1-8. 
    Issue T1-6 cloned to T1-8.



    Output in Jira:

  1. Make sure that the acli.properties file in the CLI client folder is filled with Cloud details of Jira as shown below:

    acli.properties
    # Cloud requires an email address and a corresponding API token from Atlassian.
    # Use an existing token or create one at https://id.atlassian.com/manage/api-tokens (requires an Atlassian account login).
    credentials       = --user automation@examplegear.com --token qweRTYUI05eg8g95fXopqw         
    cloudSite         = examplegear
    myjiracloud       = jiracloud       -s https://${cloudSite}.atlassian.net      ${credentials}
    # This defines the default client for actions, choose the most likely used client
    default           = ${myjiracloud}
  • This article applies to the Cloud environment. It can also be applied to the Server environment by changing the acli.properties file with appropriate credentials. 
  • It is recommended to test this scenario in a test environment before implementing it in production. 
  • Make sure that the acli.properties file, if it is CLI v9.0 and above
  • No labels