Best practice for the use of TAG's for a software developer.

I use tags most in workflow automations(WFA), to set tags when the flow is done/failed, to prevent loops if you use the update event. 

If you use the service catalogue, you can add the name of the service item as a tag then you can filter or create reports based on that. 

Use tags when using the Supervisor Rules to prevent loops.

Hi.

Adding to Daniel’s response, you can use tags for Analytics, not only for service items, but in general.

Regards,

Implementing Freshservice for your service center in the energy sector is a great step. To effectively utilize the tags function, consider categorizing incidents based on common themes like software types (on-premise, SaaS), specific application names, urgency levels, or even the location of the issue. This allows for streamlined tracking and sorting of incidents. Additionally, using tags to denote the stage of resolution (e.g., "Open," "In Progress," "Resolved") can enhance workflow management. Leveraging dedicated custom fields for software application information is a good approach, ensuring comprehensive coverage. Learning from others' experiences can provide valuable insights tailored to your industry and workflows.

We use Tags for making dashboard views (through list), we determine our flows by tags, also in analitycs.

In general we use tags for almost everything. It helps mainly when you want to show tickets in different places “at once” even though you have one agent group set.

Since you can add and delete tags through workflow automator everything is easier that way