Clone Jira issues applying powerful customizations
Edit issue fields before cloning
Clone to a different project or issue type
Customized operations to streamline workflow
Create the issue as you want it to be without having to edit it later. Customization support allows administrators to pre-defined what gets copied and field settings appropriate for your workflow.
Select the project and issue type during the clone operation.
Condition the operation on issue fields like project, type, component, and version. Determine various target fields by project, type, component, and version of current issue. User role can be used as well.
Edit issue fields before cloning
Clone to a different project or issue type
Customized operations to streamline workflow
Create the issue as you want it to be without having to edit it later. Customization support allows administrators to pre-defined what gets copied and field settings appropriate for your workflow.
Select the project and issue type during the clone operation.
Condition the operation on issue fields like project, type, component, and version. Determine various target fields by project, type, component, and version of current issue. User role can be used as well.
More details
- Option to change target project or issue type
- Edit fields before cloning
- Define specialized clone operations with properties
- Include and exclude of custom fields as part of clone
- Option to clone attachments
- Option to clone comments
- Option to clone subtasks
- Option to copy subtask estimates to cloned subtasks
- Option to copy parent versions
- Option to copy parent fix and affected versions to each cloned subtask
- Option to clone links
More details
- Option to change target project or issue type
- Edit fields before cloning
- Define specialized clone operations with properties
- Include and exclude of custom fields as part of clone
- Option to clone attachments
- Option to clone comments
- Option to clone subtasks
- Option to copy subtask estimates to cloned subtasks
- Option to copy parent versions
- Option to copy parent fix and affected versions to each cloned subtask
- Option to clone links
Reviews for cloud
(20)Sign in to write a review
Thanks for your feedback :).
Steps to disable the standard clone action should answer your question.
Thanks for the review, glad it is working out for you. For changing status, you really need to transition the issue to a different status. I would recommend using the Transition issues from Update on Transition for JIRA. How to update issues after initial issue create is the reference for how to do this automatically when the clone is created. You need to be able to distinguish the "clone" case from other cases where you do not want the transition to occur. If you need more clarifications, ask a question on our questions forum.
Torsten, clone doesn't copy work logs. Can you please open an issue with more details of what you are seeing including JIRA release.
Reviews for server
(20)Sign in to write a reviewThanks for your feedback :).
Steps to disable the standard clone action should answer your question.
Thanks for the review, glad it is working out for you. For changing status, you really need to transition the issue to a different status. I would recommend using the Transition issues from Update on Transition for JIRA. How to update issues after initial issue create is the reference for how to do this automatically when the clone is created. You need to be able to distinguish the "clone" case from other cases where you do not want the transition to occur. If you need more clarifications, ask a question on our questions forum.
Torsten, clone doesn't copy work logs. Can you please open an issue with more details of what you are seeing including JIRA release.
Reviews for Data Center
(20)Sign in to write a reviewThanks for your feedback :).
Steps to disable the standard clone action should answer your question.
Thanks for the review, glad it is working out for you. For changing status, you really need to transition the issue to a different status. I would recommend using the Transition issues from Update on Transition for JIRA. How to update issues after initial issue create is the reference for how to do this automatically when the clone is created. You need to be able to distinguish the "clone" case from other cases where you do not want the transition to occur. If you need more clarifications, ask a question on our questions forum.
Torsten, clone doesn't copy work logs. Can you please open an issue with more details of what you are seeing including JIRA release.
Pricing
| 10 users$10 | 25 users$120 | 50 users$200 | 100 users$400 | 250 users$600 | 500 & upAdditional pricing details |
| 10 users$10/year | 25 users$120/year | 50 users$200/year | 100 users$400/year | 250 users$600/year | 500 & upAdditional pricing details |
Paid-via-Atlassian pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your host product. For Jira Server 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (50 users) and Jira Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of Jira Server prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly.
- Do you offer academic, community, or open-source licenses?
For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.
For more details about qualifying for special licenses, see here.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Paid-via-Atlassian pricing FAQ
- How does Data Center app pricing work?
Data Center pricing FAQ
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my Data Center pricing?
Data Center pricing FAQ
- Do you offer academic, community, or open-source licenses?
Data Center pricing FAQ
- Can I extend my free trial?
Data Center pricing FAQ
Bob Swift Atlassian Add-ons (an Appfire company) is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Bob Swift Atlassian Add-ons (an Appfire company) is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 6.1.0 • Jira Server 7.0.0 - 7.10.1 • Released 2017-09-01
Summary
Support for time tracking fields
Details
Versions
Version 6.1.0 • Jira Data Center 7.0.0 - 7.10.1 • Released 2017-09-01
Summary
Support for time tracking fields
Details
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new add-ons from the left-hand side of the page.
- Locate Clone Plus for Jira via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Clone Plus for Jira. You're prompted to log into MyAtlassian. Clone Plus for Jira begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Clone Plus for Jira versions compatible with your instance, you can look through our version history page.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new add-ons from the left-hand side of the page.
- Locate Clone Plus for Jira via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Clone Plus for Jira. You're prompted to log into MyAtlassian. Clone Plus for Jira begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Clone Plus for Jira versions compatible with your instance, you can look through our version history page.
Similar apps
