Critical work has stopped
Major impact with no practical workaround. Example: a shared system is unavailable for the team.
What to raise, how to prioritise it, and what to expect along the way.
Choose a department, explain what you need, and add any useful screenshots. Your team takes it from there.
Priority helps your team decide what to address first. Choose the level that best describes how your work is affected.
Major impact with no practical workaround. Example: a shared system is unavailable for the team.
Important work is seriously affected. Example: essential equipment is failing and work is delayed.
Work can continue while the team helps. Example: access to an additional tool or a routine account issue.
Limited immediate impact. Example: a cosmetic problem or a small enhancement.
These provisional targets use elapsed hours from submission. They are not guaranteed deadlines or a promise of 24/7 support. Your organisation will confirm service hours before live use. A lead can set a separate due date on a ticket.
Assignment tells you who's helping. Status tells you what's happening.
Your request is received and ready to be assigned.
An assigned team member is working on it.
Work needs more information or another dependency. A reason is recorded; due dates keep running.
A solution has been provided. Check whether it worked.
You've confirmed the solution, or a lead/admin has closed it with a recorded reason.
Reopen the same ticket with a reason. It returns to Open for review. If it's a different issue, raise a new request.
You, the assigned agent, the responsible department's leads and administrators. All comments and attachments share that same audience.
You can edit the original request before work begins. After that, add a reply so the team keeps the full context.
An unresolved ticket is overdue when its explicit due date has passed. Resolved, Closed and Cancelled tickets aren't currently overdue.
Leads and admins can correct priority, reassign or transfer with a reason. When a department changes, the old team's access ends unless another permission applies.
No. You confirm closure after a solution, or a lead/admin closes with a recorded reason. Mistaken or duplicate requests can be cancelled while preserving history.
Your workspace is where every request moves forward.