-
Notifications
You must be signed in to change notification settings - Fork 16
Ticket Folder Pane
The left-hand panel in Tickets β Inbox. It is how you narrow a few hundred tickets down to the handful you are actually going to work on, and it does more than it looks like it does.
At the top sit two buttons: Department and Analyst. They change what the middle of the list is made of.
| Department | One folder per active department β IT Support, Infrastructure, Development. The usual view when work is owned by a team. |
| Analyst | One folder per analyst, showing what each person is carrying. The usual view when you are running the desk rather than working it. |
The choice is yours alone. It is remembered against your account, so switching does not change what anybody else sees, and it survives signing out.
Each folder shows how many tickets are in it, and clicking one opens it to reveal a count per status:
IT Support (32)
Open (24)
In Progress (4)
On Hold (1)
Awaiting Response (3)
Closed (0)
Resolved (0)
Click the folder to see everything in it; click a status underneath to narrow to just those. A status with nothing in it is greyed rather than hidden, so the shape of the list stays the same as you move about and you can see at a glance that nothing is on hold.
The statuses are your statuses. They come from whatever you have configured under Tickets β Settings β Statuses, in your display order, so an install using In Analysis and Waiting for Vendor sees exactly those.
Opening a folder never changes what you are looking at. Click IT Support and you get IT Support's tickets, whether the list of statuses underneath is open or shut.
Above and below the group folders are four that are always there.
Everything you have access to, and the view most people leave open. It expands like any other folder, giving you a status count across the entire desk β which is the quickest way to answer "how much of this is actually still open?" without filtering anything.
Work nobody has picked up. It expands too, and this one is worth understanding properly, because what it means follows the grouping you have chosen:
| Grouped by | Unassigned means | Typical use |
|---|---|---|
| Department | No department has been set | Triage: mail that arrived and has not been filed |
| Analyst | Nobody is working on it | The pile to hand out at a stand-up |
These are genuinely different sets β a ticket can be filed to IT Support and still have nobody working on it β so the counts underneath change when you flip the toggle. That is deliberate, not a glitch.
Tickets that have left the queue until a time you chose. They are not in All Tickets, not in their department, and not in anyone's analyst folder β a snoozed ticket has genuinely gone away. See Snoozing tickets.
Deleted tickets, kept and restorable. Also excluded from every other folder. See Selecting several tickets for bulk deletion.
You can drag tickets from the list onto folders in the pane, and where you drop decides what changes.
| Drop onto | What it does |
|---|---|
| A department | Files it to that department |
| An analyst | Assigns it to that person |
| A status under a department | Files it and sets the status, in one move |
| A status under an analyst | Assigns it and sets the status |
| A status under All Tickets | Sets the status only β nothing else is touched |
| A status under Unassigned | Unassigns it and sets the status |
| Unassigned | Clears the department, or the analyst, depending on the grouping |
| Trash | Deletes it (restorable) |
Two things worth knowing:
Dragging a selected ticket drags the whole selection. If you have ticked five tickets and drag one of them, all five move. Dragging a ticket that is not part of the selection collapses the selection to that one first, so you can never move a set you thought you had deselected.
Hovering over a closed folder opens it. Hold a dragged ticket over a department, an analyst or Unassigned for a moment and it expands, so you can drop onto a status without letting go first.
Every change made by dragging is written to the ticket's history exactly as if you had used the dropdowns.
- Trashed and snoozed tickets are excluded from every ordinary folder β they are counted only in their own.
- Counts respect your access. If your teams limit you to certain departments, every number in the pane is already narrowed to what you can see.
- On a multi-company install, everything is scoped to the company you are currently in.
- The numbers under a folder add up to the number on it. They are counted the same way as the total above them rather than by a separate rule that could drift.
- Merged tickets are not counted. When one ticket is merged into another the loser is kept so its number goes on working, but it is no longer a job in a queue and does not appear in any folder.
- A ticket with no email still counts, and still shows. Most tickets arrive as an email, but not all do, and the ones that do not are listed exactly like the rest.
The counts and the list used to be able to disagree β a folder could say 99 and list 96. That turned out to be two separate faults and both are fixed, so if you ever see a badge that does not match the list beneath it, that is worth reporting.
- The folder pane β Developer Guide β how it is built
- Merging tickets and splitting tickets β the other two things you do from this list
- Selecting several tickets
- Snoozing tickets
FreeITSM β an open-source IT Service Management platform Β· github.com/edmozley/freeitsm Β· MIT licence
- Installation
- β° Scheduled tasks (cron jobs)
- Architecture
- AI Providers
- Internationalisation (i18n)
- Timezones & Time Handling
- Theming & Dark Mode
- β¨οΈ Command palette (βK)
- π Searching inside tickets
- π Attached documents
- MobileβFriendly
-
Security
- Layer 1 β which modules you can enter
- β³ π§© Module Access Control
- β³ π οΈ Module Access β Developer Guide
- Layer 2 β what you can administer
- β³ π Roles & Permissions
- β³ π οΈ Roles β Developer Guide
- β³ π€ Why capabilities are constants
- Layer 3 β the System module
- β³ π Admin Access Control
- Hardening
- β³ π Security review response 2026-08
- β³ π‘οΈ Security hardening 2026-08
- β³ π οΈ Security hardening 2026-08 β Developer Guide
- β³ π‘οΈ Round three β plain English
- β³ π οΈ Round three β Developer Guide
- Single Sign-On (SSO)
- ποΈ LDAP & Active Directory
- Browser Extension
- API Reference
-
π REST API β how it works
- β³ π« REST API: Tickets
- β³ π» REST API: Assets
- β³ π΄ REST API: Problems
- β³ π REST API: Changes
- β³ π REST API: Knowledge
- β³ β REST API: Tasks
- β³ ποΈ REST API: CMDB
- β³ π REST API: Contracts
- β³ ποΈ REST API: Calendar
- β³ πΏ REST API: Software
- β³ π¦ REST API: Service Status
- β³ βοΈ REST API: Morning Checks
- β³ π REST API: Forms
- β³ βοΈ REST API: Workflow
- β³ πΊοΈ REST API: Network Mapper
- β³ π§ Using the API docs page
- β³ π OpenAPI specification
- β³ β OpenAPI: kept correct
- β³ π οΈ Maintaining the catalogue
- Watchtower
-
Tickets
- β³ Mailbox Authentication
- β³ π€ Email send log
- β³ Basic IMAP mailboxes
- β³ Email rendering & images
- β³ SLA Management
- β³ WhatsApp channel
- β³ π¬ Web chat channel
- β³ π£ Slack channel
- β³ π Linking tickets
- β³ ποΈ Canned responses
- β³ βοΈ Limiting replies to particular senders
- β³ βοΈ Email signatures
- β³ π The public web address
- β³ π’ Ticket numbering
- β³ π Raising a ticket for someone else
- β³ π Merging tickets
- β³ β Splitting tickets
- β³ β Selecting several tickets
- β³ ποΈ The folder pane
- β³ π οΈ Snoozing tickets β Developer Guide
- β³ π₯ Collision detection
- β³ β±οΈ Time tracking
- Problem Management
- Tasks
- Assets
- Knowledge
- Change Management
- Calendar
- Morning Checks
- Reporting
- Software
- Forms
- Contracts
- Service Status
- π Notifications
- π¨ War Room
- Self-Service Portal
- LMS
- Process Mapper
- CMDB
- Network Mapper
- Workflows
- Issue trackers (Jira, Azure DevOps)
- System
-
Overview
- β³ π Progress tracker
- β³ Concepts & vocabulary
- β³ Email routing & mailboxes
- β³ Settings: global vs per-company
- β³ Users & self-service
- β³ Staff cross-company access
- β³ Worked examples
- β³ Pitfalls & gotchas
- β³ Scope: what it's for
- β³ π οΈ Developer Guide (make a module multi-company)
- β³ ποΈ Case study: CMDB (a linked graph)
- β³ π§ͺ Test harness (prove it's isolated)