Just exploring if there would be any draw-backs to allowing custom fields to display on tickets based on conditional criteria similar to conditions defined in triggers i.e. based on a tag that correspondes to a specific product line workflow?
My use-case for this would be to avoid the clutter (or irrelevant ticket contexts) caused by multiple custom fields displayed on all tickets, yet the fields only apply to tickets belonging to specific workflows organized by product line (which is the case in our instance).
This tends to cause additional steepness to the learning curve for users who collaborate on support but don't do so on a regular basis and eliminates human error for our experienced agent.