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

Unsure How to Populate Child Issues within Theme-Schema

mummareddy supriya

Within the theme as configured in PDS EDF 2.0 schemas, how do I populate issues under the Child issues header (see below image)? I am hoping we have an approach to pinning various issues types to themes, similar to using epic link to pin issues to epics. Whatever approach we can use will help in tying together the various levels of milestone planning.

I did try using the parent of/child of linkage, but this added a separate header with links, as expected

Accepted answers

All comments

Walter Buggenhout

Hi @mummareddy supriya,

Can you be more specific about what you are trying to achieve here? The image you refer to is not attached and your question is quite vague.

Happy to help if you could present more details about the problem you are trying to solve and the challenges you are facing.

mummareddy supriya

whenever I'm connecting a theme to an epic.Epic is the parent of right, and theme is the child of it.but why does this theme not fall under "Child Issues"?

mummareddy supriya

whenever I'm connecting a theme to an epic.Epic is the parent of right, and theme is the child of it.but why does this theme not fall under "Child Issues"?

Walter Buggenhout

Hi @mummareddy supriya,

You are creating an issue link between the issues. Even though the link type may be named Parent of, it is just a relationship between the two. You could have just named Parent of something like has something remotely to do with and you would see the exact same result.

If you want to create a real parent-child relationship between 2 issues in Jira, you need to use the Parent field on an Epic to it a child of a Theme, and thus add the parent theme issue in the parent field of the Epic, to be very precise.

But: you need to be on a Jira Software Premium plan to make this work. And, you need to specify theme as a hierarchy level above the epic in order to actually map it as a parent level above epics.

Since I see you have Structure in your environment (from your first screenshot), I would not be surprised if you are not on a premium plan and you / your organization has made the choice to use structure instead to extend your hierarchy. This is a marketplace that would indeed allow you to create custom hierarchies based on issue links in Jira. But if that is the case here, you should look into the Structure section on your issue to see if the parent / child relationship is being displayed.

mummareddy supriya

@Walter Buggenhout I appreciate your solution and your thorough explanation.

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