Agile teams are used to group work under bigger chunks called epics. These are particularly useful to communicate and coordinate between teams since epics are generally feature-oriented, and hide the minutia of implementation. You can read more about JIRA epics in their knowledge base.
Unito fully supports epic synchronization in applications such as JIRA.
Epics are treated as parent tasks: any task or issue grouped under an epic will be synchronized as a subtask of the epic. You can add, remove and move tasks from epics, letting you plan those epics from outside JIRA. You can even create deeper hierarchies using both epics and subtasks.
An epic and its issues in JIRA
The resulting tasks and subtasks in Wrike
To enable epic support, edit your sync and enable the “Sync subtasks and epic hierarchies” setting under the JIRA filters section.
Sync settings -> JIRA -> Filters
The following special cases are not supported at this time.
Multiple parent epics: in some apps (Wrike for example), a subtask can have multiple parent tasks, whereas JIRA only allows one parent epic per issue. To keep a seamless synchronisation, refrain from assigning multiple parents to synced subtasks in apps like Wrike.
Parent epic outside project: JIRA lets you associate an issue to epics outside the project. In this case, we will simply ignore the parent epic, and the issue will sync normally.
Convert from parent epic to parent task, and vice versa: JIRA does not allow the conversion between “sub-tasks” and full issues linked to an epic. So in another app, if you move a subtask from a JIRA epic parent to a JIRA non-epic issue, the move will not synchronize.
Available on more apps very soon: The epics synchronization is currently available for JIRA-Wrike syncs only. We are working on making it available for all of the other combinations of apps, such JIRA-Asana which has been a particularly popular demand. Stay tuned!