Skip to main content

We’re looking to enforce tagging when a support ticket is marked as Resolved — ideally from a predefined list of tags we use for resolution classification. We’ve been able to enforce tagging when conversations are moved or archived, but this doesn’t appear to apply when someone simply changes the status to Resolved (e.g., using status buttons or automatically in sending a response).
We rely on tagging for resolution audits and postmortems, so ensuring consistent tag usage at closeout is important.

Before submitting this as a feature request, I wanted to check if anyone has successfully configured this in their workspace.

Here’s a screenshot of the rule that isn’t working the way I’d hoped:

 

Hey Ward, 

Phoebe here with the Front team. Thanks for flagging this! 

At the moment, required tagging rules can only function on the triggers “conversation is archived” or “conversation is moved” and this is fixed, but our team is aware that this limits options for teams who use ticketing. 

We have an open feature request for this functionality in our Product Ideas Portal which is accessible to all users: https://front.ideas.aha.io/ideas/PRD-I-2877

I highly recommend voting on this feature request! 


Reply