New Custom Fields automatically appear in Context Fields

[Janik]

Hey!

Whenever I create a new custom field it is usually only needed for one or two Request Types but it appears in all existing Request Types in the "Context Fields" area and absolutely clutters the issue view for the agents.

Is there any way to have this in the "Hide when empty" section by default or do I have to go through all request types of this issue type and manually move them down there? Everytime a new field is added?
This is so much work I feel like there has to be an easier way to do this but I just can't find it.

Since this is a Service Management project I don't have the "Issue Layout" option in the project settings do do it once per Screen.

So, is there any way to get what I need?

Thanks

[Jehan Gonsalkorale · Accepted solution]

Hi Janik, 

This is something we are actively working on. I understand the experience right now is not ideal, particularly when you have lots of request types sharing the same issue type (or, more accurately, screen scheme). 

We will be rolling out a change in the coming months where this behaviour will stop and fields will be hidden by default. 

Sorry for the inconvenience, 

Jehan Gonsalkorale

Product Manager, Jira Service Management

[Eli Devlin]

Hi @Jehan Gonsalkorale can you share any updates on this? From what I can tell, it's still quite troublesome. I've even noticed newly created custom fields appearing in Request Types that don't use the screen that I added them to during custom field creation. 

Thanks, 

Eli

[Vishwas]

Hey @Janik 

Welcome to Atlassian Community !!

Whenever a new custom field is added it goes to screen of the issue type. The request types are created against an issue type, so that is why any field added to issue type screen will be available to all request types associated with it.

So only option is to go to request type and remove them. I know its bit tedious and can't think of any solution.

Regards,

Vishwas

[Janik]

Thank you for your response, even though it is not the answer I was hoping for. With dozens of request types that's not really something feasible to do every time a new field is added and it severely impacts the agents' experience.

[Vishwas]

hmm, I understand your concern. This is something everyone would like to have but as of now it's not there yet. Maybe somewhere down the line Atlassian Team could pick up and suggest on this