Synchronize field values between Jira issues
Synchronize field values between Jira issues
Synchronize field values between Jira issues
Field Synchronization
Multiple Listeners
Advanced Configuration
Define listeners to sync values between parent & subtasks, linked issues, epics & stories, Jira Portfolio parent&children
Define multiple listeners for different sync needs across your system
Each listener can be configured to work with a different set of projects, issuetypes, link types, events, sync direction
Field Synchronization
Multiple Listeners
Advanced Configuration
Define listeners to sync values between parent & subtasks, linked issues, epics & stories, Jira Portfolio parent&children
Define multiple listeners for different sync needs across your system
Each listener can be configured to work with a different set of projects, issuetypes, link types, events, sync direction
More details
Field Sync apps gives you the ability to synchronize field values between jira issues.
The app listens to updates on Jira issues and syncs changed field values between parent & subtasks, linked issues, epic & stories and Jira Portfolio parent & child issues.
The app can sync both system and custom fields.
Advanced configuration options allow you to define detailed JQL's to select source and target issues, events, link directions and fields to sync.
The new version 5 supports transitive syncs in which one update made by a listener can trigger a sync in another listener. This structure can lead to a chain of syncs across many issues.
More details
Field Sync apps gives you the ability to synchronize field values between jira issues.
The app listens to updates on Jira issues and syncs changed field values between parent & subtasks, linked issues, epic & stories and Jira Portfolio parent & child issues.
The app can sync both system and custom fields.
Advanced configuration options allow you to define detailed JQL's to select source and target issues, events, link directions and fields to sync.
The new version 5 supports transitive syncs in which one update made by a listener can trigger a sync in another listener. This structure can lead to a chain of syncs across many issues.
Reviews for cloud
(10)Sign in to write a review
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
Тимофеев К.А./ГАММА-ЦЕНТР : " 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
Reviews for server
(10)Sign in to write a review
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
Reviews for Data Center
(10)Sign in to write a reviewHi 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
Тимофеев К.А./ГАММА-ЦЕНТР : " 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
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$10 | 25 users$65 | 50 users$125 | 100 users$250 | 250 users$375 | 500 & upAdditional pricing details |
| 50 users$125/year | 100 users$250/year | 250 users$350/year | 500 users$450/year | 750 users$600/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. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- 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. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- 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.
OBSS is a Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
OBSS 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.
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.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 5.6.0.189 • Jira Server 7.5.0 - 8.6.1 • Released 2019-12-17
Summary
Sync Existing as a Service
Details
Ability to trigger Sync Existing Issues feature as a REST endpoint
Versions
Version 5.6.0.189 • Jira Data Center 7.5.0 - 8.6.1 • Released 2019-12-17
Summary
Sync Existing as a Service
Details
Ability to trigger Sync Existing Issues feature as a REST endpoint
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 Field Sync 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 Field Sync. You're prompted to log into MyAtlassian. Field Sync 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 Field Sync 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 Field Sync 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 Field Sync. You're prompted to log into MyAtlassian. Field Sync 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 Field Sync versions compatible with your instance, you can look through our version history page.
Similar apps
