Nine issue types, plus your own.
Start with nine built-in issue types and add your own, with your label, colour and order. Every issue keeps its blockers, its epic, its story points and any extra field you decide it needs, all in one place.
Task, bug, user story, feature, epic, improvement, spike, sub-task and tech debt ship as rows in a table rather than as a fixed list. Add your own and it behaves exactly like the nine.
One issue, open
Everything on one issue.
Status, priority, type, story points, epic and assignee down the side. Blockers and the work they hold up on the left, along with any fields you added yourself. The type list starts with nine built-in types, plus any your team has created.
Build the shared Account 360 spine
One record surface behind Sales, Clients and Service, so a customer is the same customer in all three. Won and lost deals suppress the at-risk banner.
You can add your own issue types.
Add your own issue types.
Nine built-in types to start with, and the ones you add work exactly the same way.
- Start from task, bug, user story, feature, epic, improvement, spike, sub-task and tech debt
- Add your own type, with its label, colour, icon and place in the order
- Turn a type off when you stop using it; older work keeps its label
- The nine built-in types stay as read-only defaults
- Mark an issue as a hotfix and it logs a learning by itself when it closes
Link a blocker once, see it from both sides.
Everything about an issue is on one screen, not spread across tabs.
- Mark what is blocking an issue; the blocking issue shows what it holds up automatically
- Add your own fields to any issue, with no setup
- Give it story points, a priority and a place in a sprint
- Put it under an epic, or under a parent issue
- Assign it to anyone on your employee roster
Access
Who can do what.
Anybody can raise an issue, add a field and flag what is blocking them. Changing the issue types the whole organisation uses affects everyone, so that stays with a small group.
See every issue, every epic and what blocks what.
Raise an issue, add a field, name a blocker.
Create epics and assign work to people.
Create and reorder the issue types everyone uses.
Admin is the highest role and is not limited by the permission grid, so give it only to the few people who genuinely need it.
One piece of work, start to finish
An issue raised as a chore, a type the team created that morning.
One issue got a brand-new type, a custom field, a blocker that appeared on the other issue by itself, and an epic owned by a real person from the employee roster. None of it needed a workaround.
Chore is a type this team added themselves. It works exactly like the nine built-in types.