I would like to have a new issue type called " A " and it should have the exact same functionality as Epic Issue type except the name.It is a needed functionality for us. People tend to be confused by the "Epic" name, and we cannot just changed it, as it's used in many projects.
What would you recommend?
Reference to : https://jira.atlassian.com/browse/JSW-7203
You can't add a new Epic type. The best alternative would be a specific Issue Link.
We have the Structure plugin, and that allows us to set a hierarchy of issues based on epic links (an epic contains its stories), but also based on specific issue links (stories contain other stories from other projects).
For instance, we use a project as a Portfolio in which we have Epic and Feature issue types. We use an implemented by/implements issue link to link our Features with Epics from Development projects, which are run in scrum boards. These development Epics also have Stories which have Subtasks.
So within Structure, that gives us a 5-level hierarchy. You can have as many levels as you want, the estimates are summed up in special estimates fields in the parent issues.
That's the original, non-duplicate issue from your reference. Creating hierarchies with issue types other than Epic>Story, that's basically what Structure does. I wouldn't count on this feature being added to JIRA Software (Agile) anytime soon.
It's a good plugin, very powerful but a bit pricey, and it's not exactly easy to configure the synced filters. I think you should give it a go with a 30-day trial.
Do you know if it is possible to change the field scheme associated with "Epic" issue types without impacting the work of other groups that use epics? I would like to remove some of the extraneous fields that have been added for other teams in the global Epic issue type.
Yes you can. In most respects, Epics are issues like the others, so they can be assigned their own Screen Scheme.
You might want to specify different field behaviors, like which fields are mandatory, with a specific Field Configuration for your Epics
Once you get used to the concept of Schemes and Issue Type Schemes, you can easily configure different issue types to behave completely differently from one another. Just a bit of advice though, try and keep the customizations to a minimum and re-use screens as much as you can. It quickly gets out of hand as your instances grows and users want things done in a very specific way.
I just read you Answer Above . Actually, I also want to create customize Hierarchy levels in JIRA Itself so I am using Portfolio plugins for creating Hierarchy levels. The problem I am facing right now is that I am not able to add Epic (by default) in the Level List. Please find the image below.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG