Hi and Welcome to the documentation of Bulk Clone Professional Cloud for Jira

On the following pages we will guide you through the setup and usage of this plugin, and you will see how easy it is to get started and how intuitive the plugin is to use.

The documentation contains of the following chapters;

• Installation of the plugin
• Setup of the plugin
• Usage of the plugin
• Full history of Release Notes

If you have support questions drop us a note here

Check out our Video Tutorials also

Installation of the Plugin

1. Log into your JIRA instance as an admin.
2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads
3. Click Find new add-ons from the left-hand side of the page.
4. Locate Bulk Clone Professional for Cloud via search. Results include add-on versions compatible with your JIRA instance
5. Click Try free to begin a new trial or Buy now to purchase a license for Bulk Clone Professional for Cloud. You’re prompted to log into MyAtlassian. Bulk Clone Professional begins to download.
6. Enter your information and click Generate license when redirected to MyAtlassian.
7. Click Apply license. If you’re using an older version of UPM, you can copy and paste the license into your JIRA instance.
8. You’re all set! Click Close in the Installed and ready to go dialog.

 

Setup of the plugin

The configuration and setup of the plugin is very simple to accommodate and basically follow the same scheme as the built in Jira bulk operations

Default Settings – “Jira Administrator” and “Jira System Administrator” always has global access to Bulk Clone in all instances, all others must apply generic Jira Bulk Operation privileges;

1. Global “Bulk Change” operational rights (Found under Administration|System in Jira)
2. “Create Issue” permission for the Jira project(s) you are cloning to. (Check Jira Project’s permission scheme)

 

Special Permission Settings

Bulk Clone can clone without problem if even if the users has only Read Only rights to the source project(s). This is particular useful for instance if you have a “template project(s)” which you want to Bulk Clone from, but want to protect the content of this project not to be altered accidentally by your users.

Setup & configuration of Bulk Clone on the apps panel

The Panel contains of these choices & configurations

• On the APPS|Templates you can maintain existing templates saved prior – Users guide on Bulk Clone Templates if you need to save a new template for the first time you do so in your cloning operation in the last “Confirmation Screen”, it has an option called “Saved Templates. You can also check out our instructional Youtube video on how to leverage our Smart Templates

• Clone Spaces – Create a new space by cloning a existing space’s configuration with or without data

• xRay – Your Xray Cloud API Configuration – Setup xRay Test Management with Bulk Clone. Go into xRay plugin and create an API Key, copy the Client ID and secret into here and you are connected and BulkClone will load the xRay tab in your next Bulk Cloning session.

• Connected Sites – Advanced Edition only – Setup a connection to another Jira site that allows you to Bulk Clone between sites. This is particular useful in large enterprises with multiple Jira sites in different regions or use case scenarios like “mergers” where data needs to be transitioned. Note that you can also Bulk Clone xRay test entities between sites, just check the box and setup an xRay API key in the other Jira Site

• Dashboard – Usage and environment info – Your “birdseye view” on how Bulk Clone is being used

• Log – View previous cloning operations and maintain log histories. This is were can can delete old logs or detect in details if something has gone wrong and what in detail.

• License – License Information on your installed instance, very useful if you need help from your Jira admin or us.

• Setup manual triggers or schedule an automated job with Bulk Clone

This is extremely useful when you have mission critical reoccurring Bulk Cloning operations that need to run so you wont forget to run them.  See also our instructional video on Youtube

• You will find this if you choose a particular space/project and then right click on it and choose manage the “…” and the go to “Space Settings|Automation”. Create a new rule from scratch

• Search for Bulk Clone and it will pop up as an action item

• Reuse any of your earlier saved templates – If you run on our “Advanced Edition” you can also reuse templates to other Jira sites & Bulk Clone

Everyday use of Bulk Clone

Once you have configured the setup of the plugin as described above, it is now time to go to action and use it.

• From Jira: Go To: “Search for Issues” menu to query the result-set you want to clone, alternatively click on existing saved filter.
• Once the result set for the JQL builder is shown you can then choose “Bulk Clone” on the Apps Menu. (Ensure that you have user rights for this menu choice)
• The listings should look like the screenshot below;
• 

 

 

You are directed to the Bulk Clone startup screen, This is where you set your Bulk Cloning Options

Template – section

• The template “dropdown” allows you to choose a previously saved cloning template (saved on the final confirmation screen. This is particular useful if you are doing repeated cloning operations and don’t want to set the options each time or simply forgot what settings you were applying before.

General – section

• “Clone Subtasks” – Includes subtasks associated to an issue (They do not need to be included in the JQL query)
• “Clone Attachments“- Any attachment to either Parent issue types or Subtask issue types gets cloned. For
• “Clone Comments” – checkbox allows you to include/exclude cloning of comments associated to an issue, all comment threads for the issue is cloned if this option is checked.
• The “Set Reporter as Current User” – checkbox set the reporter to the current logged in user
• The “Rebuild Epic Links” – checkbox allows you to included/exclude a preservation of link relationships between the issue type Epic and its associated User Stories (associated through the Epic Link Field) if an Epic is also cloned. It includes that the Epic and its associated stories are included in the JQL Query
• The “Rebuild Parent Links” –  Allows you to included/exclude a preservation of link relationships of any defined parent/child relationship of issues

Fields – section

• “Clone Labels” – Clones any previously set labels on the issues, both for parents and subtasks
• “Clone Original Estimate” – checkbox allows you to include/exclude any time Estimates for a particular issue, for instance User Stories, Test Cases, Incidents etc.
• The “Edit Target Field(s) Values” – Allows you to include/exclude editing of output values of Jira’s system & custom fields. You can select a free number of fields to alter the output for. Any mandatory fields will also be autodetected here.
• “Clone Status” – checkbox allows you to clone an work item’s workflow status. if the status exists in the cloned target project it clones it directly according to the source work item status, otherwise you are presented with a “mapping screen” what you want to clone it to.

Work item links – section

• “Clone Work Items Links” – Clones the link between the work items

The “Add a Clones Link” – Adds a “Clone Link” to the original issue

Identify output – section

• The “Unique Label” – Clones the autogenerated label by Bulk Clone so you can identify your cloned set afterwards
• The “Summary Prefix” – field allows you to include/exclude a custom prefix on the “Summary field.
• The “Summary Suffix” – field allows you to include/exclude a custom suffix on the “Summary field.

xRay – Tab – Note will only appear if xRay is installed and enabled

• “Clone Test Details” – Clones the test the manual steps & cucumber scenarios of a xRay test case
• The “Rebuild Test Set Associations” – Checkbox allows you to included/exclude a preservation of link relationships between a xRay “Test Set” parent issue type and its associated tests (test cases) (without cloning the link of the original source issues)
• The “Rebuild Test Plan Associations” – Checkbox allows you to included/exclude a preservation of link relationships between the xRay “Test Plan” parent issue type and its associated tests or test sets (without cloning the link of the original source issues)
• The “Rebuild Test Pre-Conditions Associations” – Checkbox allows you to included/exclude a preservation of link relationships between the xRay “Test Plan” parent issue type and its associated tests or test sets (without cloning the link of the original source issues)
• The “Rebuild Test Executions Associations” – Checkbox allows you to included/exclude a preservation of link relationships between the xRay “Test Executions” parent issue type and its associated tests or test sets (without cloning the link of the original source issues)

Speed – Tab – section

Here you can set your Bulk Cloning speed of your set to be cloned

Note: Higher speeds clone more work items in parallel, then restore backlog order using the ranking API. Very large runs are automatically reduced to a safer speed to stay within Jira’s shared rate limits. Choose “one at a time” to guarantee order without the ranking API.

Once you’re done with your Bulk Clone settings, press “Next”. If you have choosen to just Bulk Clone a subset of issues in the first step, you are presented with this screen, Where you can determine what items you like to clone.

Next if you have our “Advanced Edition” installed, you will be presented with this screen, where you can determine which Jira site to Bulk Clone too. (Requires that you have setup a remote connection prior)

Next you get into the Project & Fields mapping screen

Here you can configure field settings and set values for “mandatory” fields and/or redirect any issue type to a different project(s) or even change one issue type to another.

 

• • You can also configure Field settings for Subtasks and/or redirect subtasks toa different project(s)
• If you have enabled the “Clone Status” option in the startup screen and the workflows between the source project(s) and the target project differs, you are prompted with this screen to remap it if you want.

• • Once all field configurations are set we are ready to to Bulk Clone, but first a final Confirmation prior to Bulk Cloning which looks like this

• • Note here: that you can “save your configuration options” in a template, and it can be chosen for the next Bulk Cloning session in the startup screen.
  • If you are happy with your set options and field configurations, press “Start Cloning” and the Bulk Cloning operation starts
  • You are prompted with the current status progress screen during Bulk Cloning;

• Once completed, press the “Acknowledge” button to list the outcome of the Bulk Cloning operation

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Finally the Bulk Clone Panel – You find it under “APPS–>Bulk Clone”, the tabpanel here contains a

• Dashboard – Gives you an overview of usage of the plugin
• Log – How has the cloning operation concluded
• xRay (only if xRay is installed & Enabled) that allows you to configer xRay usage
• Templates – All of the saved cloning templates for future reuse
• License – What type of license you are running on

You have now gone through a complete Bulk Cloning Operation, its not more complex than this.

 

Happy Bulk Cloning

Bulk Clone APPS Team