Example of a Task: In general, creating a “Subscribe for a newsletter” component and adding it to a website is a Story. A Task for it would be to embed a Mailchimp subscription form. Implementing and validating it would also be a Task. Jira Epic vs Story vs Epics . As mentioned earlier, Epics are great for grouping Stories. Rising Star. Jul 13, 2017. You can modify the "Issue Type" to call it Epic /Feature/etc. To have a kanban board focus on Epics only you can set a filter on the board to only look at those issue types. You can also use "Quick filters" to further filter the board while viewing it. Editing issue types: At step 1, take subtask's parent's epic link and store it into a text custom field (I called it EpicLink (temp) as I'm not keeping it for long) as a step 3, run a new automation script on the tasks and update the epic link using the content of the EpicLink (temp) field. This works, absolutely not elegant but does the job Confluence will then automatically generate a Jira Roadmap macro. ii) Use the macro shortcut menu: From the macro shortcuts menu in Confluence, simply select Jira Roadmap. iii) Pull up the macro menu: From the full macro menu in Confluence, select Jira Roadmap. Note: These steps are for Advanced Roadmap. How can I automatically change all the tasks' statuses from all the tasks "inside" an Epic based on the Epic's status? Example: if I have 3 tasks with "to do" status, but I decide to put the entire Epic as "On Hold", all those tasks would also move to "On Hold". The trick may be to restore the former statuses when I place the Epic as "In The feature’s Points field in Jira Align would sync with the Story Points field on the Jira epic. Note that Jira Align features (Jira epics) have story points in Jira Align that is a rollup of children stories LOE. Jira Align does not sync this field with Jira epics; it syncs the feature’s Points field which is a separate estimate. Trigger: sub-task updated (you may want to make this more specific) Condition: issue type is sub-task; Branch: for jql: key = {{issue.parent.Epic Link}} Action: the action you want to take; This will edit the Epic of the parent. Hope that is what you were after. Cheers, Nick For Sub-task, Copy "Parent Epic Name" from Parent Issue to Sub-task's "Parent Epic Name" field. What I did and didn't work: 1. create a new text field 'parent epic name' ) to Story and Sub-Task screens. 2. add an automation for when an issue is edited, the issue field parent epic name will be copied from the parent issue, field epic link. ax74u.