Show issues of only one type in hierarchy report

[pat d-o]

Hi Folks,

I have an AIO Hierarchy report of type Epic -> Issue. By definition, it lists all the issues pertaining to listed epics, so I get something like that:

Epic 1

- Story 1

- Story 2

- My Issue 3

Epic 2

- Bug 1

- My Issue 4

I would like to filter further the issues and show only those of a specific type, so that I get something like:

Epic 1

- My Issue 3

Epic 2

- My Issue 4

Is there is a way to do it?

take care

pat

[Petter Gonçalves]

Hello William,

I think that maybe you have misunderstood how the request type feature works.

Request Types are required to create issues through the Customer Portal, while you can create issues without a request type internally on JIRA.

In order to allow a request type to be selected for a specific issue type once it's created, you must map them in the Request Type page.

Let's suppose you have an issue type "Task" and you want to create it internally with no request type and then set the request type as "Problem" posteriorly.

To add the Problem request type as an option when editing the issue, you will need to properly map the request type problem with the issue type task in the Request Type page.

Please, check the documentation below if you need more details about it:

https://confluence.atlassian.com/get-started-with-jira-service-desk/create-service-desk-request-types-917968307.html

[William Wynn]

When setting up Request Types, I can't seem to select an issue type that is a sub task issue type. Is there any way to support sub-tasks issue types in a service desk project?

We're able to manually create an issue and tag it with a sub-task type, but then it becomes impossible to edit that issue because the request type is a required. Alternatively is there a way to make the request type no longer a required field when editing a case?

[Petter Gonçalves]

Hello William,

You are correct to say that Request types are not available to be mapped to sub-task issues. As you can see in this documentation, sub-tasks can only be used on the backend for internal discussions and can not be used to interact with customers in the portal.

Also, we have a feature request opened to map Sub-tasks to Request Types:

- Sub-tasks as an applicable issue type for Requests

However, Request Types are not required fields. Can you confirm if you are not using another custom field with the same name?

In fact, you can simply remove the field Request Type from your sub-task screens so you can work with this internally and edit the sub-tasks as you need.

[Nic Brough -Adaptavist-]

You don't.  I'm afraid this is not possible in Jira.