Summary

One of the major benefits of Clone Plus for Jira is the ability to customize clone operations to suit your development process. An administrator can customize these operations on the Configuration page. Before diving into configuring these customizations, take a look at the next section that provides an overview of each customization feature.

Features

	Feature	Overview	References
1	90+ unique custom clone operations can be defined	Clone operation name can be customized to reflect the purpose of your specific clone process. Each operation can be enabled or disabled independently as your needs change. Operations allow cloned issues to be cloned to a different project or different issue type, as admin specifies. To create unlimited clone operations, you must add a new clone operation or edit an existing one after upgrading to version 1.3.0.	Configuration
2	Bulk cloning	Users can use JQL query to search for issues of interest from various projects and clone them in bulk while copying the respective comments, links, watchers and more. Clone operations can be customized to be available for cloning all the issues in your saved filters.	Configuration
3	Conditioning	Each operation can have unique conditions that specify when the operation is available to users. Condition based on fields project issue type status	Configuration
4	Clone option defaults	Set default options Options available copy attachments copy watchers copy comments copy subtasks copy subtask estimates copy estimates copy parent versions copy links copy issues in epic copy subtasks of issues in epic copy subtasks estimates to cloned subtasks of issues in epic copy work logs When you use the Copy links option, note that a Confluence link from the issue being cloned is converted to a web link in the cloned issue.	Configuration
5	Substitution variables	Current issue fields are available as substitution variables for the setting of fields.	Configuration Substitution variables
6	Exclude field list	Fields specified in this list are not cloned over from the original issue to the target issue, even if they are added or edited while cloning. The values are cleared in the newly cloned issue.	Configuration
7	Ignore field list	Fields specified in this list are not visible in the Clone UI display. The source value of this field in the original issue is copied as-is to the target issue field. This is not applicable to subtask(s) cloning.	Configuration
8	Set fields	The Configuration provides a drop-down list of options for each set field or you can use substitution variables to define issue field values to be used while cloning.	Configuration Substitution variables

Customization information - Cloud

Summary

Features