Hi all,
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.
Thank you
Hi Paula,
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?
Best, Max
@Max Foerster thanks for your answer. You wrote "by default".
Does this mean there is a way to do it via admin configuration?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
Cheers,
JP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This request fits in perfectly with our needs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agreed - we could definitely use this
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same! This would help out team in a very big way. Essentially we need to add "project" placeholders in a Jira project so that we do not have to create a project board just to have this place holder. We would like to use epics for its indended purpose. AND show "Projects" or "Initiatives" on out timeline.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And it looks like my wish was granted... mostly. By mostly I mean only for Premium and Enterprise:
https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/
I wish features like these were more explicitly called out in the standard vs premium vs enterprise charts out there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just found that it is possibe to have multiple epic-level issues (I think, just found it. not sure if you can have more than just "epic" at the epic level... wording is confusing). And Jira PREMIUM has the option to have more than 3 levels of issues (so you can have issues above EPIC):
https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Will this be possible in the future? We also need this ability. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Paula,
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How do you do it?
I have tried and I only see the options that @Max Foerster - K15t mentioned so I'm not sure how can I add all the epic functions that I need.
Regards,
Paula
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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 :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would need to disagree with the statement that Jira is a fully customisable tool. As your statement is in fact saying that you actually cannot create a customised Epic. If you lose all the functionality of an epic-type issue - then the issue type is not in itself an epic.
If a project can have multiple workflows - then multiple epics should be allowed to be created for each workflow, as an issue type cannot be shared between workflows. This is very limiting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, Jira is very limited in case of using Issues like Epics..
Sol if you need a functionality to be Container of other issues, you could use Epic Sum UP(our App) on DC to add this functionality.
If you are looking for different use cases without changing the issue type, you can do:
- assign different worklfows per project (is somehow confusion)
- add a Custom Select field to add the Context of your Epic, which can then be reflected in the Name by automatic Summary changes, eg. Vacation-Epic, Project Epic.
Thats what we did before we added stacking functionality to our app.
hope that helps. Without addons, Jira is more or less straight forward to the Atlassian viewport of things ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
FYI this is also possible in DC now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Kindly wanted to ask, did you manage to create an issue type in Jira DC similarly to Epic's functionality? If so, can you share how please? Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looks like they've updated the feature offerings for Jira Cloud Premium and Enterprise accounts to allow for this functionality.
https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/
This was a pleasant surprise I found today.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does the new epic type show on the roadmaps?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.