My Service Requests
Route: /org/service-requests/my (customers: /support/requests)
Permission: Submit Service Request
1. What it is
Where a requester tracks what they ordered. Backward-looking and history-shaped — as opposed to Request a Service, which is forward-looking and item-shaped.
2. The table
| Column | Holds |
|---|---|
| Request | The item title, with its item key in mono beneath |
| Project | Which project it was raised against |
| Status | Pending Approval (amber) or Approved (green) |
| Ticket | The ticket reference once one exists — or — |
| Requested | Timestamp |
Refresh re-reads the list. Raise a Request returns to the catalog.
The Ticket column is the clearest proof of the approval rule
An Approved row carries a ticket number. Pending Approval shows —, because
no ticket exists until approval. If a requester asks why
their request isn't in the queue, this column is the answer.
3. Don't confuse this with…
| These two | Differ by |
|---|---|
| My Service Requests vs Request a Service | Tracking vs ordering |
| My Service Requests vs Approvals | My requests vs requests I must decide on |
| This vs Resolution Queue | Requests (some without tickets) vs tickets |
4. Troubleshooting
| Symptom | Cause |
|---|---|
Ticket column shows — | Still awaiting approval |
| Request missing | Raised on a different project |
| Stuck at Pending Approval | No approver assigned, or the approver has not acted |