Skip to main content

Priorities, labels, and estimates

What priorities, labels, and estimates mean on an Examply task, and how to use them to sort and filter your work.

Priorities, labels, and estimates give tasks context beyond a title and a due date. This article explains what each one means in Examply, how to apply them, and how to use them to sort and filter your work.

None of the three are required to create a task, but a project with consistent priorities, labels, and estimates is far easier to plan around, since Timeline and List views can lean on that data instead of on guesswork.

Priorities

Every task has one of four priority levels. New tasks default to Medium unless you set one explicitly. Priority affects sort order in List view and the color of the flag shown on the task card in Board view.

Priority

Flag color

Typical use

Urgent

Red

Blocking work or a same-day deadline

High

Orange

Due this week, or blocking a teammate

Medium

Yellow

Default priority for planned work

Low

Grey

Nice-to-have, no fixed deadline

Set priority from the task's detail view, or select multiple tasks in List view and set priority in bulk.

Labels

Labels are freeform tags you create per workspace, such as "bug", "design", or "client-facing". Unlike priority, a task can carry any number of labels.

  1. Open a task and click Labels.

  2. Select an existing label, or type a new name and click Create label.

  3. Repeat to add as many labels as the task needs.

Note: Labels are shared across the whole workspace, not just one project. Reuse existing labels where you can, so filters stay useful across teams.

Estimates

Estimates capture how much effort a task is expected to take. Your workspace admin sets whether estimates are entered as hours or story points in Workspace settings → Estimates.

Estimate type

Best for

Hours

Client-services teams that bill by the hour

Story points

Product teams running sprint-based planning

Estimates roll up to the project level, so a project's Timeline view can show total remaining effort alongside dates. Switching a workspace's estimate type doesn't convert existing numbers — tasks estimated in hours keep that number even after a switch to story points, so plan the change for the start of a sprint or billing period.


Tips

  • Filter List view by label to see all "client-facing" or "bug" tasks across every project in a team.

  • Combine a priority filter with a label filter, for example Urgent tasks labeled "bug", to build a focused view for standups.

  • Retire unused labels from Workspace settings → Labels rather than leaving near-duplicates like "bug" and "Bug" in the picker.

Did this answer your question?