Customers have installed this add-on in at least 723 active instances.
    by Bob Swift Atlassian Add-ons (an Appfire company) for JIRA Server 6.4 - 7.0.2 and more versions
    Versions available for JIRA Server 4.1 - 6.3.15
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.
    Atlassian Verified
    Bob Swift Atlassian Add-ons (an Appfire company) is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    Bob Swift Atlassian Add-ons (an Appfire company) supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    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.

    More details

    Watch the video!

    • 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

    User reviews

    Sign in to write a review »
    by Assia Alexandrova on 2015-10-28
    So far I have been able to do most of my desired customizations with Clone Plus. I am also interested in changing the status of the original issue, once it has been cloned. Will this add-on allow me to do so, or should I look at Create On Transition instead?
    Was this review helpful?YesNo

    Vendor response

    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.

    by PetraPensky on 2014-07-07
    When will version 3.1.0 be released? We are waiting for the JCPP-175 fix. Thanks a lot.
    Was this review helpful?YesNo

    Vendor response

    Planned to go out today (2014-07-07). Watch: https://bobswift.atlassian.net/wiki/display/JCPP/Release+Notes+3.1
    by Anthony Mak on 2014-05-13
    I got the following error when I try Clone+ with a project using JIRA Agile. This error appear just next to the Epic Link field. === An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getValueFromIssue' in class com.atlassian.greenhopper.customfield.epiclink.EpicLinkCFType threw exception com.atlassian.cache.CacheException: java.lang.NullPointerException at com.pyxis.greenhopper.jira:gh-epic-link/templates/greenhopper/jira/customfield/epiclink/edit-epiclink.vm[line 35, column 57] at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:262) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:507) at org.apache....
    Was this review helpful?YesNo

    Vendor response

    Support issues can be opened here: https://bobswift.atlassian.net/browse/JCPP or find the issue tracker link on the Support tab on this page. Specific to this problem, it stems from a JIRA Agile problem with a workaround documented here: https://bobswift.atlassian.net/browse/JCPP-183
    by Torsten Allard on 2013-03-15
    This tool is quite good. However, for us it still lacks of having a possibility to clone issues without worklog data. It only seems to be possible to exclude worklog of subtasks but not of the main issue itself. If that was possible, we would buy that tool immediately!
    Was this review helpful?YesNo

    Vendor response

    Torsten, clone doesn't copy work logs. Can you please open an issue with more details of what you are seeing including JIRA release.

    by Oliver Pereira on 2012-09-26
    Works fine till 1.3.1v5 but breaks in 1.3.2. 5 stars for getting people addicted to the plugin... ;-)
    Was this review helpful?YesNo

    Vendor response

    1.3.2 is JIRA 4.x only, if you had 1.3.1v5 then 2.0.0 is the only upgrade path. Is that what you are talking about?


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons 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 add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on 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 tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications 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 add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    Add-on purchase and renewal is half-price if you have an academic license for your Atlassian host application. Add-ons 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 add-ons, you can extend your add-on 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 add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons 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 add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more


    Bob Swift Atlassian Add-ons (an Appfire company) is Atlassian Verified. Verified add-on vendors demonstrate high quality, reliability, and business traction. Learn more

    Bob Swift Atlassian Add-ons (an Appfire company) supports Clone Plus for JIRA. You can visit the support site to get help.

    Get support


    Version 5.1.0 JIRA Server 6.4 - 7.0.2 Released 2015-10-26


    More customization options, radio button support, fixes


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Clone Plus for JIRA via search. The appropriate add-on version appears in the search results.
    5. 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.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. 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 add-ons