Recent searches


No recent searches

Explore recipe: Custom formatting for ticket tags



Edited Jun 21, 2024


2

4

4 comments

This will prove to be super handy thanks Jess. 

Is there a way that I could remove all characters leading up to the first _ without specifying the string and number of characters?

So I wouldn't have to created a custom attribute for each tag if I had multiple tags per ticket -hopefully that makes sense. 

Many thanks.

1


I agree. It seems like this should be baked into Explore.

1


To get around having duplicate tags with identical names, I sometimes use the following format:

    tag_group/tag_sub_group/specific_tag

Generally, when I'm reporting, I don't care about the groups and want to see only the specific tag with decent formatting. The code below will accomplish this and remove any number of groups/sub groups.

To make this work as expected, tags cannot have slashes "/" in them except when separating groups.

 

REGEXP_REPLACE(REPLACE(REGEXP_REPLACE([Ticket tags], "([^\/]*\/)*", ""), "_", " "), "^[a-z]", UPPERCASE(REGEXP_EXTRACT(REPLACE(REGEXP_REPLACE([Ticket tags], "([^\/]*\/)*", ""), "_", " "), "^[a-z]")))

 

Beforecustomer_service/escalations/billing

AfterBilling

Hope this is helpful for anybody who might use tags in a similar way.

0


Thanks for sharing this, Jozef!

0


Please sign in to leave a comment.