The Execution Hierarchy screen is where you decide which level each connected provider's issue type belongs to — Initiative, Project, or Task.
Default state and adding levels
A brand-new organization starts with zero project levels and one fixed Tasks level that can't be removed or reordered — it's always last. Click + New Level between existing levels to insert a new one, named "New Level" until you rename it; at least one project level is required to save.
Rename, remove, and assign
- Rename a level by typing directly into its title.
- Remove a level with the x next to its title — disabled if it's the fixed Tasks level, or if it still contains any issue types (remove those first).
- Assign an issue type to a level by dragging its chip from one level into another. Newly detected issue types are auto-injected into Tasks with a green "new" badge until you move them.
Only whole issue-type chips are draggable — you can't drag an entire level to reorder it; a level's position is fixed by where you inserted it.
What to do about it
Click Save Hierarchy to commit your changes, or Discard Changes to revert — both only appear once something's changed. This screen only auto-discovers issue types from Jira and GitHub connections; if your organization's only connection is Azure DevOps or Linear, no issue types appear here to assign. See How Execution Hierarchy Works for what the levels mean once configured, and Open and Edit a Project for using them day to day.