kir-dev / kir-dev/ticketing-api
New field for board: accessType
Open
Nobody has claimed this yet.
enhancement
good first issue
priority: low
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Boards should have a accessType enum to make separate them from our internal boards.
If accessType is:
PUBLIC: can be accessed by everybody (main purpose is that it's open for COMMON users), e.g. TanulóSCH hibák, InduláSch hibák boards etc.- Issue #25 will solve the email sending to SUPPORT.
PRIVATE: can be accessed by SUPPORT and ADMIN users.ARCHIVED_PUBLIC: was accessed by everybody, does not show anymore.ARCHIVED_PRIVATE: was accessed by SUPPORT and ADMIN, does not show anymore.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Begin by locating the Board model and the code that determines board visibility, then trace how user roles are checked. Done means Boards expose the four specified accessType values and visibility matches each stated rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- api, authorization, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100