Sort feature

This page highlights the use-cases of having a sort feature and solution

Problem Statement

We have multiple views (my objective, all objective, starred & team views) and filter conditions (company/non-aligned, people, team, status, due-date, negotiation, starred etc) for the user to serve different needs. In each of these use-cases the user wants to see the OKRs in a specific order. Currently we are trying to solve this by having a default sorting order for views and a different sorting order for filter output. However, we should enable the user to take this action and sort things in the order they want. Also, another reason is that the user today does not know our default sorting logic.

One can Sort a view before or after applying filters

Sorting Conditions

• Last updated at (Latest first) - P0

• Due-date (Overdue -> closer dates; Negative to positive diff ) - P0

• Progress (Lowest first) - P0

• Status (sorting order?) - P1

• Created at (default sorting order) -P1

• State (in-negotiation first and then rest) - P2

• Type of objective (company versus non-aligned) along with depth - P2

Sorting logic

Questions?

1. Does the sorting output result in a flat view or not? If not does the sorting logic apply to only Objectives? or does it apply to Key-results also?

2. Is it good that the user sees a change in order of key-results if it applies to O and then to key-results?

3. Does the sorting logic stay permanent? Can the user make a sorting logic permanent? If not when does the sorting logic change?