Overview for the individual
Tasks live in many repositories and on many boards. This track gives each participant one overview of their own tasks, built up in steps from the simplest.
Steps
| Step | Content | Issue |
|---|---|---|
| A1 Search and view | A ready-made search for your own open tasks across the whole organisation, and the “My tasks” view on the architecture group’s project board. See User guide. | solution-task-management#7 |
| A2 Aggregate board | One board that automatically collects the tasks from all repositories, with a shared status. Builds on the shared status model. Done October 2026: SAMT-BU All tasks. | solution-task-management#8 |
| A3 Personal board | A personal board with its own fields, such as “My status” and “My priority”. | solution-task-management#5 |
| A4 Other git platforms | Tasks from git platforms other than GitHub in the same overview. | solution-task-management#9 |
The aggregate board and the portfolio board are two different things
The aggregate board collects tasks from all boards. The portfolio board in the track Portfolio management has one card per pilot, product or work area. They are kept separate.
Personal board: reads, but does not write back
An issue can be on several boards at once. Closing, assignees and comments belong to the issue itself and are therefore shared by all boards. Status, priority and deadlines belong to the board and are owned by it.
The personal board therefore reads from the project boards, but never writes back to them. The project’s priority and my own priority across projects are two different and equally valid questions. The reasoning is in solution-task-management#5.