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

define specific child issues for a "project" issuetype

Bert Duhamel

In a specific protfolio Jira project, I'd like to create specific child issues per issue (of the type "project")
The child issues are specific project related issues that are only to be used in the portfolio jira-project.

The child issue-types are "project risk/project decision and project issue". How should I create this mother child relation in only my portfolio project directly linked to the project that are created in there?

Accepted answers

Walter Buggenhout

Hi @Bert Duhamel,

The hierarchy relation between issues in Jira is defined centrally in Jira settings > Work items > Work type hierarchy and spans your entire instance. In short: any parent-child relation you create is not going to be limited to a single project.

If you want specific work types to be available in a single project only, that will have to be defined by the work type scheme associated with that project and that project only.

You know where / how you can reach me, so happy to help if you need assistance 😊

Hope this helps!

All comments

Walter Buggenhout

Hi @Bert Duhamel,

If you want specific work types to be available in a single project only, that will have to be defined by the work type scheme associated with that project and that project only.

You know where / how you can reach me, so happy to help if you need assistance 😊

Hope this helps!

Bert Duhamel

Thanks Walter, I understand that this child-parent relation between issues needs to be managed in issue hierarchy.
In our current config we have defined the following hierarchy : Project - Epic - standard issues.
in this particular portfolio project (in which we use the issue type "project" as a default, we would like to be able to use these 3 specific issuetypes directly under project.
Should a create an intermediate hierarchy then between Project and Epic?

Walter Buggenhout

When you are just looking at the hierarchy aspect of the initial question, you would have to add your new issue types at the epic level in your hierarchy configuration.

If you add a level in between project and epic, that would break the parent-child relationship you currently have between existing projects and epics. So don't go there. If you add the new types at the same epic level, also be aware that they won't be available anywhere else in your site at a different level.

On a final note: it seems you are trying to implement a solution for overall risk management and decision tracking for projects. Atlassian has other ways of managing those built in already in its platform experience, as you can see here:

Screenshot 2025-05-12 at 08.22.04.png

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

jira-cloud-administration

not-applicable