OKRs
  • About OKRs
  • The market
  • Why build ourselves?
  • Product philosophy
  • Product Decision Record
  • Key milestones
  • Features
    • OKR Unit
    • OKR Views
    • Default Sorting in views and Filters
    • OKR details page
    • Filters
    • Notifications
    • Move and Paste feature
    • Personal Starring ⭐️
    • Due date as an attribute
    • Cloning OKRs to a new quarter
    • Help Section
    • OKR dependency resolution
    • Drag and Drop (Upcoming)
    • Visibility control 🔒
    • Admin Page (Upcoming)
    • Search
    • Sort feature
    • Slack Integration
  • Key Documents
  • Data Strategy
    • Success Metrics
    • Reporting/Metrics Dashboard
  • Program Management
    • Team
    • Working Principles
    • Toolkit
    • Meetings Schedule
    • Product Roadmap
    • Release notes
  • Major links
    • Project Board
    • Design Mockups
    • Feature Discussions Document
    • xto10x Google Drive
    • xto10x Wiki
    • xto10x Slack
    • Staging (OKR tool)
  • Templates
    • Document Template
    • Voice and Tone
Powered by GitBook
On this page

Was this helpful?

  1. Features

Filters

This page describes the type, logic and outcomes of filters on the OKR tool

  • We have 7 filter conditions:

    • Type of Objective: Company and Non-aligned

    • Owner

    • Team

    • State: In-negotiation

    • Status

    • Due-date

    • Label/Tags: Star

  • All 4 categories exists across all views.

  • Do we do Dynamic filters or not? Filter selection one by one or all filters have to be selected first and then we do apply and then only the view changes.

  • Logic of filters:

    • Union results (in same category) Eg: If I choose the status as off-track and dropped. I should be able to see all OKRs that are either off-track or dropped. [Add all of same category]

    • Intersection across categories Eg: If I choose the team as engineering and status as off-track. Then I should be able to see a set of objectives which have team tagged as engineering and status as off-track. Successive filters should apply.

    • In case the intersection has no results to display, it would show no results found/ blank page.

  • Filters apply to the current view of the user (to whatever expansion state). However, we do have the entire tree as per filtered criteria which can be used if user keeps expanding.

  • Filter list only includes people/teams etc tagged to some objectives and not the entire universe of users. In case a user searches for someone who does not own an objective, they would see no results?

  • We would not be saving a user’s filtered view across sessions and hence a new sessions would automatically reset filters.

  • One can reset all filters together to get to the default view

PreviousOKR details pageNextNotifications

Last updated 5 years ago

Was this helpful?