Customers have installed this add-on in at least 224 active instances.
    by CollabSoftfor JIRA Server 7.2.0 - 7.3.6 and more versions
    Versions available for JIRA Server 6.4 - 6.4.14
    JIRA Server 7.0.2 - 7.1.10
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    JIRA Service Desk
    This add-on is compatible with JIRA Service Desk.
    CollabSoft supports this add-on.

    Get support

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

    Share versions and components between projects with Version & Component Sync for JIRA

    Share versions and components between projects with Version & Component Sync for JIRA

    More details

    This is the first version of the add-on that combines the Version Sync and Component Sync add-ons into a single product compatible with JIRA 7.2.x.

    Existing customers of Version Sync & Component Sync add-ons should disable the old versions in their JIRA instance prior to upgrading. Although backwards compatibility is not guaranteed, the add-on will try to migrate current add-on configurations to the latest version.

    Please make sure to read the add-on documentation prior to installation.

    User reviews

    Sign in to write a review
    by Anand Unadkat on 2017-03-17
    When is this going to be compatible with JIRA Version 7.3.2? Thanks
    Was this review helpful?YesNo
    by Ron Gliane on 2017-03-14
    Re-installed after updating to get the 2/22/17 patch. But now every time I enable the add-on, the Summary view for a project's administration page looks like the HTML is mangled. When I click on the link to add a project link for Versions or Components, the link takes me back to the mangled Summary view.
    Was this review helpful?YesNo

    Hi Ron,

    Thanks for your feedback on the Version & Component Sync add-on. The problem with not finding any projects to sync with is indeed a know problem. A hotfix release will be made available on the Atlassian Marketplace by the end of today for all supported versions of the add-on to address this issue.

    [UPDATE 2017-02-22]: the hotfix release that resolves this issue is now available on the Atlassian Marketplace.

    Kind regards,

    Remie Bolte

    by Binisha on 2017-03-10
    Hi Team, We recently happen to install this add-on on our instance. Can you please let me know how this works when a component is deleted from Main project? Main project - MP Synced project - SP 1. Have created few issues in the Synced project[SP] with, say a component "ABC". 2. Have deleted the component "ABC" in the main project[MP] and moved the related issues to another component say "DEF" the issues which had component as "ABC" in the main project moved to "DEF" 3. However in the synced project[SP] the components changed to "None". This should have automatically moved to the component "DEF". We have not got a chance to do the same test with versions. The Addition of components works well. Thanks Binisha
    Was this review helpful?YesNo

    Hi Binisha,

    If I understand you correctly, you would have expected the *issues* in the synced project (SP) to be updated to the new component (DEF) after the original component (ABC) was deleted from the main project (MP).

    This feature is currently not supported in the Version & Component Sync add-on as it only synchronises the versions and components between projects. It does not assign them to issues. You can achieve the above scenario by either renaming ABC component to DEF or by bulk updating the issues in the SP project.

    When renaming a component in MP, the change will be propagated to SP. Issues that were assigned ABC will now show DEF, essentially because it keeps the same component ID. This would work the same without Version & Component Sync, accept that it will mean that you will have to manually rename component ABC in all projects :)

    Using bulk update, you should first create DEF in MP, wait for it to sync to SP, filter all issues with component ABC using JQL and then update them by adding DEF. Now you can safely delete ABC from MP, which will be synced to SP, without loosing references to DEF in the issues.

    Other than renaming the component/version, the feature you are describing cannot be achieved by Version & Component Sync as there is no way for the add-on to know that it is your intention to replace ABC with DEF in the project issues.

    I hope the described workarounds wil help you achieve your goal!

    Kind regards,

    Remie Bolte

    by Kubo Qubson Grznarik on 2017-03-02
    Good plugin. Simple to configure and use.
    Was this review helpful?YesNo

    Thanks! I'm glad to hear the add-on has proved useful

    by John Colburn on 2017-02-23
    We had an issue after upgrading to JIRA 7.2. Unlike other reviewers we found the CollabSoft team to be responsive and very helpful in resolving our issue. If you manage a large JIRA instance or have several teams / projects collaborating an aligning versions and components, it's a must have add-on.
    Was this review helpful?YesNo

    @John: thank you for your kind words and for your help in debugging and resolving the issue!


    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.

    Note: While this add-on has features specific to JIRA Service Desk, the add-on is technically available across the whole JIRA instance. Therefore the above guidelines for the license tier still apply.

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

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free 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

    CollabSoft provides support for this add-on.

    Vendor support resources


    Find out how this add-on works.

    Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this add-on.


    Version 2.1.7 JIRA Server 7.2.0 - 7.3.6 Released 2017-04-24


    Minor bug fix release


    This bug fix release resolves an issue with project links not being properly deleted from the Version & Component Sync add-on configuration when the linked JIRA project no longer exists. The Version & Component Sync add-on would continuously try to synchronise to the deleted project. In addition, the project link would also be incorrectly shown in the add-on settings 'Overview' page.


    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 Version & Component Sync 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 Version & Component Sync for JIRA. You're prompted to log into MyAtlassian. Version & Component Sync 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 Version & Component Sync for JIRA versions compatible with your instance, you can look through our version history page.

    Similar add-ons