Value Sync

The Sync Values option in External Data for Jira Fields is an easy way to retroactively populate or update values in existing Jira issues. This is especially useful when you have introduced new dependent fields or updated data sources and need to bring past issues up to date with the latest configuration. By setting clear rules for how and when fields should be updated, Sync Values helps maintain consistency in your Jira projects without the need for manual bulk editing.

How Value Sync Can Help You Keep Issues Consistent

Sync Values is particularly useful because it bridges the gap between the automatic triggers that apply to newly created or updated issues and the existing backlog of issues that were created before dependent fields were introduced.

The triggers for dependent fields are typically an issue creation or update. They ensure that new changes are applied consistently in the future. However, these triggers do not apply retroactively to issues that have already been created.

Sync Values allows you to bulk update these older issues to match your current dependency rules. This means that even if your field dependencies were set after issues were created, you can ensure that those issues are brought up to date. This keeps your Jira data consistent across the board, saving time and eliminating the manual editing that would otherwise be required to fill in missing values across a large number of issues.

Configuration & Options Guide

Access Value Sync

Sync Values can be accessed via the Actions tab in the application settings. Click “Add new Action” and select the “Value Sync” option.

Sync Value Options

Sync Values also lets you control how fields are updated: you can choose to overwrite existing data each time, or to fill only currently empty fields.

Run Value Sync on Demand

Sync Values provides an easy way to automatically populate or update fields for existing issues. You can run it on-demand for all or selected issues.

Target Specific Projects or Issue Types for Updates

By entering a JQL query like shown below, you can target specific projects or issue types that you want to update. JQL queries are also a convenient way to test actions on a small scale before applying them to your entire backlog.

Typical Use Cases

Introducing a New Dependent Field After Issues Are Already Created

A common scenario is to introduce a new dependent field after several issues have already been created. Instead of manually updating each issue, you can run Sync Values to retroactively populate the field with the correct information.

Update Outdated Data in Older Issues

Another example is updating outdated data in case of major changes in your data source: You can use this feature to replace all old values with current data from your data source.