The job of this console
Track what you opened, answer a waiting-on-you prompt, and close when the desk agrees. Raise new work on the team tickets screen if you have it.
Workspace · Service
My Tickets
Service tickets you opened or are assigned — the same ticket records the project service desk uses.
Scroll to Flowcharts. Scenario: Update a ticket from My tickets.
Personal service queue
Your tickets, still the desk’s records
My tickets shows service desk rows you requested or own. Status changes write to that ticket, not a private list.
Workspace → My tickets
Route
/workspace/my-tickets
Org flag myTicketsEnabled
Employee · Assignee
Seat at the table
Employees and assignees with myTicketsEnabled. Service owners use Projects → Tickets & service.
The working rhythm
Filter mine, open, comment, save. Watch SLA on the ticket detail, not on this list alone.
Moments that bring you here
A laptop request that became a ticket. Waiting on you. After an SLA reminder. When chat said ‘I’ll ticket it’.
ⓘ
One ticket entity
This is not a shadow helpdesk. Access grants may still need Admin access requests or Roles.
Flowcharts
1 — Work a ticket you own
Open your queue, update the same ticket the service desk stores.
flowchart TD
A[Open My tickets] --> B[Filter mine]
B --> C[Open ticket]
C --> D[Comment / status]
D --> E[Save]
E --> F[Service desk register matches]
- 1OpenWorkspace → My tickets.
- 2FilterRequested by you vs assigned to you.
- 3UpdateStatus and comments on the ticket entity.
- 4ConfirmTeam tickets register is the same row.
Overview
My tickets is a personal slice of the ticket / service desk entity. It is not a second helpdesk. Access requests for laptops still live under Admin access requests when that is the domain.
How to use
1. Same ticket everywhere
Do not recapture the issue in chat as the only copy.
2. SLA lives on the ticket
This queue does not override policy.
3. Sensitive data
No passwords or payroll files in comments.