...
This will provide an example of how to provide a customize clone operation. You must be a JIRA Administrator to do customization. If you are on at least release 3.1, you can configure customization via the Configuration user interface. Prior to release 3.1, you will also need access to the JIRA installation server file system. You should do this on a test environment before moving to production! Both the default clone plus operations and specialized clone plus operations can be customized.
...
| Tip |
|---|
|
Start by doing a simple customization following the steps below and one of the examples on this page. Once you are comfortable with the process, you can look at the detail documentation for all the customization possibilities: Clone properties |
Steps
| Table plus |
|---|
| autoNumber | true |
|---|
| enableSorting | false | autoNumber | true |
|---|
|
| Step | Detail | Examples |
|---|
| Pick a number from 1 to 8 to uniquely identify the customization to be used |
| |
|
| | Decide whether you need a base clone or extended clone custom action | - base clone actions maintains the project and issue type of the original issue
- up to 8 of these can be distinctly customized via properties
- extended clone actions allows the project or issue type to be changed
- up to 8 of these can be distinctly customized via properties
|
| |
| Have you already done some customization with the property file? If not, create a clone-plus.properties file in the JIRA home directory | |
|
| The property file works based on named entries that start with a prefix | The prefix corresponding to the selection of number and type from step 1 and 2 | - Use prefix 1. for customization number 1 using the base clone plus action (not allowed to change the project)
- Use prefix 2.plus for customization number 2 using the extended clone plus action that allows the project to be changed
| | Set the name of the operations so something meaningful for your users |
|
| - 1.label = Clone
- 2.plus.label = Clone to requirements
| | Set the condition that determines whether or not the action is valid for a specific issue | If no condition is set, the operation will not show up for any issue! Tip: for testing, limit the action to a test project until you are happy with the rest of the customization | - Valid for all issues: 1.condition.*.*.* = true
- Valid only for project XYZ: 2.plus.condition.XYZ.*.* = true
- Valid only for project XYZ bugs: 3.condition.XYZ.1.* = true
| | Add other condition elements |
| | |
|
| | Add other properties to match your requirements | See Clone properties for all the customization points |
| | |
|
Example
| Include Page |
|---|
| JCPP:Example clone-plus.properties |
|---|
| JCPP:Example clone-plus.properties |
|---|
|