Create field mappings
Connect compatible fields between related issues with the Field Echo panel.
.png)
Automatic field synchronization for Jira
Keep related issues in sync ... without updating each one.
A changed launch date, priority, or customer reference should not leave your team tracking down every issue that contains it. Field Echo automatically synchronizes mapped fields across related Jira issues, keeping shared information current where teams plan, work, and report.
Choose which issue holds the source value and which fields should follow it. Field Echo handles subsequent updates across teams and projects, while everyone continues working in their own issues.
01
Choose the sourceDecide which issue owns the value and which related issues need to display it.
02
Map compatible fieldsCreate a mapping from the current issue to a compatible field on a target issue.
03
Keep later changes alignedWhen the source field changes, Field Echo synchronizes the mapped target in the background.
01 / The coordination problem
The same information belongs in more than one issue.
Engineering, testing, and customer success may all need the launch date on their own Jira issues. It belongs in their planning views, filters, and reports—not just in an epic someone has to open to check.
The problem starts when that date changes. Every copy becomes another update to remember, and one missed edit can leave a team working against the old plan.
Field Echo keeps those fields connected to a source you choose. When the source changes, the mapped fields follow, so keeping information close to the work does not mean maintaining it by hand.
Use synchronization for fields that represent the same fact. A team’s independent deadline or a historical record of the original plan should remain separate.
Explore the practical guides in Insights01
Dates drift
One issue changes while a related team's field still shows the old plan.
02
Updates repeat
Someone opens the same related issues and copies the same value again.
03
Reporting diverges
Filters and reports reflect inconsistent information across connected work.
02 / How changes travel
Share the information. Keep control of the fields.
You decide which fields should stay synchronized and which should remain independent. A shared launch date can follow the program’s source issue while each team keeps its own delivery deadline.
Create a one-way mapping between compatible fields, within a project or across projects. Updates flow from source to target; target edits do not flow back, and circular mapping paths are blocked. No Jira Automation rules or workflow changes are required.
Read the complete DocumentationMapping lifecycleExplicit source → target
1 / Select
Start from the source issueOpen the Field Echo panel from the issue's Apps menu and search for the target issue.
Field Echo2 / Validate
Choose compatible fieldsSelectors show fields that are available, editable, and compatible with the selected type. Jira access is validated before the mapping is saved.
Field Echo3 / Save
Create the mappingSelect Add Mapping. Saving a mapping leaves the current target value unchanged. Synchronization begins with the next source-field change, and the mapping remains active until you delete it.
Field Echo4 / Observe
See both sidesOutbound mappings belong to the source issue. Inbound mappings give the receiving issue a read-only view of the relationship.
Field EchoBoundary
Target edits do not flow backField Echo uses one-way synchronization and blocks circular paths. It does not require Jira Automation rules or change your workflows.
03 / Field Echo in action
See where a value comes from—and where it goes.
View incoming and outgoing mappings from your Jira issues, so you can understand which fields receive updates and which supply them. Manage a mapping from its source, or remove it when the relationship is no longer needed.
See incoming and outgoing relationships
View mappings from either issue. Modify or remove a mapping from its source.
.png)
Coordinate across several issues
An issue can receive updates from one issue and synchronize mapped fields to others, with loop protection.
.png)
Review mappings and failures centrally
For administrators, the Admin Console brings active mappings, health indicators, and recent synchronization errors into one place. When an update fails, you have a place to investigate.
.png)
04 / Across teams and projects
Shared information without shared busywork.
Keep the fields that represent the same fact consistent, while teams retain their own work items and workflows.
Planning
Keep teams working toward the same launch date
Engineering, QA, and customer success each need the launch date in their own Jira issues. Map those fields to the release issue so a schedule change reaches each team’s planning views and reports without another round of manual updates.
Delivery
Carry shared priorities across projects
A program’s priorities can change while delivery work is spread across several Jira projects. Map the shared priority from the program’s source issue to the related delivery issues, so teams see the updated priority alongside the work they need to do.
Relationships
Keep partner-facing information current
An internal delivery issue and a partner-facing issue may need the same milestone date or shared text. Synchronize the relevant fields so changes reach the partner-facing record without someone copying each update. Choose which fields to share within the issues users are permitted to access.
Visibility
Keep reports consistent across teams
Teams build filters and reports from different sets of issues. When those issues carry copies of the same customer reference, milestone, or reporting field, outdated values can produce conflicting views. Map those fields to a common source so reports use consistent information as it changes.
05 / Operational boundaries
Explicit mappings. Native Jira permissions.
Field Echo focuses on field-to-field synchronization. It does not modify workflows, permissions, issue security schemes, or project configurations.
Compatibility
Standard and custom fieldsCompatible text, date, number, and string-array fields (such as Labels). Unavailable or non-editable fields are excluded.
DocumentedPermissions
Validate at setup; synchronize as the appMappings are created using the current user's view/edit access. Later synchronization runs with the application's permissions.
DocumentedAdministration
Mappings and recent errorsThe Admin Console exposes active relationships and synchronization failures. Permanent 404 failures receive an ERROR status; temporary rate limits may resolve automatically.
DocumentedRemoval
Stop future synchronizationDeleting a mapping stops future updates and removes the relationship from both issues. Existing field values remain unchanged.
DocumentedData boundary
Your Jira data stays within Atlassian’s ecosystem.Field Echo synchronizes your fields without sending data outside Atlassian’s Jira Cloud ecosystem. Built on Atlassian Forge, it uses no external database or third-party analytics. Mapping configuration, synchronization metadata, and recent error logs remain within that same environment.
Documented06 / A practical first mapping
Start with a value you already copy.
Choose two Jira issues that need the same date or other shared value. Decide which one owns that fact. Create a mapping, change the source field, then inspect the receiving issue and the mapping views on both sides.
Field Echo is available through the Atlassian Marketplace. For setup details, compatible fields, permissions, troubleshooting, and FAQs, use the Documentation.
Help when you need it
01
Inspect the source and target
Check that the mapping exists, the source changed after creation, and the target field remains editable.
02
Review the console
Use recent error messages and mapping health to distinguish temporary failures from relationships needing attention.
03
Contact support
Include issue keys, timestamps, and application errors. Open the support portal or email support@alterisedge.com.
Field Echo for Jira
One source. Consistent information.
Keep related work aligned through explicit, one-way field mappings.