Feature priority

Who can use it: Project Managers and Super Admins set priority. Everyone on the project, clients included, can see it.

Each feature can be High, Medium, Low or Not set (the default).

Use case

The Harbor project has fourteen features. In the weekly call, Tom says reordering matters most before the holiday season. Ravi sets REQ-4 to High, sorts the list by priority, and shares the screen. Everyone sees the same order, and Arjun knows what to pick up next.

flowchart LR
    H["High<br/>REQ-4, REQ-7"] --> M["Medium<br/>REQ-2, REQ-9"] --> L["Low<br/>REQ-11"] --> N["Not set<br/>REQ-12, REQ-13"]

Sorted by priority: High first, then Medium, Low and Not set. Features with the same priority are ordered by key.

Set a priority

1. Open the feature.
2. Pick High, Medium or Low under the title. Pick Not set to clear it.

Note

Changing the priority doesn’t touch the requirement, its version or its sign-offs, so you can change it at any stage except Discarded. Every change is recorded in the feature’s history.

Filter and sort

On the feature list:

• Filter by one or more priorities, including Not set. For example, show High and Medium only.
• Sort by priority instead of by key.