Update the parent issue when a sub-task is updated; Comment on linked issues when an issue is resolved. Smarter smart-values! But wait there’s more! Smart-values got even smarter! You can now also easily get access to a parent or epic’s data via: {{issue.parent.fields.some field}} or {{issue.epic.fields.another field}} The link I included for the epic has a pretty good example of what an epic is. Components are used to break down your project into smaller parts, one example is that you use teams as components. You can then set the component lead to your team lead and automatically have an issue assigned to him/her when a new issue is created. Epics. When issues share a theme across projects and milestones, you can manage them by using epics. You can also create child epics and assign start and end dates, which creates a visual roadmap for you to view progress. When your team is working on a large feature that involves multiple discussions in different issues in different projects in Create an issue from Jira issues macro: Jira 4.3: Any: Create issues by highlighting text on a Confluence page: Jira 6.3.1: Any: Create issue by highlighting text on a Confluence page and automatically link issues to an epic : Jira 6.3.1 and Jira Agile 6.3.5: Classic projects only: Link and create Confluence pages from epics and sprints : Jira The concept of Epics are pretty amorphous and undefined. You can find descriptions of Epics as large user stories that need broken down and in that regard, it is common for some to try and squeeze them into a release train window. For instance an Epic may be a container for a specific measurable outcome. Implement the Mastercard API. Jira cloud. Diagnosis. The field 'Epic Link' on the child issue should be matched with the 'Epic Name' from its parent, but this mapping is not directly supported under Automation action. The available options are Copy from issue/Copy from parent/ Copy from Epic/ Copy from trigger issue, but these options are only for 'Epic link' not 'Epic Name Epic hierarchy level – Epic issues in Jira are mapped to the epic hierarchy level by default. Epic issues are the byproducts of higher-level priorities being broken down into smaller and more manageable chunks of work. Epic issues can span multiple sprints in a project, and are comprised of multiple stories. Story hierarchy level – Story Jira issue table allows you to visually manage issues placed inside a 2-dimensional grid where X & Y correspond to Jira parameters, i.e., effort & impact or team & sprint. Pro plan only Confluence macro @Aline Chapman It is possible to rename "Epic" issue type to "Feature" in Jira Cloud via Administration->Issues->Issue Types->Epic; click on three dots, which shows "Edit". In order to do that one should have Jira Admin access. Renaming is a global change (Configuration), it would impact all Jira projects in that Jira Cloud instance. Issues are the basic unit of work in Jira Software and come in various types: story, task, bug, etc. There are two additional issue types - epic and subtask - that can possess a hierarchical relationship with the aforementioned standard issue types. Let's run through some quick definitions. An epic is a large work item made up of subsidiary eOtjHh.