New custom field without adding it to all request types

[Steven Miller]

We have multiple request types under 'service request'. Say one is 'Software Install' and one is 'Hardware Purchase'.

We have created multiple specific custom fields which we add to these specific requests, one being a list of available software and another being hardware that can be purchased.

The issue is when after creating the new field, we are required to associate it with an existing screen. As these are all based on 'service requests', the new field gets added to both request type context field lists, when we only want to have it added to one. We then have to go into each request type and hide the unwanted field from the context view.

Is there a better way I could be going about this? This problem is only going to be more of a pain as we continue to add request types and custom fields.

[Chris Garstin]

None of the answers that suggest the convoluted use of multiple issue types and/or field configurations are workable. Request type field definitions are clearly separate from screen schemes and there should be an option to NOT automatically add new fields.

Ive asked Atlassian to create a feature request to properly make this possible:

https://jira.atlassian.com/browse/JRACLOUD-94280

[Brant Schroeder]

@Steven Miller - I just answered a similar post here: https://community.atlassian.com/t5/Jira-Service-Management/How-are-others-managing-custom-fields-with-request-types/qaq-p/1677504   Let me know if you have any additional questions.

[Steven Miller]

Thanks, I replied over in that thread since it is very recent.