Skip to main content

Filter aligned OKRs on the Aligns tab

When an objective has dozens of OKRs aligned beneath it, the Aligns tab can get long fast. Filtering lets you narrow the view to just the slice you care about - a specific team, a time period, or open items only - so you can run alignment reviews and drill into objectives without scrolling through everything.

When to use filtering

Filtering the Aligns tab is useful when you need to focus on a subset of aligned work, for example:

  • "Show me only the Sales team's OKRs aligned to this annual objective."

  • "Show me only the Q1 OKRs aligned to this objective."

  • "Show me Sales team Q1 OKRs aligned to this objective."


How to use it

  1. Open the objective and go to its Aligns tab;



  2. Select the Filter button. The filter panel opens;

  3. Choose your filter fields and values;


  4. Select Apply to update the tree, or Reset to clear everything.


Filtering is completely optional. If you don't set any filters, every objective below the root shows unfiltered.

Available filters

Filter

Options

Notes

Objective Status

Open / Closed

Defaults to Open.

Time Period

One or more WorkBoard time frames (Q1–Q4, H1, H2, FY, or a custom date)

Choose an operator: falls within or exactly equals.

Team

Multi-select from your team directory

N/A


What actually gets filtered

  • The filter applies only to the OKRs aligned below the objective you're on. That objective stays pinned at the top and is never filtered out, and nothing above it in the hierarchy is affected.

  • It uses a hide model: any objective that doesn't match is hidden along with everything beneath it.

Combine multiple values

Team and Time Period accept multiple values. Each value you pick appears as a removable chip in the filter row.

  • Within a single field, values combine with OR.

  • Across different fields, filters combine with AND.

Example: Team = Product, Engineering and Time Period = Q1, Q2, Q3 shows objectives owned by Product or Engineering

To remove a value, select the x on its chip. Removing all chips from a field returns it to the empty state, and that field is ignored the next time you apply. An empty filter row does not affect your results.

Did this answer your question?