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
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.
Read more here:
HI @Alex Koxaras _Relational_ I am using different request type but same screen
is there anyway without changing the screens ?
BR,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
NO, Iam using one issue type for each request but only screen is shared with all request types
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you don't have scriptrunner installed then you have to create separate screens (and screen schemes) for separate issue types which will be associated to separate request types. The links I've pasted on my previous comment should be enough to help you with that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.