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

    Ask a question

    OBSS supports this add-on.

    Get support

    Synchronizes field values between parent and subtasks, linked issues, epics and stories

    Synchronizes field values between parent and subtasks, linked issues, epics and stories

    Field Synchronization

    Multiple Configuration Feature

    Advanced Configuration

    Field Sync plugin allows you to synchronize the field values between issues. It is possible to bidirectional sync fields between issues and sub-tasks, between linked issues and between epics and stories.

    You can define multiple configurations to sync between different projects, issue types and fields.

    Different settings for sub-issues and linked issues including project name, issue type, sub-issue type, link type and direction. Besides, 'Sync on create/move' and 'Allow sync on not editable issues' features are added.

    More details

    Field Sync add-on offers you the ability to synchronize the selected fields between selected issues that might be parent and sub-task issues, linked issues, and epic & stories. If you change the field value and synch is completed, than field is also changed that on linked issues. Also there are many advanced configuration settings for your projects these are:

    • Direction
    • Sync on Create/Move
    • Allow sync on not editable issues
    • Allow comment sync on issues
    • Allow define multiple configuration

    JIRA 6.x version is also compatible. Please check Version History page.

    User reviews

    Sign in to write a review »
    by Kate Allison on 2015-07-28
    Update: Vendor did address the bug quickly after logging a review, so I am updating my review now that the critical defect is gone :) 4th start is just pending the support for multiple configurations by project within each listener type (sub-task, issue link, epic-story link) which I heard is coming --- I really need this plugin to work, but there is next to zero visibility into where your support ticket ends up after submitting. Everything, at first glance was working great, but the Comment sync does not respect the settings. I have Sub-Tasks comments syncing in every project, issue type, etc. even though the sub-task listener is not configured for these projects. Big issue. Think I have to disable the plugin now, which sucks because I just bought it.
    Was this review helpful?YesNo


    Hi Kate,

    We are glad to see that your critical issue was resolved quickly.

    As mentioned before, "having different configurations for different JIRA projects" is definitely on our medium term roadmap but it requires some serious modification to the code so we can not give a target date yet.

    Thanks for the interest in our plugin.

    OBSS Atlassian Team

    by William Cupps on 2014-10-10
    I have tried to find a way to get through to support for this product with no luck. I need the ability to sync just some fields in project A and other fields in project B. I need the ability to pre-populate a create sub task screen with values from the sync. I can't find any way to do this, and can't seem to find any way to get in touch with support.
    Was this review helpful?YesNo


    Hello William, We give a support via https://dev.obss.com.tr/jira. You may check that link, create issue for your questions and comments. Thank you.
    by Martin Ferijanz on 2014-04-29
    This plugin is great but it is possible to get this functionality also for epics and stories? The link type between epics and stories are not like the other default link types and it would be great if it's also possible. BR Elke
    Was this review helpful?YesNo


    Hi Martin, We have released the Epic-Story sync feature with v.3.0. Best Regards, OBSS Atlassian Team
    by Total Company on 2014-01-08
    Dear OBSS, First of all I would like to say this is a fantastic add-on which brings lots of benefits to some Jira environments in the world. It's easy to use and the documentation is up to date. It's safes lots of time if the user only needs to change 1-3 fields for the sub-task and the other information are automatically synchronized. I review this addon with 3 stars, because there is one issue. In our Jira environment we have over 50 jira projects. For some projects it's necessary to have the same information in the parent issues as the sub-task issue. And the fact that you can keep the custom fields synchronized with the parent issues. But for some projects we want to synchronize custom fields, but not the basic fields. This add-on doesn't support different settings for some projects. Could you develop this or if I missed it instruct me how to do it?
    Was this review helpful?YesNo


    Dear Sir/Madam, Thanks for your constructive feedback. Different sync settings for different projects is a good idea and can provide more functionality to system. We have created a new feature ticket and also added to our roadmap. By the way, we will be releasing Field Sync 2.0.0 version next week which includes more system field support. Kind Regards, OBSS Atlassian Team
    by Тимофеев Кирилл on 2013-08-22
    Хороший и нужный плагин, но в нем есть баг: Если имя проекта содержит специальные символы (прим.: ":"), то плагин на нем не работает.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo


    Тимофеев К.А./ГАММА-ЦЕНТР :  " Good and necessary plug-in, but it has a bug: If the project name contains special characters (note: ":"), then plug-in does not work."  ( by Google Translate) 

    Hi Тимофеев,

    Thanks for your feedback. We have created a ticket for this bug. We will be releasing a patch today.

    We are also adding a new feature which is "Bidirectional Sync". So that, field sync from Sub-task to Parent task will be a valid option.

    Best Regards,
    OBSS Atlassian Team


    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?

    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


    OBSS supports Field Sync. You can visit the support site to get help.

    Get support


    Version 4.1.4.j7 JIRA Server 7.0.0 - 7.1.10 Released 2016-05-05


    Hot Fix


    Listener creation bug solved.


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

    Similar add-ons