How are others managing custom fields with request types?

Matt Harford

Hi There, 

We are using JSM Cloud and for the last several months have been building out forms / request types as we move more of our work over. 

I'm wondering how others are managing new custom fields? 

If we add a new custom field, and associate it to the screen scheme for our default issue type, it shows up in every single request type context view which is a huge pain - it clutters everything up, and makes it hard to find the fields we are looking for. 

In order to fix this, we've been going in to each request type, and "hiding" the fields that aren't relevant to those request types. The more request types we have, the more time consuming and tedious this is to do. 

Has anyone come up with a way to address this?

Thanks so much,

Matt 

Brant Schroeder

@Matt Harford 

We have a specific screen scheme for our service desks.  We associate the new custom fields with the screen(s) on that scheme when we created for the service desk.  This is easy to do when prompted during the custom field creation process (Associate the field services to a screen)  We also limit what projects and issues it is associated with in the context so it does not show up on other issue types.