kir-dev / kir-dev/ticketing-api
User authorization levels
Open
enhancement
good first issue
priority: medium
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This can be achieved through implementing user roles, e.g. ADMIN, SUPPORT, COMMON.
See more at: https://docs.nestjs.com/security/authorization
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the NestJS authorization documentation linked in the issue and inspect the existing project structure for user and access-control entry points. The requested roles are ADMIN, SUPPORT, and COMMON; done means their authorization behavior is implemented, but the issue does not name files or tests to verify.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api, authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100