[Security Team] Instructions for using the Security Management board
Problem: Most of the subteams (and some of the larger projects, such as ZTN) have split into multiple projects and subgroups under
gitlab-com/gl-security, so issues created in those projects can not be tracked in a board created under a single subproject (https://gitlab.com/gitlab-com/gl-security/engineering/boards/1085717?&label_name=Security%20Management). Having to create a new related issue under
gitlab-com/gl-security-engineering for any issue in the other projects that need to appear on that board creates busy work for the team and would require multiple clicks through issues to get to the actual work for someone trying to understand the current state.
- Create a board at the group level: https://gitlab.com/groups/gitlab-com/gl-security/-/boards/1122898?&label_name=FY20Q2
- Simplify the labels by creating a scoped label
Security Management::<Team>for all the sub teams.
- Add a new label for
~FY19Q2so that items can be easily tagged if they need to be added to or moved to separate boards for each quarter. This may make more sense as a Milestone or Epic, but for this first iteration, I already was scripting making changes to the labels, so just kept it to that).
Once I got done fighting with some of the limitations of the
labels related API, actually making the changes to already labelled issues is pretty easy, so all of this is easy to iterate on.
I also created a
security-managers group, similar to the
support-managers group, but wasn't sure if all the team members listed as interim managers in
team.yml should be added.
@kathyw This is all based on the conversation we had about tracking work across the multiple projects we have split under
gl-security without having to create duplicate issues in the
engineering project for work you want to show up in that board.