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; } } }

Creating a parent issue type but not just for epics ...

Heike Ellwood

Hi -

My team uses an issue type called 'Requirement' which leads to different types of work: epics, stories, defects etc. So basically, there is not always an epic between Requirement and Story.

Ideally I would like to configure a custom field in each of the downstream issue types (epic, story, task ...) that works like a parent field for requirement.

So basically, a parent field that has a Requirement dropdown in epics, but the same field in stories and tasks.

Is there a way to either configure this or write a JQL query as a basis for a customized dropdown field?

PS. I would like to avoid using links as there are a lot of links to choose from ...

Thanks!

Accepted answers

All comments

Trudy P Claspill

Hello @Heike Ellwood

Welcome to the Atlassian community.

While it is possible, with third party apps, to create an Issue Picker field that you could configure to show a list of issues based on a filter, Jira would not treat that information the same way it does the built in Parent field.

Jira Cloud does not provide an Issue Picker custom field type natively, so adding such a field would require a third party app. Here is a search from the Atlassian Marketplace that will help you get started finding such apps.

https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=issue%20picker%20field

John Funk

Hi Heike - Welcome to the Atlassian Community!

Why are you doing a Requirement issue type at the top level and not just linking the issue to the appropriate level of issue? Then you can avoid having to have something in the middle.

Heike Ellwood

Hi John - sorry, I don't understand the question. There is a need to track requirements as stand-alone entities with a workflow, Requirements lead to work (epics/stories etc.). That's why I thought a hierarchy might work best. If we start linking issues, they currently have 100 different types of link available - how would you then report on what work goes with what requirement?

Heike Ellwood

Sorry ... thank you for replying BTW! :-)

John Funk

Why in the world would you have 100 different types of links??? Create an issue type called Requirement if you want. Then create an issue with that issue type. Then create your Epic or your Story and link it to the Requirement - using Relates to or something like that. You don't need to be that description with the links. You know its a requirement because it uses a Requirements issue type.

Heike Ellwood

Thank you @Trudy I'll look it up!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud