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

screens and Select List (single choice) default value

Mohamed Saad Taha

Dears,

I have different requests sharing the same screen and when I add Custom filed Select List (single choice) used in one request and configured default value I found this filed appear in other request with the default value although it is no configured in the other requests

how can I solve this other than creating different screens

Thanks

Accepted answers

Alex Koxaras -Relational-

Hi @Mohamed Saad Taha

You have to create request types using different issue types. For these issue types you have to to create separate screens and screen scheme. In these screens you will choose all the necessary fields.

Doing all the above will result in having different fields for your different request types.

All comments

Alex Koxaras -Relational-

Hi @Mohamed Saad Taha

Doing all the above will result in having different fields for your different request types.

Read more here:

Rilwan Ahmed

Hi @Mohamed Saad Taha ,

Create a field context for that particular custom field, set default value in it and then map it to required project and issue type only.

Remove the default value from general field context. It will be get auto mapped to rest all of the projects and issue type

https://confluence.atlassian.com/adminjiraserver/configuring-custom-field-contexts-1047552717.html

Alex Koxaras -Relational-

@Rilwan Ahmed if that field appears on the rest of the request types, this mean that all request types are using the same issue type. So field context will do nothing.

Mohamed Saad Taha

HI @Alex Koxaras -Relational- I am using different request type but same screen

is there anyway without changing the screens ?

BR,

Alex Koxaras -Relational-

If you are using the same issue type for X request types, then no. To all these X request types this field will be visible and applied with the default value.

Alex Koxaras -Relational-

Now that I'm thinking of it, you could use script runner's behavior to change default values and hide the field from any request type. Do you have this app installed?

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-server

jira-service-management

jira-service-management-server