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

How do I restirct the child issues an issue type can have for a project

Paddy Walsh_jgelqo

I think I am trying to achieve something simple but I really can't see how to do it?

I can see that issue type schemes indicate which issue types a project can have. But how can I restrict the child issue types that an issue type can have?

There seems to be the assumption that an epic can have any issue type as a child, but I have created some new issue types that I do not want to be children of an epic - and I do not want to be able to create a Bug as a child of an epic.

How can this be achieved? Given that you can create new issue types, there surely must be some way to restrict where they are used?

Accepted answers

Trudy P Claspill

Hello @Paddy Walsh

Unfortunately there is no feature specifically for restricting what type of issues can be children of Epics.

The native Jira issue hierarchy is

Epics
|-- base level issue types (i.e. Story, Bug, Task)
    |-- subtask issue types

When an issue type is created and made available in a project, Jira allows the issue type to be used appropriate to its place in the issue hierarchy.

To prevent a specific issue type from being made a child of an Epic you would have to implement work arounds to try to prevent it (for instance, a Validator in the Workflow Create Transition) or to try to undo the linkage after it was created (for instance, using an Automation Rule to monitor for Bugs being made child issues of Epics).

All comments

Trudy P Claspill

Hello @Paddy Walsh

Unfortunately there is no feature specifically for restricting what type of issues can be children of Epics.

The native Jira issue hierarchy is

Epics
|-- base level issue types (i.e. Story, Bug, Task)
    |-- subtask issue types

When an issue type is created and made available in a project, Jira allows the issue type to be used appropriate to its place in the issue hierarchy.

Paddy Walsh_jgelqo

Thanks @Trudy P Claspill .

I feared as much. Sadly we got Jira Premium on the basis that we could add additional issue types at the epic level but such issues are not really at the epic level as Jira allows you to create them as children of an Epic - very strange.

It seems that even though you can specify that new issue types are at the epic level they are still base-level issue types which is not at all what I expected.

Trudy P Claspill

I have not worked much with AR and the extended Issue Hierarchy so I decided to test this out.

When I add a new issue type in the Issue Hierarchy at the same level as Epic, I am not able to then make that issue a child of the Epic issue type.

Screen Shot 2023-06-23 at 9.06.49 AM.png

When I try to drag an Epic mark 2 type of issue into an Epic on a Backlog screen (for a Company Managed project), I get an error message and am not able to complete the task.

Screen Shot 2023-06-23 at 9.08.23 AM.png

Are you working with issues in Company Managed projects?

Can you provide some screen images or steps to recreate the scenario where you are able to add such an issue as a child of an Epic?

Paddy Walsh_jgelqo

Actually, I am not able to add such an issue as a child of an Epic. If I select 'Add a Child Issue' when in an Epic I see the new Issue type in the dropdown list - suggesting I can add it as a child - the create screen appears but when I submit it nothing happens - it just hangs.

I am using company-managed projects.

This seems a little buggy to me - surely if you can't add it as a child then it should not appear in the list.

For other issue types, I can add validators as you suggest but that means someone has to complete the whole create screen before they are told they can't do it. Would seem to make more sense if you could just define the allowed hierarchy.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud