Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review and categorize on-call tickets #49

Closed
robrap opened this issue Jul 29, 2022 · 8 comments
Closed

Review and categorize on-call tickets #49

robrap opened this issue Jul 29, 2022 · 8 comments
Assignees
Labels

Comments

@robrap
Copy link
Contributor

robrap commented Jul 29, 2022

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

@robrap robrap added the on-call label Jul 29, 2022
@robrap
Copy link
Contributor Author

robrap commented Jul 29, 2022

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 robrap removed the backlog To be put on a team's backlog or wishlist label Apr 20, 2023
@robrap
Copy link
Contributor Author

robrap commented Apr 21, 2023

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 jristau1984 self-assigned this Jul 1, 2024
@jristau1984 jristau1984 moved this from Prioritized to In Progress in Arch-BOM Jul 1, 2024
@jristau1984
Copy link

jristau1984 commented Jul 1, 2024

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

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

@jristau1984
Copy link

jristau1984 commented Jul 1, 2024

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
Copy link

jristau1984 commented Jul 1, 2024

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

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

@jristau1984
Copy link

openedx/edx-platform#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
Copy link

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
Copy link

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

@github-project-automation github-project-automation bot moved this from In Progress to Done in Arch-BOM Aug 26, 2024
@jristau1984 jristau1984 moved this from Done to Done - Long Term Storage in Arch-BOM Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done - Long Term Storage
Development

No branches or pull requests

2 participants