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

show specific fields for that specific issue type in Jira Service Desk (backend)

Meytal

I created a service desk project with a kanban board so it would be easier to see the requests coming in.

I have multiple issues types, in which each issue type should have specific fields (many custom).

I added the fields and assigned them to the specific screen.

The thing is, in the Customer Portal, all the fields are placed correctly for the specific request.

Two issues:

1., When I try an open a request via the Jira Service Desk itself, i see all the fields from all the issue types.

2. When I view the issue that was created, it shows me ALL the fields from all the issue types.

I want to show ONLY the specific fields for that specific issue type when I create & view through Jira Service Desk Backend.

What am i doing wrong?

In the below, i should NOT be seeing anything "optimail"

add fields.jpg

Accepted answers

All comments

Bastian Stehmann

Hi @Meytal

So you created a screen for each issue type? Then it should show only the fields on that screen.

That it works correct, you have to add the screen to a screen scheme, and the screen scheme to an issue type screen scheme.

https://confluence.atlassian.com/adminjiracloud/associating-screen-and-issue-operation-mappings-with-an-issue-type-776636504.html

Meytal

The thing is, i am seeing all those TABS and the fields that are NOT related to that specific issue when I view the issue within the service desk backend (see screenshot above).

In the last screenshot, i should only be seeing General Details + Sandbox API Details. The Optimail should not be there as it is associated to a different issue type.

Hope this makes sense.

Meytal

By the way, i think the problem i am having is that i can't associate an Issue Type Scheme to more than one Project.

For example, if u look in this screenshot, the issue types are correct.

1. For Create an issue, if I could add the field "Request Type" to choose that should help show the correct fields for a specific Request Type i created.

2. For view, i have Request Type, but it still shows ALL the fields, including the irrelevant tabs.

Meytal

I think the problem is that I have all the fields in one Screens, then I got to Request Type and I see all the fields which is great, but then when I View the incident in the backend, it shows me ALL the fields for that particular Request Type/Issue which is not good.

This is what I see now in Request Types->Issue Type->Optimail Request.

I would have wanted to see ONLY this Screen for the Optimail Request Issue type under Request Types->Issue Type->Optimail Request.

Instead i see the above above "PISD: Jira Service Desk Screen"

Meytal

Thanks Bastian for solving my issue! I truly appreciate your response time, patience and professionalism.

For those interested:

Went to Issue Type Screen Scheme configuration page.
There I went to my Service desk Issue Type Screen Scheme assigned to my project
Clicked configure for this scheme
There i can see the Default is Screen Scheme is configured
What we did is to add the new Issue Type and assign the new Screen Scheme to it (the button for this is on the top right) with that Issue Type Screen Scheme

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-desk-cloud