Instead of having to recreate field every time they are needed, it would make more sense to be able to choose from a list of fields that have already been defined. This would also be very helpful to enable workflows based on these custom fields.
For example, all Employee New Hire, Separation and Change catalog items have a field called "Effective Date." This should become the due date for the ticket and for any task created from the ticket.
I have a ticket raised for similar feature some time ago so sharing it here as well.
Is it possible to reuse a dropdown field across multiple service requests so that I could update the list values in one place?
I've been currently updating the same dropdown field in multiple services requests when I'd rather threat this as data source.
Even better, this could be the AWS account name linked to Freshservice CMDB with the integration plugin.
We currently have custom Location field on multiple service requests but would be useful to be able to use the built in Location category as custom field in the requests.
Yes! Please give attention to this matter.
Reusing of code or reusing of components (custome fileds) , where at the time of updating just need to touch one place, is a no brainer feature for Service Catalogs.
I agree. The addition of Data Sources was a step in the right direction, but we're just talking about a centrally managed list that can be used as a field in a service request item. I have +150 service request items each needing a list of all business units (+30). If we add/modify a business unit, that's me updating 150 individually managed, yet identical lists.