Repositories and project boards
This page describes how task management is set up in the GitHub organisation samt-x as of October 2026.
One repository per board
| Work area | Repository | Project board | Template |
|---|---|---|---|
| Pilot 1 – Seamless transition between lower and upper secondary school | samt-bu-pilot-1 | Project 1 | Standard |
| Pilot 2 – Choice of educational pathway | samt-bu-pilot-2 | Project 2 | Standard |
| Pilot 3 – Moving between municipalities | samt-bu-pilot-3 | Project 4 | Simple |
| Pilot 4 – Diplomas | samt-bu-pilot-4 | Project 3 | Standard |
| Pilot 5 – Identifiers in education | samt-bu-pilot-5 | Project 9 | Standard |
| Pilot 6 – Parents’ access to data | samt-bu-pilot-6 | Project 10 | Standard |
| Framework and generic architecture | samt-bu-architecture | Project 5 | Standard + Proposed |
| Information models | information-models | Project 6 | Standard |
| Shared tasks across pilots | samt-bu-common-tasks | – | – |
| The website docs.samt-bu.no | solution-samt-bu-docs | – | – |
| Task management | solution-task-management | – | – |
| The portfolio (one card per work area) | samt-bu-portfolio | Project 13 | Own setup |
Note: Project 3 belongs to Pilot 4, and Project 4 to Pilot 3. The numbers were assigned in the order the boards were created, and cannot be changed.
Project 7 and Project 11 are templates for new boards, see below. Project 12 «SAMT-BU All tasks» is the aggregate board, see The aggregate board below. Project 13 is the portfolio board, with one card per pilot, product and work area. Its Status field is the phase.
The pilot repositories also hold the pilot’s pages on docs.samt-bu.no. Tasks and content are therefore in the same repository.
Board names
All boards are named «SAMT-BU» followed by the work area, for example «SAMT-BU Pilot 3 – Flytting av barn og unge i skoleåret». The prefix distinguishes the boards from other projects participants have in GitHub.
Automation
Each board has an automatic rule (Auto-add): all open issues in the linked repository are added to the board. When an issue is closed, its status is set to done.
Templates for new boards
| Template | Board | Statuses |
|---|---|---|
| Simple | Project 11 «[TEMPLATE] Simple board» | To do, In progress, Done |
| Standard | Project 7 «[TEMPLATE] Standard board» | To do, Ready, In progress, In review, Done |
Both templates have the fields Responsible, Priority, Effort, Estimate (person-days), Start date and Due date, and five views: Board (kanban by status), By responsible (kanban by responsible person), Open tasks, My tasks and Timeline. What the statuses and fields mean is described under Conventions.
To create a new board:
- Choose New project in the organisation and pick one of the templates.
- Name the board following the pattern below.
- Link the board to the repository, and set the rule for automatic adding (see Automation).
- Add the people as options in the Responsible field.
The boards that existed before the templates were moved over to them in October 2026 (M2 Templates in use). The statuses were renamed, and no task lost its status. Project 5 also has the step Proposed, the field Contributors and the views All tasks and Closed tasks.
The aggregate board
Project 12 «SAMT-BU All tasks» collects all issues in the public repositories. Private repositories are not included. The status is translated to the shared level (see Conventions): Not started, In progress or Done. Closed issues become Done, and open issues without a board become Not started. The field Source status shows the board and the status the task has there.
The board is filled by the workflow Sync All tasks in the repository solution-task-management, every hour and when run manually. The sync goes one way only, and never writes to the project boards. All automatic rules on the aggregate board are switched off, and must stay that way. Access is described under Technical documentation.
Access
Access is granted through teams in the organisation. Each pilot has a team with the same name as the repository, for example samt-bu-pilot-3, with write access to the pilot’s repository. The core team has write access to all the repositories.
Exceptions
Two comments given on pages on docs.samt-bu.no appear on the board for Pilot 4, but live in the samt-bu-docs repository. The comment panel on the website only finds comments in that repository, so they cannot be moved.