Review and categorize on-call tickets

edx / edx-arch-experiments

A plugin to include applications under development by the architecture team at edx

GNU Affero General Public License v3.0

0 stars 3 forks source link

Review and categorize on-call tickets #49

Closed robrap closed 1 month ago

robrap commented 2 years ago

Review and categorize existing on-call tickets into milestone(s) such that we could prioritize as a team.

Clarify (through labels, or some means) which tickets are to reduce on-call toil, vs which tickets are just BOM ownership work that had no home.
Search GitHub issues with on-call label.
Search JIRA tickets: https://2u-internal.atlassian.net/wiki/spaces/AT/pages/16387065/On-Call+Arch-BOM#On-call-Improvements.
Should we move JIRA tickets that were "prioritized" (i.e. above the line)? Note: if the tickets contain private info, we may need to reference the JIRA ticket.

robrap commented 2 years ago

Note: I was hoping to do this while on-call, but did not get to it. Do we want to leave this as a ticket on the board, or move it to backlog and do it during a warm down phase from active work?

robrap commented 1 year ago

Note: We may need to ticket looking at the rest of the backlog as well: https://2u-internal.atlassian.net/jira/software/projects/ARCHBOM/boards/612/backlog

jristau1984 commented 3 months ago

First improvement: Remove the "P2 - On call Routine" priority option

[x] Review the content in the "on-call" label, and ensure it is appropriate to leverage (only 2 items)
[x] Add "on-call" label to all tickets in this priority bucket (20 items)
[x] Update the "P2 - On-call" items on the board to "P2 - Quick Win"
[x] Remove the priority from all applicable items
[x] Remove the priority from the project config

jristau1984 commented 3 months ago

I was unable to apply the on-call label to 3 of the 20 items. This is due to

one being a PR in devstack repo where that label does not exist.
one being in the ecommerce-scripts repo where that label does not exist. (this ticket is Done, so it is a problem)
one being in the edx-platform repo where that label does not exist.

I have moved the two un-Done tickets to the "On-Call" status for now, and will tackle them when I retire that status.

jristau1984 commented 3 months ago

Second improvement: Remove the "On-Call" status option

[x] Add "on-call" label to all tickets in this status (7 items)
[x] Update the " On-call" items on the board to "Prioritized"
[x] Remove the status from all applicable items
[x] Remove the status from the project config

jristau1984 commented 3 months ago

https://github.com/openedx/edx-platform/issues/32671 is the only remaining on-call item that cannot be labelled. Given that it is a year old and has had lots of activity on it, I presume this should just have the on-call label dropped? @robrap any thoughts on how to deal with this lingering item?

jristau1984 commented 2 months ago

I have transferred about 1/3 of the Jira backlog into Github. This will continue in my free time until they are all moved and in a status that allows them to be re-reviewed by the team.

jristau1984 commented 1 month ago

There is now a process for reviewing the priority of tickets (including on-call tickets) during the weekly backlog refinement meeting.