JIRA Agile is supported as well on displaying epics, sprints and backlogs (SCRUM) or as KANBAN view grouping related issue status'. In both cases, you have to select your related agile board as shown below. Be aware of Atlassian's internal object model: a sprint is no longer just a custom field belonging to an issue as it was in older times of "Greenhopper" (original name of JIRA Agile before rebranding). Now, a sprint belongs to an agile view and an issue can be assigned to a sprint of an agile board. Thus, having multiple agile boards, an issue can belong to different sprints having a 1:n relationship and not a 1:1 as often assumed.
If you select an agile board (SCRUM or KANBAN) instead of a JIRA filter, you will get a Gantt-Chart as displayed below being grouped by epics, sprints and backlog or based on its Kanban status':
Alternatively, you can create a new JIRA filter having a JQL statement containing "ORDER BY epic-names" (depending on your language you have to adjust "epic-names"):
this will display aggregated sums of estimations and group by epics in order to support product owners etc. Additionally, epic's planned start/end date will be automatically adjusted to fit to min/max of assigned issues.
