Get started
Core ideas
Understand projects, epics, stories, tasks, statuses, priorities, and labels.
Last updated
A project groups work for a product, team, or client. Each piece of work inside it is a card, called an issue in the app.
Make a large goal manageable#
For a website launch, you might have an epic called “Launch the website”, a story called “Visitors can contact us”, and a task called “Write the contact form confirmation”. This keeps the reason for a small task close to the task itself.
Organize your cards#
- Create an Epic for a large body of work.
- Create a Story and choose its epic as the parent. A story describes a useful result for a user.
- Create a Task under the story for a concrete piece of work. You can also leave stories or tasks without a parent.
- Open Hierarchy from the project view menu to see the parent and child cards together.
Describe where work stands#
- Open a card and choose its Status. Status describes progress, such as To do, In progress, In review, or Done. Projects can have custom statuses.
- Set Priority to Urgent, High, Medium, Low, or No priority. Priority describes importance, not progress.
- Choose an Assignee, the person responsible for the card, and add Labels for subjects such as bugs or design.
Tips and common mistakes#
- You do not need all three card types. A small project can start with tasks alone.
- Labels belong to a project. Use consistent names so filters remain useful.
- Moving a card to a status does not change its priority. Decide those separately.
- A cycle groups project work for a period. A weekly commitment records what a person plans to work on. Neither replaces the card hierarchy.