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

Custom field with default value appears on all request detail view

Pierre Keutel

Hello,

I have an issue with custom fields where the default value is set.

In fact I have 2 fields where a default value is set for a special request type. When a customer opens another request type which does not include those fields these are nevertheless shown in the request detail screen (in the backend) for all other request.

Since I did not assign the fields to other request I do not expect that those fields will show up on other request types (as it is quite disturbing) since these fields do not have anything to do where they pop up.

Is there a config which I missed ?

Thanks in advance.

Accepted answers

All comments

Kedar Pepakayala

what is your main problem you want to remove the custom filed from that project

or want remove Automatic appear of field from the view screen

Pierre Keutel

I want to have the custom field only appearing where it belongs to. I try to give a more detailed example of my problem.

example:

custom field: primary mail -> default value "@example.com"

custom field is added to request type: "user creation"

when a request of type "intranet problems" (does not include "primary mail" field) comes in and I check the detailed view I can see description etc. but also "primary field" : "@example.com"

This should not be shown in the request as this type does not have the field attached. Either there is a bug or I missed some configuration.

Kedar Pepakayala

can you share with snapshot of jira with your problem you are facing

Pierre Keutel

OK - here one example:

1st pic shows the fields for this kind of request type

fields assigned for RebookingApp request.png 2nd pic shows request detail view with "not assigned" field (Primary Mail) rebookingApp request not assigned field.png

Joe Pitt

You say the request type doens't have the field attached. If you're thinking it doesn't appear on the create or edit screens that doesn't matter. It sounds like when you created the field you made it either global, for the issue type (inadvertantly perhaps), or for the project. It doesn't matter if appears on any of the screens, if it is defined for the issue type, project, or global it will appear in the details page when there is a value, default or set, for it. Go to the custom field and verify how it is defined.

Kedar Pepakayala

Check that field must be in both Field configuration and screen and it assingned for that request type or not

JiraSD support

I see this happens when a default value is configured, on a custom field

Maitreyee_k9eds7

Was this resolved, I am having the same problem

support for vo

Hello,

Was this resolved ?
I am having the same problem today ...

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

jira

jira-service-desk