Complete Migration of HAML component instances to Pajamas => 52.4%

This is follow on work to #8789 (closed).

Overall Epic that is collecting the overall work - gitlab-org&3963 (closed) and supports UX OKR: &1043 (closed)

The plan for this quarter is to complete this work.

Note on the score: I've put it down as 52.4% as this is the current completion percentage from the main epic. However, 200 of these issues were completed in the previous quarter. In terms of how much closer we got to our goal, this KR could equally be scored at 23.6%.


Progress

Component Epic Completed % Notes
😄 Alerts gitlab-org&4070 (closed) 52/56 92.8% This has been largely driven by community contributions
😐 Buttons gitlab-org&4001 (closed) 97/192 50.5% The community has been a big help here too
😬 Modals gitlab-org&4386 4/25 16%
😬 Dropdowns gitlab-org&4549 2/70 2.8%
Pagination 0/0 100% This was complete before we started, easy win
😬 Tabs gitlab-org&3983 0/53 0%
😄 Popovers gitlab-org&4409 (closed) 8/12 66.6% These were completed, it seems we found some more 🤔
😄 Tooltips gitlab-org&4383 (closed) 108/109 99% The epic was created after work started so the number in the epic is only for the remaining quarter of the issues
- - - - -
😐 Total 271/517 52.4%

Retro

Progress on this initiative slowed down a lot this quarter. In FY21-Q3 we migrated 199 components. In this quarter we only migrated 72.

There were a number of factors that lead to the decrease in numbers:

  1. It was a slow quarter generally. With the holiday season right in the middle of the quarter, there were less people looking at it.
  2. The "easy" issues have mostly been picked up. We had a lot of quick wins in the last quarter. The issues we're left with are the tricker, larger ones.
  3. There was a lot less visibility this time around. I (@samdbeckham) didn't promote this KR/Epic as much as I did in the previous quarter.

Good

  1. As it was before, the community involvement was high. Hosting this topic at the hackathon really helped.
  2. @aturinske has been a big help in getting tabs started and general triaging
  3. A portion of these issues were fixed outside this effort as general feature / tech debt work.

Bad

  1. We didn't focus on larger components. In the last retro we wanted to try this, but we didn't.
  2. As a result of the above, there has been little-to-no movement on dropdowns and modals.

Try

  1. Categorising the remaining issues by stage / group. We may be able to get them scheduled in as regular product work. I've spoke with @stanhu about unleashing Tanukibot on these issues to aid in this effort.
  2. Triaging these issues. We've done light triaging periodically for buttons and alerts, but there's likely some issues that can be closed now due to them being fixed as part of regular product work.
  3. HYPE! We've done a great job in the last two quarters generating interest with the larger community, we should push on doing the same within GitLab
Edited by Sam Beckham