Skip to main content

Naming Your Levels

Clears organises work in four levels. You can choose what your account calls each of them, so Clears reads the way your team already talks. For example, an Azure DevOps team can see Epic / Feature / User Story / Task instead of Clears' own names.

LevelClears' nameWhat it holds
Level 1InitiativeGroups epics
Level 2EpicGroups stories
Level 3StoryThe unit of work Clears analyses and executes
Level 4SubtaskOne step of a story, implemented by the AI agent

The names only change how the levels are displayed. The levels themselves, and how Clears works with them, stay the same.

Presets​

Pick a preset, or edit the names to make your own:

PresetLevel 1Level 2Level 3Level 4
JiraInitiativeEpicStorySubtask
Azure DevOps (Agile)EpicFeatureUser StoryTask
CustomYour namesYour namesYour namesYour names

Note that the Azure DevOps (Agile) preset moves the names down one level: Azure DevOps' Epic is Clears' initiative, and Azure DevOps' Feature is Clears' epic. This matches how Clears 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 Clears' 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.

  1. 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).
  2. Check the preview line under the levels, for example "A Feature groups User Stories; a User Story is split into Tasks".
  3. 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 Clears web app: the Board, the Epics page (its menu entry and page title use your plural name for Level 2), 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 Clears' own names, so an assistant still calls search_user_stories, even when your account calls stories Product Backlog Items.

Everything else keeps Clears' own names (initiative, epic, story, subtask):

  • Slack and Microsoft Teams messages
  • Emails
  • The names Clears uses in Jira and Azure DevOps themselves. Your work item types are never renamed.