Skip to main content

Filters in a Context view

Does this apply to you? Look at your sidebar. If it has a Context entry, yes. If it still lists Performance Delivery, Project Financials and AI Return separately, your organization hasn't moved yet — read Editing and filtering Views and Filters and Comparison Options instead.


​

This is the part of Context that changes how the screen behaves. The filters belong to the view, not to the tab. You set them once in the top bar, and every tab answers with that scope — so the date range you pick while looking at flow is the same one DORA, cost and AI answer with.


​

Before Context, each dashboard carried its own filters and you re-applied them as you moved between screens. That's the step that's gone.


​

What you can filter by


​

  • Date range — the usual presets, plus Year to date and Custom range.

  • Teams — the view's own teams. A view created with no teams shows every team you can see.

  • Projects and Repositories — the scope of boards and code.

  • Work items — the issue-type selector. This is the one people look for under another name; there is no separate filter for labels or workflow stages.

  • Parent tasks — narrow to work under specific parents. Pick projects first, or type two letters to search.

  • Rework exclusions — transitions this view shouldn't count as rework.


​

Each filter you apply shows as a chip in the bar, and each chip can be removed on its own. Clear all empties them in one go.


​

Who can change them


​

This is where a shared view differs from your own, and it's worth knowing before you wonder why a control is greyed out. There are three levels:


​

If the view is…

Date range

The other filters

Yours

yes

yes

Shared with you as editor

yes

yes

Shared as viewer, with dates

yes, your own

no

Shared as viewer

no

no


​

Two consequences worth stating plainly:


​

An editor's change is everyone's change. Editing a shared view's filters writes them into the owner's view — the next person to open it sees your scope, not the one they left. If you want a different cut, duplicate the view instead.


​

A viewer sees the view as its owner left it. The message says so: Only the owner of this view can change its filters. The one exception is viewer with dates, where your date range is yours alone — the owner's other filters still apply, and moving your dates changes nothing for anybody else.


​

What the filters do and don't reach


​

Filters scope the data a tab computes. They don't change which tabs the view has, and they don't change what each tab shows — that's Edit metrics, covered in Building a view in Context.


​

One thing that behaves differently on purpose: an AI report is written from the view's data at the moment it runs, and then it stops moving. If you change the filters afterwards, the report says so rather than silently going stale — it tells you its period no longer matches the view's.


​

Related articles


​

  • What is Context?

  • Building a view in Context

  • Sharing a Context view

Did this answer your question?