Sitewide: migrate from ZH to Github Projects

[jilladams]

Migration

Brain dump:

Project

• [x] Create project: https://github.com/orgs/department-of-veterans-affairs/projects/1442/views/1
• [x] Config custom fields
  • [x] sprints
  • [x] points
  • [x] ~Teams?~ Only can have single value, so leaving as Labels
  • [x] Status (sprint board columns
• [x] Config workflows
  • [x] auto add new cms sitewide label issues
  • [x] auto add new team sitewide label issues
• [x] Make a Priority custom field
  • [x] Ask PMs what levels should be
  • [x] Add it to the board card visibility

Issues / Epics

va.gov-team tix

Epics: https://github.com/department-of-veterans-affairs/va.gov-team/issues?q=is%3Aissue%20state%3Aopen%20label%3Asitewide%20label%3AEpic

• [x] Make sure we have a list of tickets within each epic
• [ ] Import relevant issues into project (Issues tab, check all, select Project from dropdown, 25 per page)
• [ ] Build parent/child relationships for each epic
• [ ] Map points from GH issue to GHP card

va.gov-cms tix

Epics: https://github.com/department-of-veterans-affairs/va.gov-cms/issues?q=is%3Aissue%20state%3Aopen%20label%3Asitewide%20label%3AEpic

• [ ] Make sure we have a list of tickets within each epic
• [ ] Import relevant issues into project (Issues tab, check all, select Project from dropdown, 25 per page)
• [ ] Build parent/child relationships for each epic
• [ ] Map points from GH issue to GHP card

Flagged Facilities

FIgure out:

• Can we make a board for them?
• Can tickets live in 2 boards?
• Can boards sync lanes?

Left behinds

We have 1131 open sitewide tix across CMS / team repos, and GHP project issue cap = 1200. We can't bring in all our tickets. This is the list of things we are leaving behind:

Sprint board

• [ ] Confirm lane name revisions with the team
• [ ] Config the sprint card view - which fields to show / hide
• [ ] Config the slices
• [ ] If we did Discipline as a field, we could make Discipline lanes in the board, but: lots of our tix have 2+ disciplines. Talk to team about it.

Monthly reporting

Opportunities

Roadmap

How can we use this for quarterly priorities?

Planning

Can we use a view to deal with sprint planning? Look at Oddball template "Planning" view

[jilladams]

@FranECross @Agile6MSkinner we have an Opp to add a JIRA-like "priority" field in Github Projects.

1. Do you want that?
2. If so, what levels of priority are most useful for planning purposes?

[Agile6MSkinner]

@jilladams Yes please. On what to use there, I haven't felt like we've had the most success with MoSCoW, and I'm wondering if we shouldn't move to something with less semantic baggage, like "Critical, High, Medium, Low" or even more simple: "P0, P1, P2, P3"

[jilladams]

I was also pondering "Emergent" - a la COVID, or this alternative banners thing. Do you think that's the same as "Critical"?

[Agile6MSkinner]

I think "Emergent" is the same thing as "Critical," although the fact that there's even some semantic noise there does lend credence to the idea of P0 - P3, with P1 being the default high priority and P0 being outside-the-norm issues