Issue originates as changes to infrastructure
Pull requests that update a dependency file
Pull requests that update Docker code
Pull request from a developer outside the Altinn teams.
Issues highlight areas where team members aim to gain experience during Freeday on Fridays
Pull requests that update GitHub Actions code
Issues that are easy to fix for new team members or external contributors (org-wide)
Non functional, often repeating tasks.
Improvements or additions to documentation
Questions raised should be labeled with this.
Used for issues that describes functionality for our users.
Pull requests that update .net code
Issues relevant for Brønnøysundregistrene.
Issues relevant for Digitaliseringsdirektoratet
Issues relevant for Skatteetaten
Issues relevant for Statistisk sentralbyrå.
Further work depending on the completion of some other task/PoC/issue
Status: When you create an issue before you have enough info to properly describe the issue.
Status: An issue that is closed as a duplicate of another issue.
Awaiting clarification/input from stakeholders etc.
Status: Used when something will not be fixed. Describe why.
Threat modelling considered unnecessary for issue
Threat modelling assumed to be required for issue