Getting started with customization
On this page:
Overview
This page provides an example of how to create a customized clone operation. Only the Jira Administrators can create a customized clone operation. You can create a customized clone operation using the Configuration user interface. It is recommended to do customizing in a test environment before moving to production.
You can customize the default clone plus operations or create a new customized clone operation. It is recommended to do simple customization on the default clone plus operations to set fieldExcludes and leave all other customization to the new customized clone operation.
In your environment, there are likely a bunch of custom fields that should not be copied when cloning issues. It is easy to exclude them by adding a global fieldExcludes line in your clone-plus.properties. This can be extended or overridden on a specific custom clone operation if necessary.
Start by doing a simple customization following the steps and one of the examples on this page. Once you are comfortable with the process, you can look at the detailed documentation for all the customization possibilities: Clone properties
Steps
 | Steps | Details | Examples |
---|---|---|---|
1 | Select a number from 1 to 8 to uniquely identify the customization to be used. | Â | Â |
2 | Decide whether you need a base clone or extended clone custom clone operation. |
| Â |
3 | Enable the module corresponding to your selection from steps 1 and 2. | For more details, see the Enable and disable clone operations page. |  |
4 | If you doing the customization for the first time, create a clone-plus.properties file in the Jira home directory If you have already done the customization earlier, the file must be available in the directory. |
| Â |
5 | The property file works based on named entries that start with a prefix. | The prefix corresponds to the selection of number and type from steps 1 and 2. |
|
6 | Set the required name of the clone operations. | Â |
|
7 | Set the condition that determines whether or not the clone operation 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 clone operation to a test project until you are happy with the rest of the customization |
|
8 | Add other condition elements. | Â |
|
9 | Test the clone operation. | Â | Â |
10 | If required ddd other properties to match your requirements. | See Clone properties for all the customization points. | Â |
11 | Test the clone operation. | Â | Â |
Example
Log a request with our support team.
Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.