Change an epic's priority
An epic never runs by itself: its subtasks do. Each subtask takes the epic's priority when it is created, and changing the epic's priority later changes every subtask that isn't finished. Lower a large epic to let other work go first, or raise it when its result is needed sooner. Priority decides which queued task starts first; it doesn't stop or restart anything.
Who can do this: anyone with edit access to the epic's project. Others see Priority but can't change it.
- Open the epic and select its Task tab.
- Select Advanced. Priority sits just before Throttle.
- In Priority, pick the new level. The levels, highest first, are Urgent, High, Normal and Low.
- Select Save. The epic keeps running as it was.
- Check a subtask. Open it from the epic's list of subtasks, select its Details tab, then Timeline. A new row records the change; open it to read it, such as Priority: Normal → Low.
- Back on the board, queued subtasks show the new level's mark beside their names: ⇈ for Urgent, ↑ for High, ↓ for Low, and none for Normal.
Only subtasks that are not done and not archived take the new level. A subtask that is already running keeps running; the level matters the next time it waits in the queue. Subtasks the epic creates later, such as the build tasks its plan adds, start at the new level too.
To give one subtask a different level from the rest, change that subtask's own Priority after the epic's, as in Move a queued task up the queue. The next change to the epic's priority overwrites it.
Related
- How epics and features work: how an epic's subtasks are created and run.
- New task › Advanced: Priority and every other setting under Advanced.
- Limit how many subtasks run at once: cap the epic's subtasks instead of reordering them.