Getting started
Ten minutes from an empty workspace to a team working on a real board.
1. Create the workspace
Create an account. The first person in a workspace is its owner. Confirm your email from the link we send. Once you're in, the dashboard shows a Get your team started checklist that ticks itself off as you go.
2. Make a project
Go to Projects → New project and pick a short key (like WEB). Issue keys use it: WEB-12. Not sure yet? Use Try a sample project on the dashboard: it creates a project with six example issues spread across the board, which you can delete later.
3. Bring in the team
- Teammates: Settings → Members. Roles: owner (everything, including members and integrations), editor (create and change work), viewer (read only).
- Clients: Settings → Members → Client access. A client sees only the projects you share, can comment and file issues, and their access ends on the date you set. Issues they file wait in the backlog's Triage box until an owner or editor accepts or declines them.
- Projects can narrow access further under Project settings → Members.
4. Learn the daily moves
| Do this | How |
|---|---|
| Create an issue from anywhere | Ctrl K, type the title. Tags: #bug !high @name ~sprint |
| Add many issues fast | Use the + Add issue row under any board column, the backlog or a sprint. Type a title and press Enter; the row stays open for the next one. The same tags work there. Paste a list (one per line, bullets and numbers are fine) to create one issue per line. |
| Plan several sprints | Backlog → Create sprint. Pick a length and how many: they are named and dated back to back after your last sprint. |
| Create an issue from chat | /create-issue WEB Login fails on Safari. Other commands: /assign WEB-12 @name, /meeting, /huddle. |
| Move work | Drag cards on the board. An Undo button appears for a few seconds after every move. |
| Change many issues at once | Tick them on the board, backlog or Issues page, then set status, priority or assignee, add a label, or move them to a sprint. Undo works here too. |
| Filter | The board, backlog and Issues page share one filter row: Type, Priority, Assignee (including Me and Unassigned), Label, Sprint and Due (overdue, next 7 days, none). Tick several values to match any of them; different filters must all match. Filters live in the link, so share it or save it as a view. Label and Sprint appear on the Issues page once you pick a project. |
| Avoid duplicates | When you type a new issue's title, look-alike issues show up underneath, with who handled them. |
| Reschedule | Reports → Timeline. Drag a bar to move it, or its right edge to change the due date. Arrows show what blocks what; a red dashed arrow means something starts before its blocker ends. |
| See how a sprint is going | Reports → Sprint burndown (remaining work per day) and Velocity (taken on against finished, last six sprints). |
| Write together | Open a page under Docs. Everyone with the page open edits the same copy live; nobody overwrites anyone. |
5. Connect the rest
- GitHub: import repos and keep issues in sync.
- Google Calendar: Settings → Integrations, per person. Meetings and sprint ceremonies land in your calendar.
- Phone app: notifications for assignments, mentions, pushes and failed builds.
Where things live
- Inbox: everything that needs you. Dashboard: your work across all projects.
- Project: Board, Backlog, Sprints, Docs, Ideation, QA, Scans, Reports, Settings. Sections a team doesn't use can be switched off under Project settings → General & Git.
- Your menu (top right): dark mode and a compact layout, both remembered on this browser.
- Settings → Security: your sessions, with which app (web, admin or phone) each one is from.