Ideas for new GitHub project board

fyliu commented 6 months ago

Dependency

When the Hack for LA boards are all migrated

Overview

These are ideas for useful view and issue fields for the new GitHub project.

Action Items

[x] migrate to new project
[ ] configure project views
[ ] cleanup
[ ] document

Resources/Instructions

I made one using issues copied from Peopledepot in my forked repo, which is roughly based on this one which manages several projects
- A lot of the categories we used the generic labels for in the past can be converted into issue fields to be more useful in displaying in views
- feature, size, role, ready for, stakeholder, p-feature, PII
- the only caveat is the fields are single-select only
- Added views to show different dimensions of the project
- Kanban board that's basically the old one
  - it can be simplified into Ice Box, New Issue Review, Prioritized Backlog, In Progress, Review, Done
  - note that the reviewer should be the one setting the status to Review. The coder should set the ready for review field and leave it in In progress status or better yet in a new status like Paused
    
    Show
- Attention with filters for different actions and roles
  - converted Question/Review board column into ready for choices
  - converted discussion label into ready for choice
    
    Show
- Sprint planning just to see what it would look like to have 2-week sprints
  
  Show
  ![image](https://github.com/hackforla/peopledepot/assets/1160105/efcfd3d4-173e-4204-971e-05eeea34de65)
- Backlog with filters for different roles
  
  Show
  ![image](https://github.com/hackforla/peopledepot/assets/1160105/76afc6f6-6ce0-45d1-9a61-0df64bc87511)
- Off-path to show issues that are off the designated path (being worked on outside a sprint, etc.)
  - this is just an idea and is what the "Slush" view seems to be for the other project
    
    Show
- Roadmap to show the progression of issues being worked on
  - this seems to need sprints to work. If we don't have those, maybe we can use weekly blocks and mark them as having been worked on for those weeks
  - converting "Feature:" labels into issue fields would allow this view to show the progression for each feature
  - another option is to add start and end dates to each issue and display those
  - automation possibility: these timestamps can be created corresponding to the issue moves to different columns: issue proposed, issue created, work started, work finished, issue completed
    
    Show
- My Issues to show all my issues on the board
  
  Show
  ![image](https://github.com/hackforla/peopledepot/assets/1160105/99e78ea9-f93b-49c4-a005-523b2a91576f)
- Added new fields for the required issue data
- feature, role, size, stakeholder
- Planning to remove some of the columns once they're not used
- hidden for now
- Prioritized Backlog, Question/Review, PR Needs Review, PR Being Reviewed