Jira Data Center 7.2.0 - 7.3.9
Clone Jira issues with powerful customizations and preconfigured templates
Edit field values before cloning issues
Clone to a different project or issue type
Create custom issue cloning templates
Save time and reduce errors by modifying field values and selecting what is copied over before cloning an issue, not after. Admins can configure cloning options based on your team’s needs.
Choose a different target project and/or issue type when cloning a Jira issue. You can also change field values and decide what gets copied over before cloning the issue.
Build admin-defined issue cloning templates with conditions for which clone options are available, defaults for what is copied and changed, logic for dynamically populated fields, and more.
Edit field values before cloning issues
Clone to a different project or issue type
Create custom issue cloning templates
Save time and reduce errors by modifying field values and selecting what is copied over before cloning an issue, not after. Admins can configure cloning options based on your team’s needs.
Choose a different target project and/or issue type when cloning a Jira issue. You can also change field values and decide what gets copied over before cloning the issue.
Build admin-defined issue cloning templates with conditions for which clone options are available, defaults for what is copied and changed, logic for dynamically populated fields, and more.
More details
What's new in version 6.5?
- Clone an epic and all its child issues and sub-tasks
- Control which issue types are available when cloning epics
- Add customized comments to cloned issues
Highlights:
- Edit fields before cloning Jira issues
- Change the target project and issue type when cloning
- Define specialized issue cloning templates
- Include or exclude custom fields as part of a clone
- Copy attachments, watchers, comments, links, sub-tasks, sub-task estimates, and parent versions
- Copy both fix and affects version/s field values to the issue's cloned sub-tasks
- Admins have flexible options to control how different clone operations work
- Check out the Data Center version of this app — tested for performance, reliability, and scalability
Appfire is an award-winning Platinum Top Vendor and trusted leader since 2005. Our popular Bob Swift, Wittified, and Feed Three apps alleviate common challenges faced by teams worldwide.
Start a free trial of Clone Plus for Jira today!
More details
What's new in version 6.5?
- Clone an epic and all its child issues and sub-tasks
- Control which issue types are available when cloning epics
- Add customized comments to cloned issues
Highlights:
- Edit fields before cloning Jira issues
- Change the target project and issue type when cloning
- Define specialized issue cloning templates
- Include or exclude custom fields as part of a clone
- Copy attachments, watchers, comments, links, sub-tasks, sub-task estimates, and parent versions
- Copy both fix and affects version/s field values to the issue's cloned sub-tasks
- Admins have flexible options to control how different clone operations work
- Check out the Data Center version of this app — tested for performance, reliability, and scalability
Appfire is an award-winning Platinum Top Vendor and trusted leader since 2005. Our popular Bob Swift, Wittified, and Feed Three apps alleviate common challenges faced by teams worldwide.
Start a free trial of Clone Plus for Jira today!
Reviews for cloud
(22)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
(22)Sign in to write a review
Hi Mohankumar,
Great question! We’ll need just a little more information from you (i.e. if you’re using a specific test management app) to better answer your question, so we’d recommend opening a support ticket so we can assist you.
Thanks,
Kat Sandin, Product Marketing Manager
Bob Swift Atlassian Apps (an Appfire company)
kat (dot) sandin (at) appfire (dot) com
UPDATE:
Hi Alvaro,
We’re happy to share that the feature request you mentioned in your review is now available in our latest release! You can read more about it in our release notes. Thanks again for your feedback and for sharing your positive thoughts about our app!
--
Hi Alvaro,
Thank you so much for the 4-star review! We love knowing when we've hit the mark for a customer's needs!
We also appreciate your sharing this feature request with us. We are in the planning stages for our next release and will definitely consider this for our product roadmap. In the meantime, we have logged this request as a ticket, and you can follow it here.
Please feel free to reach out if there's anything we can help with. :)
Thanks again,
Holly Wright, Marketing Director
Bob Swift Atlassian Apps (an Appfire company)
holly (at) appfire (dot) com
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.
Reviews for Data Center
(22)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.
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$10 | 25 users$120 | 50 users$200 | 100 users$400 | 250 users$600 | 500 & upAdditional pricing details |
| 50 users$200/year | 100 users$400/year | 250 users$600/year | 500 users$1,000/year | 750 users$2,000/year | 1000 & upAdditional pricing details |
Pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 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 Atlassian 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 Atlassian product. For Jira 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 (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira 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.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for server apps?
For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are available for server apps. Learn more about community and open source licenses.
- 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 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.
Pricing FAQ
- How does Data Center app pricing work?
Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.
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?
Apps are billed based on the number of users in your Atlassian product. For Jira 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 (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira 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.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for Data Center apps?
For Data Center apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are not available for Data Center apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For Data Center 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 product, and you're all set.
Bob Swift Atlassian Add-ons (an Appfire company) is a Top 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 a Top 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.5.1 • Jira Server 7.4.0 - 8.3.4 • Released 2019-08-06
Summary
Fix for opening Clone++ in a new window and other fixes
Versions
Version 6.5.1 • Jira Data Center 7.4.0 - 8.3.4 • Released 2019-08-06
Summary
Fix for opening Clone++ in a new window and other fixes
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 apps or 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 apps or 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
