RealDevSquad / RealDevSquad/website-backend
User should not be able to mark themselves as IDLE if they have task in assigned or In Progress State
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
User should not be able to mark themselves as IDLE if they have task in Assigned or In Progress State. This will ensure that users cannot falsely mark their availability as idle state when they are actively involved in tasks.
Contributor guide
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 files, tests, or entry points are named. Start by locating the API handling user availability and the task-state checks; done means IDLE is rejected when the user has an Assigned or In Progress task, with the behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100