Bulk Clone Templates — User Guide

Overview

Templates save your entire Bulk Clone configuration so you can reuse it later — from the UI or via Jira Automation rules. A template captures all your clone options, project/issue type mappings, field values, and prefix/suffix settings.

Creating a Template

  1. Go to Filters > Search for work items > Apps (top right) > Bulk Clone to open the Bulk Clone form.
  2. Configure your clone settings: – Select source issues via JQL – Set target project and issue type mappings – Enable/disable options (subtasks, attachments, comments, etc.) – Configure field values, prefix/suffix, and other settings
  3. Click Save as Template.
  4. Enter a name for the template.
  5. Choose visibility: – Private — Only you can see and use this template – Public — All Bulk Clone users can see and use this template
  6. Click Save.

What Gets Saved

A template captures the following settings:

Clone Options

  • Clone subtasks
  • Clone attachments
  • Clone comments
  • Clone status (transition to source status)
  • Clone labels
  • Clone time tracking
  • Clone issue links (with link type mappings)
  • Set reporter as current user
  • Add “cloned from” link
  • Migrate parent epic links
  • Migrate parent links
  • Edit target fields

Summary Modifications

  • Prefix (enabled + text)
  • Suffix (enabled + text)

Project & Issue Type Mappings

  • Source project → Target project
  • Source issue type → Target issue type
  • Custom field values for each mapping

Xray Settings (if applicable)

  • Clone test steps
  • Rebuild test set, test plan, precondition, and test execution associations
  • Debug mode

Note: The JQL query is saved in the template but is not automatically restored when you apply the template in the clone form. When used in Jira Automation, the JQL can come from the template or be overridden in the rule configuration.

Using a Template

From the Clone Form

  1. Open the Bulk Clone form.
  2. Click the Template dropdown at the top.
  3. Select a template — your settings will be pre-filled.
  4. Enter your JQL query (templates don’t restore JQL in the form).
  5. Review and adjust settings if needed.
  6. Click Clone.

From Jira Automation

  1. Create an automation rule with any trigger.
  2. Add the Bulk Clone Work Items action.
  3. Select a template from the dropdown.
  4. Configure the JQL query (or use the trigger issue toggle).
  5. The clone will run using the template’s saved settings.

See the Jira Automation guide for detailed automation setup.

Managing Templates

Settings > Templates

Go to Bulk Clone Settings (Global Page) and select the Templates tab.

What You See

You are… Templates shown
Regular user Your own templates (public + private)
Jira admin All templates from all users

Actions

Action Who can do it
View Anyone (if visible)
Edit Template owner or admin
Delete Template owner or admin

Editing a Template

  1. Click the Edit button on a template row.
  2. You can change: – Name — The display name – Visibility — Switch between public and private – Owner (admin only) — Transfer to another user
  3. Click Save.

Note: To update a template’s clone settings (features, mappings, field values), save a new template with the same name and delete the old one.

Viewing Template Details

Click on a template name to expand it and see the full configuration:

  • General settings: Subtasks, attachments, comments, reporter, epic/parent links
  • Field settings: Labels, time tracking, target fields, status
  • Issue link settings: Clone links, edit links, clone link type
  • Xray settings: Test steps, associations, debug mode
  • Prefix/Suffix: Text added to cloned issue summaries
  • Unique label: Auto-generated identifier
  • Project mappings: Source → Target project/issue type with field values

Visibility

Visibility Who can see it Who can use it in automation
Private Only you Only you
Public All Bulk Clone users on the site All users
  • Public templates appear in everyone’s template dropdown (clone form and automation config).
  • Private templates only appear for the owner.
  • Jira admins can see, edit, and delete all templates regardless of visibility.

Tips

  • Use public templates for team standards — Create a public template with your team’s preferred settings so everyone clones consistently.
  • Use private templates for personal workflows — Keep experimental or one-off configurations private.
  • Name templates descriptively — Include the target project or purpose (e.g., “Sprint Planning → Dev Board”, “Release Template – QA”).
  • Automation requires saved templates — You must create a template before setting up an automation rule. The rule references the template by key.