Use epics for Q1 FY2021 OKR Tracking
In order to track more accurately and list our OKRs, we should utilize GitLab epics for OKR tracking, updates, and planning.
The initial thought would be an
Objective would be an epic and a
Key Result would be issues attached to those epics.
**A potential structures could be: **
CEO: Popular next generation product - Epic --Deliver on product roadmap - Child Epic ----Achieve 100% of our category maturity plans - Issue ----Another objective would be a child epic here and that would have it's own MRs and issues
FY20-Q4 OKRs - Epic
--CEO: Popular next generation product - Child Epic
----Deliver on product roadmap - Child Epic
------Achieve 100% of our category maturity plans - Issue
Some other ideas:
- Dynamically generate handbook page of OKRs based on an OKR label
- View groupings/relationship of Objectives and KRs on handbook page (i.e. nested epics/issues)
- Dynamically calculate progress based on task list of an issue. As a follow on, epics could average the progress of their attached issues. As a last iteration, this progress could be surfaced on the OKR handbook page.