Labels

• area/infrastructure

  Issue originates as changes to infrastructure
• community-contribution-❤️

  Pull request from developers outside the Altinn teams.
• dependencies

  Pull requests that update a dependency file
• Epic
• github_actions

  Pull requests that update GitHub Actions code
• good first issue

  Issues that are easy to fix for new team members or external contributors (org-wide)
• kind/bug

  Something isn't working
• kind/chore

  Non functional, often repeating tasks.
• kind/documentation

  Improvements or additions to documentation
• kind/feature-request

  New feature or request
• kind/question

  Questions raised should be labeled with this.
• kind/user-story

  Used for issues that describes functionality for our users.
• review/db-migration
• solution/apps

  Issues related to apps or the Altinn Apps infrastructures.
• solution/platform

  Issues related to Altinn Platform solutions.
• solution/sbl

  Issues related to SBL in Altinn 2
• solution/studio

  Issues related to Altinn Studio
• solution/tul

  Issues related to TUL in Altinn 2
• status/blocked

  pending the completion of some other task/PoC/issue
• status/candidate-next-sprint

  Tag to consider including in the next sprint
• status/draft

  Status: When you create an issue before you have enough info to properly describe the issue.
• status/duplicate

  Status: An issue that is closed as a duplicate of another issue.
• status/pending-feedback

  Awaiting clarification/input from stakeholders etc.
• status/wontfix

  Status: Used when something will not be fixed. Describe why.
• tm/no

  Threat modelling considered unnecessary for issue
• tm/yes

  Threat modelling assumed to be required for issue
• up-for-grabs

  Issues that are easy to fix for new team members or external contributors