Categories and sub-categories
Enterprise feature (new in 1.20.6,
helpdesk). See the Helpdesk overview.
A ticket’s category says what it is about: Hardware, Access, Payroll. Until 1.20.6 it was typed by hand, so the same thing ended up as “Printers”, “printer” and “Printing” in three reports. Now the desk admin keeps one list of categories, each with its sub-categories, and everyone picks from it. Nothing is typed.
A pair is written Category › Sub-category, for example Hardware › Laptop.
The list
Section titled “The list”Desk settings → Forms and fields → Categories shows the list. It needs the desk capability Helpdesk settings (Admins, out of the box).
Each category shows what uses it (“12 tickets · 2 request types · 1 automation”) and its sub-categories under it.
- New category adds one. The + on a category’s row adds a sub-category to it.
- Rename (the pencil) changes the name everywhere at once: on the tickets that have it, on request types and automations that set it, and in saved views and report filters. Lines already on a ticket’s timeline keep the words they were written with (“set the category to Printers”).
- More → Move up / Move down sets the order pickers show.
- More → Archive hides it from every picker. Tickets that have it keep it, and it still shows in reports. Restore brings it back. You can’t archive a category while a request type or an automation still gives it to new tickets; change those first.
- More → Delete is for an entry nothing uses. If tickets, request types or automations still use it, the dialog says so and offers Merge into… instead.
- More → Merge into… moves everything to another entry and removes this one. See Merging.
Names are unique within their level whatever their case: “printers” and “Printers” are the same name. The same sub-category name can sit under several categories (an “Other” under each). A name is up to 80 characters. The list holds up to 200 categories, each with up to 100 sub-categories.
Tickets in the recycle bin still count as using their category until they are removed for good.
Merging
Section titled “Merging”Merge into… is how you tidy doubles. The dialog says exactly what will happen before you confirm.
- A category into another category. Its tickets take the other category. Its sub-categories move across with their tickets; one the other category already has by name becomes one with it.
- A sub-category into another sub-category, in the same category or a different one. Its tickets take that category and sub-category.
- A sub-category into a category alone. Its tickets take that category and no sub-category.
Request types, automations, saved views and report filters that named the merged entry name the kept one afterwards. A merge can’t be undone, and it can’t go into an archived entry.
Drafts from Claude
Section titled “Drafts from Claude”From 1.20.16 Claude can propose changes to the list: new categories and sub-categories, and renames. It never deletes or merges. The proposal shows above the list as a draft; pickers, rules and the API keep using the live list until someone with desk settings rights presses Publish. You can edit the names or take changes out first. Publishing a rename updates tickets, request types, rules and saved views in one go, as a rename here does, and asks you to confirm first.
If a category in the draft was renamed since it was drafted, publishing is refused (“Change 1: “Printers” is now called “Hardware”. Review the draft again before you publish it.“).
On a ticket
Section titled “On a ticket”The ticket’s Properties show Category and, when the category has sub-categories, Sub-category. Each opens a menu of the list. Picking another category clears the sub-category, since it belonged to the old one. Every change leaves a line on the timeline.
A sub-category is optional. To make it required before a ticket is solved, tick A sub-category in a Before you solve requirement set. A ticket whose category has no sub-categories passes that check.
The category also shows on the printed ticket as Category: Hardware › Laptop.
If no categories exist yet, the menu says so, and admins get a link to add them.
Where else categories are picked
Section titled “Where else categories are picked”- Request types: the category (and sub-category) its tickets start with. Tickets from Get help, the customer portal and email get them exactly as before.
- Automations: Category is any of is a list to tick: a whole category, or only some of its sub-categories. Set the category and Set the sub-category are picked from the list.
- Filters: the queue’s Filter dialog has Category and Sub-category, and they can be kept in a saved view.
- Reports: the Category filter offers the list, and Sub-category is a way to split any measure. The summary export gets a sub-category block, and the time export a Sub-category column at the end.
- Before you solve: a missing category is picked in the dialog.
Assignment rules still compare the category as text (“is”, “contains”). A rename doesn’t rewrite those, so check them after renaming a category they mention.
Nothing invents a category
Section titled “Nothing invents a category”A category that is not on the list is always refused, never added:
- The API answers
400with the allowed names. - The Claude connector is told the same and changes nothing.
- An automation or a request type can’t be saved with one.
Only someone with Helpdesk settings adds to the list.
Upgrading from 1.20.5
Section titled “Upgrading from 1.20.5”There is nothing to run.
- Every category already in use joins the list the first time 1.20.6 starts: each one on a ticket, a request type or an automation. Spellings that differ only by capitals or outer spaces become one entry, in the spelling most tickets use, and those tickets are brought to that spelling. No ticket loses its category.
- The list starts with no sub-categories. Add them, then use Merge into… to fold old doubles together.
- With nothing in use, the list starts empty and tickets simply have no category until you add some.
- Imported tickets work the same way: the categories they bring join the list when the import ends.
- Rolling back to 1.20.5 is safe. Tickets keep their category in the same place 1.20.5 reads it; the list and the sub-categories are ignored until you upgrade again, and anything typed in the meantime joins the list then.
