Your account Tickets
Tickets
A ticket is how you tell Oxelone about a bug, an idea or a question. It has a status, a thread of replies, and followers. You reach tickets from the account menu at the foot of the sidebar.
Who can do it
Every member can open a ticket and reply to their own. A ticket is visible to the person who sent it, and to the workspace's Owners and Admins. Nobody else in the workspace sees it. A ticket belongs to the workspace you sent it from; another workspace's ticket is not found, even by the person who sent it.
Send a ticket
- Open the account menu and choose New ticket.
- Choose a Kind: Bug, Idea or Question. Nothing is chosen for you.
- Write a Summary of up to 160 characters, and the Details in up to 4,000.
- Choose Send ticket. A notice says the ticket is sent, with its reference.
Diagnostic details about the page you were on are sent with it: the console route, the path through the console you took, API calls that failed, errors, and facts about your browser such as its version, operating system, screen size, theme and language. The details contain no text read off the page. The server adds who you are, your role and the workspace.
Read and follow a ticket
My tickets lists tickets, most recently touched first, with the ticket open beside the list. A dot marks a ticket with an unread update, and the account menu shows a dot on your avatar when any has one. Opening a ticket reads it.
In an open ticket you see its Reference, Kind, Status, Opened by, Opened, Last update, and Shipped in when the fix has shipped. The thread shows replies; replies from Oxelone are signed Oxelone, never by a person's name.
- Follow and Unfollow control whether you are told about changes. Followers are told through notifications.
- Mark resolved sets the status to Resolved.
- Reply in the Reply box.
Owners and Admins also see Mine and Workspace, to switch between their own tickets and the workspace's.
The statuses
A ticket is New, In progress, Waiting, Planned, Resolved or Closed. You can mark your ticket Resolved. A reply on a Resolved or Waiting ticket puts it back to In progress. A Closed ticket takes no reply, and a closing reply from Oxelone says why.
Every field
| Field | What it does | Default |
|---|---|---|
| Kind | Bug, Idea or Question. | None chosen |
| Summary | One line about what this is. | Empty |
| Details | What you did and what happened, or what you want. | Empty |
When it goes wrong
- Choose Bug, Idea or Question. Pick a kind.
- Say what this is about in one line. The summary is empty.
- Add the details. The details are empty.
- Keep it to 160 characters. / Keep it to 4,000 characters. Shorten it.
- The details about this page were too large to send. Send it again. / The details about this page could not be sent. Send it again. Try once more.
- This ticket is closed. Open a new ticket to follow up. A closed ticket takes no reply.
- This ticket was merged into another one. Reply there. Oxelone joined it to a ticket about the same thing.
- This ticket is not here. It does not exist, or it belongs to another workspace.
- Only this workspace's Owners and Admins can see every ticket. You chose Workspace without the Owner or Admin role.
- Could not send this ticket. Try again.
With the API
Not available with an API key.