Tickets

Create a ticket

1. 01Choose New, or press c.
2. 02Write a specific title and a Markdown description.
3. 03Choose a type, priority, board, assignee and optional parent epic.
4. 04Add images or files to the description if useful.

Types

Epic, story, task, bug, chore

Priorities

Lowest, low, medium, high, highest

Attachments

Up to 10 MB each

Each ticket has its own link, such as https://praxis.theorem-labs.com/WEB-42. The title has a copy-link button.

Story points

Points use a fixed Fibonacci scale: 1, 2, 3, 5, 8, 13.

• Unestimated is its own value, never zero. Totals always show how many tickets are unestimated.
• Set or change points in the editor, the ticket sheet or a bulk edit.
• Agents can estimate what they file with points, and re-estimate when the work turns out a different size.
• Flow suggests estimates for unestimated tickets. Suggestions are never saved to the ticket.

Epics and links

• Set a parent epic to group a ticket under it. A ticket has at most one epic.
• Linked tickets show as cards with type, status, priority, board and assignee.
• Drag an epic's children to reorder them. The board uses the same order.
• Opening a linked ticket keeps a back arrow to where you came from.

Blockers

A ticket is blocked if any of these is true:

• It has a blocks link from a ticket that is not done.
• It has a free-text "Blocked by whom / why" reason.
• Its status is Blocked.

Add a blocker by key in the ticket's Dependencies block. Remove a link with the cross on its row.

Praxis moves tickets automatically. Adding a blocks link moves a Backlog or To Do ticket to Blocked. When its last blocker is done, deleted or unlinked, it returns to To Do.

• Only Backlog and To Do tickets are moved to Blocked. Started tickets keep their column and show a blocked badge.
• Done tickets are never moved back.
• A free-text reason keeps a ticket in Blocked, but never moves one there by itself.
• A Blocked ticket with nothing linked is left alone.
• A ticket that leaves Blocked returns to To Do, even if it started in Backlog.

Search and find

• Search reads keys, titles, descriptions and comments.
• WEB-42, web 42 and web42 all find WEB-42. An exact key ranks first.
• Press Ctrl+F, or Cmd+F on macOS, to open the ticket finder. Use the arrow keys, Enter to select and Esc to close.
• The found ticket stays highlighted when you switch between Board, Tree, Dependencies, Map and Flow.

Mentions and edit conflicts

• Type @ in a comment to pick a person. @Full Name in a description or comment notifies them.
• Assigning a ticket to someone also notifies them. You are never notified about your own actions.
• Editing a description only notifies people newly mentioned.
• Only people with access are suggested. Mentions never grant access.