1

We already have set of IssueTypes and are following Agile Scrum.

Now, we're planning to use JIRA Agile. It is mentioned in JIRA Documentation that EPIC is an issue of Type "Epic". But, since we're a considerably sized BU with few projects - we would like to use the "New Feature" Issue Type as Epic - so the Spec, Dev and Test can be added to the "Feature" Epic.

Question is: Is it possible to use Custom Issue Type as Epic in JIRA Agile? If so, How?

Nuwan
  • 1,226
  • 1
  • 14
  • 38
R Kaja Mohideen
  • 909
  • 1
  • 8
  • 24
  • Not sure if I understand the use case correctly but I'm just curious why you don't want to use Epic issue type and convert issues with type New Feature from existing projects to Epics? – Adam Jan 21 '16 at 17:25

2 Answers2

2

Short answer is no.

The Epic issue type (and a few others) are added to a base JIRA installation when you install the "JIRA Agile" extension/plugin. None of the features (Epic Links, Epics filtering on backlogs, Epic burndown charts, etc) will work with any other issue type.

I'd suggest you begin adapting your process to use the new issue type.

Now, there's nothing stopping you associating custom fields (if that's what you use for Spec, Dev, and Test information) with the Epic issue type so you get the same functionality you have with New Feature.

kdopen
  • 8,032
  • 7
  • 44
  • 52
0

You can rename the Epic type created by Jira Agile (note that already created schemes remember the old name) to any name and it works.

I guess, there would be hack in DB and reassign issue type to Jira Agile somewhere in DB but who knows what tables are linked to see some description here

balderys
  • 1