Product shape
DevTicket is a cross-platform issue tracker: you can use it in the browser and on iOS and Android. Work lives in workspaces (each tied to an organization). You sign in once, then switch workspaces if you belong to more than one.
Documentation
Here are some general guidelines. This is not the full user doc. We'll have that soon.
Who can do what
Each member has a role—for example owner, admin, editor, or viewer. Owners and admins manage people and workspace-wide settings; editors create and edit tickets; viewers can browse without changing data. Invitations are sent by email and must be accepted with the invited address.
Configure projects, categories & priorities first
Before creating tickets, the workspace needs at least one project, category, and priority. These lists are shared for everyone in the workspace. You can mark defaults so new tickets start with sensible values (you can still override per ticket).
Tickets, updates & attachments
Tickets can be filtered, sorted, searched, and customized with visible columns; layout
preferences can differ per device. Each ticket has a thread of
updates. You can attach files to a
specific update (supported image types and PDFs, with size limits enforced in the app).
Snippets are personal text shortcuts
you expand in an update after a semicolon and trigger (for example
;sig)—useful for reusable checklists or boilerplate.
Notifications
You can be notified when you are assigned or unassigned, or when someone else updates a ticket that is assigned to you. Channel availability (such as email, SMS, or push) depends on how your workspace and account are configured—choose what you want in settings.
Export
Workspace owners and admins can download all tickets in the current workspace as a CSV file from the account area—useful for backups, audits, or analysis in another tool.
API
Programmatic access is documented alongside authentication and endpoints on the API page.