Terminologies
Terms | Definition | Example | Syntax |
---|---|---|---|
Clone operation | An option available on the UI that you use to clone an issue is called clone operation. | Clone+, Clone++, Clone+ 1, Clone++ 1, and so on. |
|
Default clone operation | The default clone operations provided by the app, which you can see on the UI when you install the app. | Clone+ and Clone++ are the default clone operations provided by the app. |
|
Custom clone operation | The Jira administrator can create custom clone operations to suit your development process. For more details, refer the Customization information page. | Clone+ 1, Clone++ 1, Clone+ (custome 2), Clone++ (custome 2), and so on. |
|
Base clone operation | The Clone+ default clone operation and its related custom clone operations are called base clone operation. | Clone+, Clone+ 1, Clone+ (custome 2), and so on. |
 |
Extended clone operation | The Clone++ default clone operation and its related custom clone operations are called base clone operation | Clone++, Clone++ 1, Clone++ (custome 2), and so on. |
|
The difference between Clone+ and Clone++ is the latter allows you to change the project and issue type of the clone. Both allow you to change other fields before the clone is created.
References
Â
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.