Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update task status to assigned on successful assignment #651

Open
1 of 3 tasks
RitikJaiswal75 opened this issue Jun 13, 2023 · 1 comment · May be fixed by #668
Open
1 of 3 tasks

Update task status to assigned on successful assignment #651

RitikJaiswal75 opened this issue Jun 13, 2023 · 1 comment · May be fixed by #668
Assignees

Comments

@RitikJaiswal75
Copy link
Contributor

RitikJaiswal75 commented Jun 13, 2023

Change task status to assigned after assigning an available task

Description

When the superuser assigns an available task to some existing user the API call adds an assignee parameter in the task but does not change the status of the task, i.e. the status still remains available.

Debugging steps followed

  • Api being used patch /task/:id
  • First, we thought that it was a caching issue
  • On further debugging, we concluded that the issue was because the backend was just changing the task assignee, not the task status

References for developer

Screenshots for reference

image

Video for the issue

Studio_Project_V1.mp4

Expectations from the solution

  • on assigning an available task to a user change its status to assigned
  • add tests for checking if the status is updated in the DB.
  • Please update the API contracts.
    - [ ] Similarly, when the user is removed from the assignee the task status should go back to available (mentioned the reason in the comments Update task status to assigned on successful assignment #651 (comment))
@kotesh-arya
Copy link
Contributor

The Task Assignee cannot be removed but only be re-assigned.
So the Point mentioned here cannot be implemented Now.
image
If we try to remove the assignee in the same way we add, It will throw the error shown below:
Screenshot (753)

@kotesh-arya kotesh-arya transferred this issue from Real-Dev-Squad/website-backend Jun 22, 2023
@kotesh-arya kotesh-arya linked a pull request Jul 1, 2023 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants