User Guide
Installation
To install Carbon, select Get it now or Try it free from Carbon’s listing on the Atlassian Marketplace.
If you don’t have the permission to do so, contact the administrator for your Jira instance.
Supported Fields
The table below depicts which system fields will be copied in the cloning or template application process.
| Field name | Automatically populated? |
|---|---|
| Summary | ✓ |
| Description | ✓* |
| Assignee | ✓ |
| Attachment | ✓* |
| Team | ✗ |
| Start date | ✓ |
| Issue color | ✓ |
| Rank | ✗ |
| Flagged | ✓ |
| Development | ✗ |
| Due date | ✓ |
| Linked issues | ✗ (Planned) |
| Issue Type | ✓ |
| Labels | ✓ |
| Project | ✓ Uses the user-selected target project |
| Reporter | ✓ Set to Carbon |
| Parent | ✗ (Planned) |
| Priority | ✓ |
| Environment | ✓ |
| Original estimate | ✓ |
*Media in descriptions and file attachments are copied by reference. Do not delete the source issue if you need to preserve these elements.
Template Features
Templates serve as the foundation for maintaining consistency across your Jira processes.
Creating a Template
Templates allow you to save a reusable blueprint from a source Jira issue that Carbon persists for future use. Carbon captures and stores field values from the source issue, with the exception of media and attachments, which are retained by reference to preserve storage efficiency.
To create a template from an existing Jira issue:
- Navigate to and open the desired source issue using Jira’s native navigation
- Click the ellipsis (…) menu in the top right corner
- Select 【Carbon】Save as template from the dropdown menu to launch the template creation modal (this may take a few moments to load)

- Configure the following template parameters:
- Template name: Provide a descriptive identifier for the template
- Template description: Document the template’s purpose and use cases
- Scope: Define template accessibility as either global (available across all projects) or specific project(s), controlling where the template can be applied

Creating a New Issue from a Template
There are two methods to initiate new issue creation from a template.
From the Sidebar Menu
- Select Apps from Jira’s sidebar menu
- Expand Carbon Templates and Cloning
- Select Apply template to launch the Apply Template modal (this may take a few moments to load)
- Select the desired source template
From Template List
- Select Apps from Jira’s sidebar menu
- Expand Carbon Templates and Cloning
- Select Templates
- On the Template List page, click the Apply this template button for the desired template to launch the Apply Template modal (this may take a few moments to load) with the source template pre-populated
The Apply Template Modal
On the modal, configure the following parameters:
- Target Project: Specify the destination project
- Content & Fields: Select which issue fields should be duplicated
- Include sub-issues and descendants: Toggle whether the complete sub-issue hierarchy should be copied

Applying a Template to an Existing Issue
This capability demonstrates Carbon’s true power: templates can be applied not only to create new issues, but also to modify and enhance existing ones.
To apply a template to an existing issue:
- Navigate to and open the target issue you wish to modify
- Click the ellipsis (…) menu in the top right corner
- Select 【Carbon】Apply template from the dropdown menu to launch the Apply Template modal (this may take a few moments to load)

- Browse available templates or search by template name. Note that template visibility is restricted based on the scope defined during template creation, showing only those authorized for the current project.
- Select the desired template to apply
- Configure the following optional parameters:
- Content & Fields: Select which issue fields should be duplicated, with an optional toggle to remove existing attachments from the target issue
- Include sub-issues: Toggle whether the complete sub-issue hierarchy should be copied
- Remove existing sub-issues from target: Toggle whether to remove the target issue’s existing sub-issues before applying the template

Managing Templates
Dashboard
The Dashboard provides a centralized overview of all template activities.
To view the Dashboard:
- Select Apps from Jira’s sidebar menu
- Expand Carbon Templates and Cloning
- Select Dashboard. This lets you:
- Access key metrics at a glance
- Find a quick how-to guide for creating a template
- Track the most recent templates

Template List
This view presents a comprehensive inventory of all available templates. Users can efficiently browse or search by template name, description, or issue type.
To view the Template List:
- Select Apps from Jira’s sidebar menu
- Expand Carbon Templates and Cloning
- Select Templates
Template Details
The Template Details page offers an in-depth view of individual templates.
To view a specific template:
- Select Apps from Jira’s sidebar menu
- Expand Carbon Templates and Cloning
- Select Templates
- On the Template List page, select the View template details button for a specific template
- This will launch the Template Details modal:

Template Metadata
Template Metadata includes all descriptive information associated with a template, namely its name, description, and scope (global or selected project(s)).
To edit a template’s metadata:
- Select Apps from Jira’s sidebar menu
- Expand Carbon Templates and Cloning
- Select Templates
- On the Template List page, select the Edit template button for a specific template
- This will launch the Edit Template Metadata modal
Cloning Features
Deep-Cloning an Issue
Issue cloning enables ad-hoc duplication of individual issues without requiring the creation of a persistent template.
Carbon’s cloning functionality supports cross-project duplication and hierarchical deep-cloning of sub-issues and their descendants.
To clone an issue:
- Navigate to and open the desired source issue using Jira’s native navigation
- Click the ellipsis (…) menu in the top right corner
- Select 【Carbon】Deep clone from the dropdown menu to launch the cloning modal (this may take a few moments to load)
- Configure the following cloning parameters:
- Target Project: Specify the destination project (may be identical to or different from the source project)
- Content & Fields: Select which issue fields should be duplicated
- Include sub-issues: Toggle whether the complete sub-issue hierarchy should be included in the cloning operation

Monitoring and Settings
Configuring Template Permission
Site administrators can easily control which user groups are authorized to edit and delete templates.
To configure this:
- Navigate to the cog icon (top right) and select Jira admin settings > System
- In the Security section of the sidebar menu, select Global permissions
- In the Grant Permission section, select Carbon: Manage All Templates
Note: If unconfigured, Carbon defaults to granting this permission to the org-admins group.

Process History
Every time a user clones an issue or applies a template, an entry is automatically recorded in the process history, providing complete visibility and an audit trail of all activities.
Process List
This view displays a chronological list of all user-triggered processes, from most recent to oldest. Users can filter processes by type: cloning or template application.
To view the Process History:
- Select Apps from Jira’s sidebar menu
- Expand Carbon Templates and Cloning
- Select Process history
Process Details
The Process Details page provides detailed information about a specific template application or issue cloning operation.
This page presents the following information:
- Job ID
- Status
- Results, displaying the number of successful and failed issue duplication tasks
- Issue hierarchy, displaying duplicated issues with direct links to their corresponding native Jira issues
To view a specific process:
- Select Apps from Jira’s sidebar menu
- Expand Carbon Templates and Cloning
- Select Process history
- On the Process History page, select the View button for a specific process.
- This will launch the Process Details modal.