nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can you tell if an issue is an epic?

Oscar Goldman

I can't see anything in the UI that identifies an issue as an epic. I even searched the whole issue-detail page for "epic" and got zero hits.

Accepted answers

All comments

Dirk Ronsmans

Hi @Oscar Goldman ,

Normally it should show it as an Icon on the top of the page next to the issue key.

If you hover over it will also show the issue type/work item type.

Could you perhaps share a screenshot?

Bharat Kumar Bondalapati

Hello @Oscar Goldman

Welcome to Atlassain Community!

As requested by @Dirk Ronsmans , please share screenshot to assist better

Evgenii

Hi, @Oscar Goldman

Welcome to the Atlassian Community!

It's actually quite simple — the Epic issue type will always have the name "Epic" , as Jira doesn't allow you to create another issue type with that exact name.

To quickly check the issue type, just hover your mouse over the issue icon , and it will show you the full issue type name.

Oscar Goldman

Thanks for the replies! Here you go:

Not that icons alone would ever be an acceptable issue-type indicator, but what you see depicted here is two different document types (the parent of this document is a different type).

Oscar Goldman

Thanks! But there's no "issue type" field displayed anywhere I can see.

Hovering over icons isn't really a practical means of identifying issues... aside from the obvious problem of being almost totally undiscoverable.

Bharat Kumar Bondalapati

Hello @Oscar Goldman

The way to identify the issue type is by looking at the "Icon" as each Issue Type has a different icon.

In your case, as @Evgenii mentioned, hovering over the icon should display the type of issue.

Mathew Lederman

@Oscar Goldman you're absolutely right, it is nearly impossible to find if you don't know where to look. Atlassian made this change with the New Jira Issue View and unfortunately, the team decided to ignore the >350 votes on the Feature Request to bring the issue type names back. They provided two workarounds:

Workaround 1: Hover Over the Icon

In the New Issue View, users can hover over the Issue Type icon to reveal a tooltip displaying the Issue Type name. This ensures that users who need clarification on the Issue Type can easily obtain this information without adding clutter to the interface.

Workaround 2: Use an Automation Rule to Populate a Custom Field

For users who prefer the Issue Type name to be explicitly displayed, a custom field can be configured through Jira's Automation functionality. The process is as follows:

Create a Custom Field:

- Go to Settings > Issues > Custom Fields.
- Create a new text field, such as "Issue Type Name."

Set Up an Automation Rule:

- Go to Project Settings > Automation and create a new rule.
- Use the trigger "Issue Created".
- Add an action "Edit Issue Fields".
- Set the "Issue Type Name" field to populate dynamically based on the Issue Type (e.g., using {}{{issue.issueType.name{}}}).

Apply as a Single-Project Rule:

- To avoid exceeding the monthly rule execution limits, configure the rule to apply only within a single project. This ensures unlimited executions and localized management.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

epic