RealDevSquad / RealDevSquad/website-backend
[ RFC ] New Task Workflow
@ivinayakg is already working on this.
Since Aug 30, 2022.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Project Description
This project will allow the tasks of Real Dev Squad to be handled in an efficient way. Each task can be in one state such as completed, blocked, etc. This project will allow us to have a new set of states that a task can be in and a few things will be automated such as if a member could not complete a task within the given period of time, the task will be unassigned from the member and it will be available for other members to be picked up.
The current status that a task can be in:- active | assigned | unAssigned | blocked | completed | High Priority | pending
changes:- active → IN_PROGRESS, unAssigned → AVAILABLE
This feature allows the task status to be in- AVAILABLE | ASSIGNED | IN_PROGRESS | BLOCKED | SMOKE_TESTING | COMPLETED | NEEDS_REVIEW | IN_REVIEW | APPROVED | MERGED | SANITY_CHECK | REGRESSION_CHECK | RELEASED | VERIFIED
Reference 👇🏻
https://app.creately.com/diagram/heYDw2DIsqh/view
Tasks
website-backend
-
Make the task’s status to accept any of these values
AVAILABLE | ASSIGNED | IN_PROGRESS | BLOCKED | SMOKE_TESING | COMPLETED | NEEDS_REVIEW | IN_REVIEW | APPROVED | MERGED | SANITY_CHECK | REGRESSION_CHECK | RELEASED | VERIFIED
(Right now it can accept any value) -
create an endpoint that fires a function that loops through all tasks whose status is
ASSIGNED | IN_PROGRESSand ifendsOn<currentTimeSET task’s status back toAVAILABLE, assignee field to be cleared and log the member and task details (For future use) -
migration script to make active →
IN_PROGRESS, unAssigned →AVAILABLE(Does not need any changes on status except availability panel)
website-status
-
On the availability panel render only tasks that are available not unAssigned(handle it before migration such that both AVAILABLE and unAssigned works)
-
When the task is assigned to a member from the availability panel make the status of the task as ASSIGNED and startedOn should be computed and endsOn should be 14 days by default
website-dashboard
-
Remove startedOn input field from the form, and endsOn input field will be hidden by default
-
default status field should be AVAILABLE
-
when the status field is selected as assigned show assignee field and make it compulsory and show endsOn date and default endsOn date is 14 days
-
When a new task is created startedOn will be computed if the task is assigned else ignored
website-members
- Makes use of the task’s status(Active) on members profile Active tasks section need to make it work either (Active || IN_PROGRESS)
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.