Field Echo automatically synchronizes field values between related Jira issues. Create a mapping once and Field Echo monitors updates, keeping connected issues aligned without manual effort.
Field Echo automatically synchronizes field values between related Jira issues. Instead of manually updating the same information in multiple places, administrators and teams can create field mappings that keep connected issues aligned automatically.
Field Echo is designed for situations where information must remain consistent across multiple issues, projects, or teams. Common examples include synchronizing due dates, priorities, custom fields, milestones, and reporting data.
Field Echo follows a simple process:
Once a mapping is created, synchronization occurs automatically whenever the source field changes.
Field Echo mappings are created directly from a Jira issue using the Field Echo panel.
Each mapping connects a source field on the current issue to a compatible target field on another issue. Once saved, changes to the source field are automatically synchronized to the target field.
Once a mapping is created, synchronization occurs automatically whenever the source field changes.
The new mapping becomes active immediately and will begin synchronizing when the source field changes.
.png)
Field Echo only allows mappings between compatible field types. The field selectors automatically filter available options to prevent invalid configurations.
Examples of supported mappings include:
If a field does not appear in a dropdown list, it is either not editable, not compatible with the selected field, or not available to the current user.
Field Echo validates permissions while mappings are being created.
Users can only create mappings to issues and fields that Jira allows them to access and edit. If a destination issue is not available for synchronization, Field Echo prevents the mapping from being created.
This ensures mappings are valid before they are saved.
Existing mappings are displayed in two tables:
Outbound Mappings
Inbound Mappings
To modify or remove a mapping, navigate to the source issue that owns the mapping.
.png)
The Field Echo Console provides a centralized view of all active field mappings across the Jira instance. Administrators can review synchronization relationships, monitor recent failures, and remove mappings when necessary.
The console is available from Jira Administration → Apps → Field Echo Console.
.png)
Field Echo records recent synchronization failures in the System Error Log.
Common entries include:
Error messages are presented in a human-readable format to simplify troubleshooting.
Mappings that encounter a permanent 404 Not Found error are marked with an ERROR status in the console.
This typically indicates that the target issue has been deleted or is no longer accessible.
Administrators can remove any mapping directly from the Field Echo Admin Console.
Removing a mapping immediately stops future synchronization and removes the relationship from both issues.
Field Echo is designed to operate within Jira's existing permission model and does not introduce additional access paths to issue data.
When creating a mapping, Field Echo validates access using the permissions of the current user.
Users can only create mappings for issues and fields that Jira allows them to view and edit. Fields that are unavailable, incompatible, or restricted by permissions are automatically excluded from the selection lists.
After a mapping is created, Field Echo performs synchronization using the application's permissions.
This allows mapped issues to remain synchronized regardless of which authorized user updates the source issue.
Field Echo stores only the information required to maintain field mappings and synchronization relationships. All information is stored locally within the instance.
Stored data includes:
Field Echo does not export Jira data to external services.
Synchronization failures are logged and displayed in the Field Echo Console to assist administrators with troubleshooting.
Permanent failures, such as deleted target issues, are clearly identified so corrective action can be taken.
Verify the following:
Field Echo only displays fields that are:
If a field does not appear, verify that the field exists and can be edited in Jira.
Field Echo only allows mappings to issues that the current user can access.
Verify that you have permission to view and edit the destination issue.
An ERROR badge typically indicates that the target issue no longer exists or cannot be reached.
Review the System Error Log for additional details and either correct the issue or remove the mapping.
Deleted mappings cannot be restored. Create a new mapping to re-establish synchronization.
Yes. Field Echo supports compatible Jira custom fields in addition to standard Jira fields.
Yes. Mappings can be created between issues in different Jira projects, provided the user has the required permissions.
Yes. Multiple fields can be synchronized between the same source and target issues.
No. Field Echo uses one-way synchronization only. Changes flow from the source issue to the target issue.
No. Field Echo operates independently and does not require Jira Automation rules.
No. Field Echo includes loop-prevention safeguards and will block mappings that would create circular synchronization paths.
No. Field Echo only synchronizes the fields you explicitly map.It does not modify workflows, permissions, issue security schemes, or project configurations.
Administrators can view all mappings from the Field Echo Admin Console.The console also provides access to recent synchronization errors and mapping management tools.
