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?

[Natalie Hobson · Accepted solution]

You could also create a new role if you prefer that to adding a group:

https://confluence.atlassian.com/display/JIRA/Managing+Project+Roles

[Ravi Shah]

I was able to add a default watcher by simply creating an automation rule at the event (trigger) of New Issue Created, followed by certain conditions which are called components in automation rule config. No Plugins are required to do so and we can choose this rules at global level or at project level as well.

HTH :)

[Jobin Kuruvilla [Adaptavist]]

I think Bug watcher plugin does this. We used to use a Component Watcher plugin too which watches components.

Howveer, you can probably get the same watcher functionality by adding groups directly into notifications provided you can create a new notification scheme for the project. This becomes painful if you want this functionlity for all projects and that is when the plugins will help!