Customers have installed this app in at least 39 active instances.
    by OBSSfor JIRA Server 6.0 - 6.4.14 and more versions
    Versions available for JIRA Server 5.2 - 5.2.11
    OBSS supports this app.

    Get support

    Transfer issues from remote JIRA systems

    Transfer issues from remote JIRA systems

    Transfer issues between JIRA systems

    Advanced Configuration

    Custom Field Support

    Transfer issues from remote JIRA system easily. Just write a JQL to filter out issues on remote system and issues in that filter will be transferred to local JIRA.

    You can define multiple synchronizers to transfer issues from multiple JIRA systems. It is even possible to target your local JIRA system and transfer issues between JIRA projects on the same instance.

    You can select which fields will be transferred from the remote issue. Transfer of system fields and custom fields is supported.

    More details

    Note: Sync for JIRA was declared End-of-Life. Existing customers will keep getting support for defects but no further feature or compatibility development is planned for the plugin.

    Sync for JIRA allows you to transfer issues from a remote JIRA system to your local JIRA.

    - Create multiple synchronizers to connect to multiple remote JIRA systems.

    - Define JQL statements to filter issues on the remote system.

    - Configure which fields to sync on issues, including system fields and custom fields.

    - Target your local JIRA to transfer issues between JIRA projects on the same JIRA.

    - Get informed by e-mail for failed issues.

    - Export & Import settings as XML

    User reviews

    Sign in to write a review
    by Baran Topal on 2015-02-03
    Hi; Is this 2 ways or only 1 way still? Is it working for new issues or covering the updated issues? Regards.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Hi Baran, Sync is only one way for now. We are developing our plug-in for cover updated issues too. Thank you for your interest in "Sync for JIRA".
    by Jacky Jin on 2014-12-03
    this plug on is very helpful to us. that we can sync the customer field from the main issue and the sub-issue.
    Was this review helpful?YesNo
    Hi, That need can be met with our other plug-in Field Sync for JIRA which allows fields to be synced between parent and sub-tasks as well as linked issues.
    by Oleg Putilin on 2014-08-05
    Sync work one way only and for new issues only. Updates are not synced.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo
    Hi Oleg, Thank you for your valuable feedback. “Full Issue Sync” feature is definitely on our roadmap. It would not be accurate to mention a specific date at this time tough. Please keep your feedbacks coming..
    by Michal Pietrasik on 2014-07-02
    Quite a long way to go before we can call it a "SYNC", but good starting point. Could you extend currently imported information with project versions and corresponding tickets affected and fixed versions earlier then providing the final fully functional solution ?
    Was this review helpful?YesNo
    Hi Michal Pietrasik, Implementing all system fields and full sync functionality is definitely on our roadmap. Implementation of system fields will sure be given priority, yet we can not provide a specific release date for both features. Kind Regards, OBSS Atlassian Team
    by Justin Dombroski on 2014-05-06
    This is more like a glorified external project import. Edits made in one instance after the initial sync aren't synced to the new instance. I can only have one sync for one issue type running at a time. Syncing subtasks doesn't appear to work.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    Hi Justin, Thanks for your feedback. For now, plugin is replicating the issues from one JIRA instance to another. Full sync feature is in our road map and we are currently working on it. You can get the 'Sub-tasks' with JQL Query and they will be created with the issue type which you configured in the settings. Kind Regards, OBSS Atlassian Team


    Pricing details are loading…

    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.

    Learn more

    OBSS provides support for this app.

    Vendor support resources


    Find out how this app works.


    Collaborative documentation platform hosted by this vendor.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

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


    Version 2.2.0 JIRA Server 6.0 - 6.4.14 Released 2015-04-21




    • Support for synchronization of updated information from remote JIRA
    • Configuration screen visual improvements


    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 Sync for JIRA via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Sync for JIRA. You're prompted to log into MyAtlassian. 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 Sync for JIRA versions compatible with your instance, you can look through our version history page.

    Similar apps