How to identify the original "Epic" type via the REST API

[James Sear]

I was wondering if anyone knows whether it's possible to identify the original special "Epic" issue type via the REST API.

I've found that it's possible to rename Epic to something else, meaning that via the API, I can't identify which issue type is the original "Epic" type.

I have tried the following APIs:

• Get all issue types (/rest/api/3/issuetype)
• Get all projects (/rest/api/3/project/search)
• Get issue type (/rest/api/3/issuetype/{id})

Each provides the same issue schema back:

{
  "self": "https://api.atlassian.com/ex/jira/262560a0-5ce0-4e72-990e-62464cbb26e6/rest/api/3/issuetype/10000",
  "id": "10000",
  "description": "A big user story that needs to be broken down. Created by Jira Software - do not edit or delete.",
  "iconUrl": "https://jpsear1.atlassian.net/images/icons/issuetypes/epic.svg",
  "name": "Renamed Epic",
  "subtask": false
}

Unfortunately, there is no where to tell this is a core "Epic" type. Any ideas?

[Federico Rela]

issuetype not in subtaskIssueTypes()

[pelizza]

Great answer, but not for this question 

By the way, it helped me on another situation...

[Jeret Shuck]

Great answer! First click, first thing that worked for me. 

[Jobin Kuruvilla [Adaptavist]]

JQL Tricks plugins has a hasSubtasks method which you can use in this query. It is a commercial plugin, btw!

[Russell Howe]

Yeah, I saw that. This isn't a problem which is worth any money to me, unfortunately.