| Div | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
On this page
|
Summary
...
| Info |
|---|
This is the documentation for Clone Plus for Jira Cloud. If you using Clone Plus for Jira Sever/Data Center, refer the Customization Information - Server page. |
One of the major benefits of Clone Plus for Jira is the ability to customize clone operations to suit your development process. This capability has been provided since the initial version of the plugin. Since version 3.x, we have made it possible to provide very sophisticated customization capabilities without programming. It still requires a clear understanding of your JIRA system and processes, but, the implementation can be done via a property-based configuration with average JIRA administration knowledge and some careful testing. Open an issue if you need more extensive customization than what is currently provided.
Features
...
| autoNumber | true |
|---|
...
- Name can be customized to reflect the purpose related to your process
- Each can be enabled independently as required
- Choose either
- clone to the same project and issue type
- clone to a different project or different issue type
...
1.label = Escalate to Engineering
1.tooltip = Creates a task for Engineering
2.label = Create a Requirement
...
- Each can have unique conditions that determine when the action is available
- Generic on condition fields
- Condition-based on fields
- project
- issue type
- status
- Condition-based on role
...
1.condition.ZCLONE.*.* = true
...
2.condition.*.*.1 = true
1-plus.role.ZCLONE = Developers
...
...
- Set default options
- Options available
copy attachments
copy watchers
copy comments
copy subtasks
copy estimates
copy parent versions
copy links
- copy epic issues (since 6.5)
- copy epic issue subtasks (since 6.5)
- copy epic issue subtask estimates (since 6.5)
...
- option.copyLinks = true
- 1.option.copyAttachments = false
- 2.option.copyWorklogs = hide
- 1.option.copyWatchers = false
...
- Clone properties
- How to clone an epic with all the child issues from the same project - 6.5
- How to clone an epic with all the child issues from different projects - 6.5
...
Current issue fields are available as substitution variables for the setting of fields
...
1.set.summary = BLOCKER: %original_summary%
...
...
In many use cases, certain fields should not be copied to the target issue
...
1.fieldExcludes = custom2, custom three
...
...
Control fields that are allowed to be changed by the user during the clone operation
...
1.ignoreFields = Special
...
...
Map to a new project based on the project, issue type, and status
Map to a new project based on project and component
Map to a new type based on the project, issue type, and status
- Map to a new component based on the component name
Map to a new version based on the version name
...
1.project.SUPPORT.*.* = ENG
1.component.UI = User interface
...
...
1.set.description = Some standard description
...
Get started
Getting Started With Customization is the best place to start.
Additional information
childrenAn administrator can customize these operations on the Configuration page. For more details, refer the following pages:
| Child pages (Children Display) | ||
|---|---|---|
|