nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can other issue-types appear in the GreenHopper 'Epics' panel?

Alex Taylor

Or to put it another way, what is it about the 'Epic' issue-type that tells GreenHopper to put it in this panel? It can't be its name, as I can rename 'Epic' to anything I like and it still works.

We have a need to set up two projects, one which uses an issue-type called 'Requirement' and one which uses 'Epic'. We would like to be able to have both issue-types show up in the 'Epics' panel on the Rapid Boards. Can it be done? :-)

We're on JIRA 5.2.4 and GreenHopper 6.1.1.

Accepted answers

Renjith Pillai

Not possible, the code picks up just one issue type in the property entry tables.

All comments

John Garcia

I can tell you that the magic numbers are stored in these property keys...

Alex Taylor

Sorry, I've no idea what I'm looking at there...

Renjith Pillai

Not possible, the code picks up just one issue type in the property entry tables.

Alex Taylor

Thanks, that's what I suspected :-(

Matthew Rowen

Are there any plans to fix this? We have a legacy project in Jira with issues that we'd like visible in the EPICs panel without having to convert the issues to the Epic issue type.

John Garcia

This is by design, so I don't anticipate it being changed.

Evgeniy Stepche3

Ok. Can we rename Epic for something else and assign custom workflow to it? Will it broke something?

Nic Brough -Adaptavist-

Apologies for the necro-post, but if people are still interested (and still happy to wait), see https://jira.atlassian.com/browse/GHS-9455

I'd still avoid renaming epics to something else, but a change of description, inline translation and changing workflows are all ok now.