Naming Your Levels
Zero0 organises work in four levels. You can choose what your account calls each of them, so Zero0 reads the way your team already talks. For example, an Azure DevOps team can see Epic / Feature / User Story / Task instead of Zero0' own names.
| Level | Zero0' name | What it holds |
|---|---|---|
| Level 1 | Initiative | Groups epics |
| Level 2 | Epic | Groups stories |
| Level 3 | Story | The unit of work Zero0 analyses and executes |
| Level 4 | Subtask | One step of a story, implemented by the AI agent |
The names only change how the levels are displayed. The levels themselves, and how Zero0 works with them, stay the same.
Presets
Pick a preset, or edit the names to make your own:
| Preset | Level 1 | Level 2 | Level 3 | Level 4 |
|---|---|---|---|---|
| Jira | Initiative | Epic | Story | Subtask |
| Azure DevOps (Agile) | Epic | Feature | User Story | Task |
| Custom | Your names | Your names | Your names | Your names |
Note that the Azure DevOps (Agile) preset moves the names down one level: Azure DevOps' Epic is Zero0' initiative, and Azure DevOps' Feature is Zero0' epic. This matches how Zero0 reads your Azure DevOps work item types (see Azure DevOps Integration).
Custom is selected for you as soon as the names differ from both presets. If you edit the names back to exactly a preset's, that preset is selected again.
Your Tracker's Default
An account that has never chosen its names follows its issue tracker:
- Azure DevOps accounts use the Azure DevOps (Agile) preset.
- Jira and standalone accounts use the Jira preset, which are Zero0' own names.
Once your account chooses names, either in the onboarding wizard or in Settings, it keeps them, whatever tracker you connect later.
Choosing Names During Onboarding
The onboarding wizard has a Name your levels step right after your tracker is connected, or right after your VCS provider in standalone mode (see the onboarding guide for Jira, Azure DevOps or standalone). It starts on your tracker's preset. When an admin clicks Continue, the names shown are saved, even if they weren't changed.
Editing the Names in Settings
Open Settings → Level naming. Every member can see the names; only users with the Admin role can change them.
- Choose a preset, or edit the names directly. For each level, set:
- the article used before the name: a or an (for example, an Epic, a Feature);
- the Singular name (for example, User Story);
- the Plural name (for example, User Stories).
- Check the preview line under the levels, for example "A Feature groups User Stories; a User Story is split into Tasks".
- Click Save.
The names must follow these rules:
- Every singular and plural name is required, and is 1 to 40 characters long. Spaces at the start and end are removed.
- No two levels may share a name. The singular names are compared ignoring case, so "Epic" and "epic" count as the same name.
To go back to your tracker's default, click Reset to Jira preset or Reset to Azure DevOps preset. Your account then follows its tracker again, as if it had never chosen.
Where the Names Are Used
Only two places use your account's names:
- The Zero0 web app: the Board, the work item views and the rest of the UI.
- The MCP server: the answers and tool descriptions that AI assistants read. The tool names don't change: they keep Zero0' own names, so an assistant still calls
search_user_stories, even when your account calls stories Product Backlog Items.
Everything else keeps Zero0' own names (initiative, epic, story, subtask):
- Slack and Microsoft Teams messages
- Emails
- The names Zero0 uses in Jira and Azure DevOps themselves. Your work item types are never renamed.