Page MenuHomePhabricator

Update selectable OKRs in xLab UI
Closed, ResolvedPublic2 Estimated Story Points

Description

As an experiment owner, I need to be able to select the OKR that I am conducting my hypothesis/experiment under.

AC

  • FY24/25's OKRs pruned/updated to just:
  • SDS 2.4
  • WE 1.7
  • FY25/26's OKRs added (note: not all the KRs, just the ones that we either know will use our system for sure or may):
  • WE 1.1 (Constructive edits for new contributors)
  • WE 1.2 (Collaboration impact)
  • WE 2.1 (Improve state of vital content on Wikipedias)
  • WE 3.1 (Engaging new audiences)
  • WE 3.2 (Diversifying donation opportunities)
  • WE 3.3 (Engaging core audiences)
  • SDS 2.1 (Experimentation Platform)
  • Formatting is FY##/## <Bucket code> #.# (e.g. "FY24/25 SDS 2.4", "FY25/26 SDS 2.1"), without the dot between bucket code and objective number:

Screenshot 2025-06-17 at 7.34.38 AM.png (732×650 px, 53 KB)

  • Because the proposed approach is creating a new okrs table in the database to avoid hardcoding them, database on staging and production must be updated accordingly to have this new table and the corresponding data

Event Timeline

mpopov updated the task description. (Show Details)
Milimetric set the point value for this task to 2.

sfaci opened https://gitlab.wikimedia.org/repos/data-engineering/mpic/-/merge_requests/202

Added okrs as a table in the database accesible via /okrs endpoint for the frontend

The above MR doesn't address the mentioned changes but make the needed changes in xLab for OKRs to live in a new table in the database. Frontend can take that data via a new non-public endpoint, /okrs implemented in the backend. So far OKRs were hardcoded in the frontend Vue component and that required code changes just to update them.

So, after merging and deploying this change we will be able to simply update the okrs table to remove/add/modify OKRs as we need

Sfaci updated the task description. (Show Details)
Sfaci updated the task description. (Show Details)

cjming merged https://gitlab.wikimedia.org/repos/data-engineering/mpic/-/merge_requests/202

Added okrs as a table in the database accesible via /okrs endpoint for the frontend

Change #1162089 had a related patch set uploaded (by Clare Ming; author: Clare Ming):

[operations/deployment-charts@master] xLab: Deploy v0.7.2 release to staging

https://gerrit.wikimedia.org/r/1162089

Change #1162089 merged by jenkins-bot:

[operations/deployment-charts@master] xLab: Deploy v0.7.2 release to staging

https://gerrit.wikimedia.org/r/1162089

@Sarai-WMF @EChukwukere-WMF This change is already deployed on staging for you to review

Looking good! No design-related issues were identified 🎉

Test status: QA PASS

  • WE 1.1 (Constructive edits for new contributors) : Able to Add and remove this OKR. OKR field stays optional after activation
  • WE 1.2 (Collaboration impact) : Able to Add and remove this OKR. OKR field stays optional after activation
  • WE 2.1 (Improve state of vital content on Wikipedias) : /Able to Add and remove this OKR. OKR field stays optional after activation
  • WE 3.1 (Engaging new audiences) : /Able to Add and remove this OKR. OKR field stays optional after activation
  • WE 3.2 (Diversifying donation opportunities) : /Able to Add and remove this OKR. OKR field stays optional after activation
  • WE 3.3 (Engaging core audiences) : Able to Add and remove this OKR. OKR field stays optional after activation
  • WE 3.3 (Engaging core audiences) : /Able to Add and remove this OKR. OKR field stays optional after activation
  • SDS 2.1 (Experimentation Platform) : Able to Add and remove this OKR. OKR field stays optional after activation

Change #1165182 had a related patch set uploaded (by Clare Ming; author: Clare Ming):

[operations/deployment-charts@master] xLab: Deploy v0.7.5 release to production

https://gerrit.wikimedia.org/r/1165182

Change #1165182 merged by jenkins-bot:

[operations/deployment-charts@master] xLab: Deploy v0.7.5 release to production

https://gerrit.wikimedia.org/r/1165182