Labels
Labels
32 labels
- Pull requests that update .net code
- Tasks related to creating a Cypress test
- Pull requests that update a dependency file
- Pull requests that update Docker code
- Issues suitable for beginners
- A big change that consists of many issues
- An issue that must be solved by summer 2023
- Pull requests that update GitHub Actions code
- Issues from icebox
- Issue that needs legal assessment
- Used when an issue needs to be analysed before it becomes a user story.
- Used when something isn't working
- Create a none user-story issue (chore, tech issue, backend issue)
- Used when issue is related to improvements or additions to documentation
- Used when issue is a new feature or request
- Questions raised should be labeled with this.
- Issues for technical debt.
- Used for issues that describes functionality for our users.
- Issue is part of report in ks2-regime
- Epic that belongs to Digdir roadmap
- An issue that needs to be refined
- 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.
- Status: Used when something will not be fixed. Describe why.
- Issue affecting the Tilgangsinfo team
- Issue affecting the Tilgangsstyring team