You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have seen this is not possible but all articles related are from a couple of years ago and I'd like to be sure this is still not possible in version 7.13.
the articles are still correct. Epics are in a way unique but still a standard-issue type introduced and utilized by Jira Software.
You only have two different types of issue types in Jira - standard issue types and sub-task issue types. Creating another entity similar to an Epic is not possible by default.
Does this answer your question?
If I could put anything on a wish list, it would be to make Epic a level as opposed to a static issue type, and give people the ability to create custom issue types. We're not all admins on all instances, folks. We can't just poof an "Epic Type" single select list field into existence like Zeus creating Athena.
Custom Epics would be excellent for Business Operations teams beginning to adopt the software as well.
I work a-lot with the music industry and there are many types of mini projects/efforts related to Songwriters, Composers or Catalog Aquisitions at the Epic Level, w/ Standard Issue Types then Subtasks to pull off what's needed for the work to get done in a three tier nested work hierarchy. Getting the businesses head around the issue type is an "Epic" -when that's the top tier that I can nest Std issues into doesn't make a lot of sense to anyone.
We should as admins be able to create a Custom issue type the BEHAVES like an epic - but isn't an actual "Epic" to keep the Agile swarm at bay. It's about nesting of work in a hierarchical structure. w/o getting them to understand custom linking, etc...
Jira is fully customizable tool as per the customer requirement. Further regarding your question, yes you can create the custom Epic Issue type within your instance. But most of the EPIC issue type needed functions will be limited. You will loose the Epic link, Epic color, Epic status etc functionalities for the custom Epic Issue type, those are by default comes with Jira System EPIC issue type.
Hope this is clear for you.
@Tushar.Kamble - that's unfortunately just renaming, not creating a new issue type at that level.
No matter what happens, there will only be one issue type at that level in the hierarchy. Its limiting, and its disappointing.
I know, someone will say something something methodology something something rules etc.
Not everyone drank that Kool Aid :)