RealDevSquad / RealDevSquad/website-backend
Task Unassignment Feature and Status Site Improvements
@heyrandhirs is already working on this.
Since Dec 12, 2023.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Issue Description
Currently, there is no direct method to unassign a task. To achieve this, a superuser must assign the task to themselves, which then reflects as overdue for them.
Additionally, a regular user assigned with a task has the ability to change the task status to available. Furthermore, on the status site, the dropdown for changing status by a superuser mentions the status as 'UN ASSIGNED,' and it should be a single word.
The ticket includes the following subtasks:
-
When a superuser marks a task as available, it will automatically unassign the task (Complete)
- Issue ticket #1750
- PR #1756.
-
A regular user assigned with a task should not have the ability to change the task status to available (WIP).
- Issue ticket #1776
-
On the status site, the dropdown for changing status by a superuser mentions the status as 'UN ASSIGNED' and it should be a single word.
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.
Assessment
This issue has not been assessed yet.