Custom field with default value appears on all request detail view

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.

KR

2 answers

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

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.

 

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

OK - here one example:

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

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

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

0 votes
Joe Pitt Community Champion Jul 06, 2017

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. 

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

 

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

27,037 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you