Skip to content

No labels!

There aren’t any labels for this repository quite yet.

30 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
area/infrastructure
area/infrastructure
Issue originates as changes to infrastructure
2
dependencies
dependencies
Pull requests that update a dependency file
docker
docker
Pull requests that update Docker code
Epic
Epic
6
external-contribution-❤️
external-contribution-❤️
Pull request from a developer outside the Altinn teams.
feature-complete
feature-complete
github_actions
github_actions
Pull requests that update GitHub Actions code
good first issue
good first issue
Issues that are easy to fix for new team members or external contributors (org-wide)
kind/analysis
kind/analysis
4
kind/bug
kind/bug
Something isn't working
kind/chore
kind/chore
Non functional, often repeating tasks.
6
kind/documentation
kind/documentation
Improvements or additions to documentation
4
kind/feature-request
kind/feature-request
New feature or request
8
kind/product-feature
kind/product-feature
kind/question
kind/question
Questions raised should be labeled with this.
kind/user-story
kind/user-story
Used for issues that describes functionality for our users.
3
.NET
.NET
Pull requests that update .net code
org/brg
org/brg
Issues relevant for Brønnøysundregistrene.
org/digdir
org/digdir
Issues relevant for Digitaliseringsdirektoratet
org/skd
org/skd
Issues relevant for Skatteetaten
org/ssb
org/ssb
Issues relevant for Statistisk sentralbyrå.
review/domain-model-changes
review/domain-model-changes
1
status/blocked
status/blocked
Further work depending on the completion of some other task/PoC/issue
8
status/draft
status/draft
Status: When you create an issue before you have enough info to properly describe the issue.
13
status/duplicate
status/duplicate
Status: An issue that is closed as a duplicate of another issue.
status/pending-feedback
status/pending-feedback
Awaiting clarification/input from stakeholders etc.
5
status/wontfix
status/wontfix
Status: Used when something will not be fixed. Describe why.
tm/no
tm/no
Threat modelling considered unnecessary for issue
tm/yes
tm/yes
Threat modelling assumed to be required for issue
up-for-grabs
up-for-grabs
Issues that are easy to fix for new team members or external contributors