HelpSpot Help Desk Software | HelpSpot Blog | HelpSpot Support

Reporting Tags - Tag Colour and Box Size


#1

Hi All,

After a few years of using HelpSpot without leveraging its full potential, we’re finally getting around to figuring out how to make it work for us more effectively.

Reporting Tags are the big boon for us, but we’re hoping to see them developed with the following features:

  • Adjustable box height (where do we modify this in the code base? Edit - Found it!).
  • Selectable background colours for Tags.
  • Real-time, per key-stroke navigation or filtering (preferably filtering).

Cheers,

Brendan


#2

Brendan this is really interesting idea. How would you see the filtering applied? Within a workspace view showing a list of requests (a “filter” by helpspot language?


#3

Hi Brendan,

Sometimes it does end up taking a while to actually dig in!

On the box height for reporting tags do you mean where they’re selected, how they require scrolling? If so you could use a custom admin theme to change the height of that if wanted to.

Colors are an interesting idea. Don’t think we’ve heard that one before, but would be interesting to highlight important ones.

On the filtering do you mean in the reporting tag selection area on the request page to have a way to find the one you want or on the Workspace filter grid to filter down a large number via reporting tags in real time kinda thing?


#6

Thanks Ian.

I found the answer to the #reportingTags max-height question last night, added a modded admin theme, applied it this morning, and it’s done the trick very nicely!

The custom background colours (per tag) would be handy in our case for creating really obvious sections in the tag list. We have over 60 tags so far, with over half a dozen “sections” currently defined by text prefixes and tag order. This may well grow over time.

I envisage the filtering need be no more than a text field atop (or below) the Reporting Tag list. Any text entered will search the tags and dynamically display only those that contain the string being defined (per key-stroke). A blank field shows all tags. This would go some way to emulating tag behaviour in other applications without radically changing the current scheme.

Thanks again for responding.

Brendan


#7

Hi Bill,

Thanks for your feedback.

I envisage the filtering need be no more than a text field atop (or below) the Reporting Tag list. Any text entered will search the tags and dynamically display only those that contain the string being defined (per key-stroke). A blank field shows all tags. This would go some way to emulating tag behaviour in other applications without radically changing the current scheme.

Cheers,

Brendan