Create General "Controls Work" Project Board

[ThomasLohnert]

One of the things discussed as part of the away day was that we as a group would like to remove the distinction between IBEX and other work of the Controls Group (e.g. HLM).

To this end, we should look into creating a project board that contains tickets from other projects alongside IBEX work so it is all collected in one place and visible to everyone in the group. The new style Github projects allow incorporating tickets from multiple repositories. We should use this feature to set up a general "Controls work" project board to eventually replace the IBEX Project Board

Acceptance Criteria

What is the acceptance criteria?

• [ ] We have a project board that incorporates tickets from IBEX as well as other project work
• [ ] If possible, modify our git automation features so that they are preserved for our new project board
• [ ] Either the project board checks are fixed for any automation changes, or a ticket is created to make that fix

How to Test

verbose instructions for reviewer to test changes (Add before making a PR)

[KathrynBaker]

This has already been started, and a draft is available at https://github.com/orgs/ISISComputingGroup/projects/5/views/1.

The scope for multiple repos is organisation level, and HLM for example is in ISIS Neutron Muon rather than our org, however, the notes in the non-classic projects will still allow visibility, and a link to the other repo put in the expanded session. Closed items can still be automated easily, the scripted ones (related to labels etc) potentially less so, but that is now something that can be looked into.