Epic-Story Listeners provide synchronization between Epics and Stories.

A sample Epic-Story Listener Configuration page is shown below.

Settings

Listener Name

Provide a unique name to the listener.

Active

Check this checkbox if you want to enable the listener. If unchecked, the listener will simply will not respond to changes on any issues.

Project Name

Choose the Jira Projects in which the listener will respond to events. 

Issue Types

Choose the issue types on which the listener will respond to events or sync values to. 

Source Issue Jql (Optional)

Source issue is the issue that the update is made on and the event is fired on. 

If entered, the listener will only act on events on issues that match the given JQL.

Since any valid JQL can be used, Source Issue JQL setting provides great flexibility to filter source issues.

Target Issue Jql (Optional)

Target issues are the stories that are linked to the epic if the source issue is an epic; or target issue is the epic that story is linked to if the source issue is a story.

If entered, the listener will only sync values to issues that match the given JQL.

Since any valid JQL can be used, Target Issue JQL setting provides great flexibility to filter target issues.

Direction

Select whether field values will be synchronized from "Story to Epic", "Epic to Story" or Both.

Fields

Choose fields to be synchronized between issues. Both system and custom field types are supported.

Append

The Append option makes the listener append source field values to the existing values on target. If selected, the values on source issue will be appended to the the existing values on target issue. If not selected, the values on the source issue will be overwritten to the values on the target issue. This option is available on multi-select system and built-in custom field types. Custom field types introduced by other apps are not supported yet.

Service User

Choose whether you want to use a Service User for the sync. This options is particularly useful when the user(s) updating source issues may not have view or edit permission on target issue(s). 

If a Service User is configured, the listener will search for and update target issues with Service User's account. Target issue history will show that the issue was updated by the Service User.

If a Service User is not configured, the listener will search for and update target issues with the user who updated the source issue. Target issue history will show that the issue was updated by the user who updated the source issue.

Sync on Create

If selected, field values will be synced between Epic and Stories according to sync direction when stories are first created (If the sync direction is Bidirectional, syncs values from Epic to Story).

Does not respond to create events on Epics since an Epic cannot have Stories when it is first created.

If not selected, only updates on the issues AFTER the issues is created will be synced.

Sync on Move

If selected, field value will be synced between linked issues according to sync direction when an Epic or Story is moved from one project to another.(If the sync direction is Bidirectional, syncs values from Epic to Story)

If not selected, listener will not respond to move events but sync might still occur since an update event might also be fired if fields are updated in the process.

Sync on Link

If selected, field values will be synced between Epics and Stories according to sync direction when a story is linked to an Epic (If the sync direction is Bidirectional, syncs values from Epic to Story).

If not selected, listener will not respond to link events.

Allow sync on not editable issues

Check this checkbox if you want the listener to ignore "jira.issue.editable = false" property of workflows and update not editable issues.