Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

With the new version came a few improvements. We’ve cleaned up the interface, allowed for keeping the history of updates in a visible place, but we’ve also changed the structure of how the OKRs are built.

  1. You can see the whole hierarchy in the main view

    In the previous version, you had a main board with a list of your objectives, but without the KRs. Now the KRs are included and their progress is counted to the progress of the objective. So you must have at least one KR to be able to see the progress of the objective.

    You can still create multiple sub-objectives for different levels of hierarchy and decide if their progress is counted to the higher-level objective’s progress.

  2. KRs have more functionality and context

    Each KR has a page of its own for more detailed tracking of progress with KR-specific updates and assigning issues to specific KR.

    Each KR has an owner - we know that it’s important for bigger teams to be able to assign KRs under the objective to different people. After the transition, the owner field on KRs will be the same as the objective’s and you can change it later.

    Each KR has a status. They will now inherit the status from the objective, but you can track them separately.

  3. Connect issues directly to the KRs

    Issues linked to the whole OKR will stay on the objective page underneath so that you won’t lose them. But if you were to link new issues, you’d need to choose a specific KR to link it. You can re-connect already connected issues to the KRs as well.

  4. Transition to simplified periods next quarter
    We simplified the added a concept of the OKR’s period with simplified OKRs' periods that include quarterly and yearly options- as it is the best practice to plan for the quarters. You can also create custom periods. Your current OKRs will keep custom the dates for the start and the due date , but If you’d want to move a current OKR to the next period or create new ones, you’d have to select from the simplified options. You can contact us if you work with a different OKR period and you’d like to define a custom period for your instanceand you can create a custom period from them in order to unify dates between your OKRs and filter them on the main board.

  5. Update KRs and objectives regularly

    Until now, you’ve changed only the value of the KRs and the objective’s status. Now you can post regular updates on both objectives and KRs so that all people interested could see how the work on the objective or on a KR progresses. Updates are stored in the “Updates section” on the KR page and in the Activity tab on the KR page.

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
cqllabel in ( "okrs" , "objective" , "kr" )