RealDevSquad / RealDevSquad/website-backend
Problem encountered while updating stand up
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Issue Description
Faced issue while updating the standup today
Expected Behavior
[Describe what should happen when this issue is resolved.]
Current Behavior
[Explain what currently happens when this issue is encountered.]
Screenshots
Reproducibility
- This issue is reproducible
- This issue is not reproducible (was not able to reproduce in the staging site tried only once)
Steps to Reproduce
- I updated my standup the form did not disappear
- I refreshed the page
- Saw get API for
progresses?userId=aaL1MXrpmnUNfLkhgXRjfail - Again I filled out the form and submitted an update and encountered an error as shown in the 1st image
- On refresh get API is working fine as shown in the second screen
Severity/Priority
- Critical
- High
- Medium
- Low
Additional Information
[Include any additional context, logs, or details that might be helpful in addressing the issue.]
Checklist
- I have read and followed the project's code of conduct.
- I have searched for similar issues before creating this one.
- I have provided all the necessary information to understand and reproduce the issue.
- I am willing to contribute to the resolution of this issue.
Thank you for contributing to our project! We appreciate your help in improving it.
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
Start by attempting the reported standup update flow in the staging site, following the listed refresh and submission steps. Inspect the progresses?userId=... API behavior and the standup update entry point; the issue provides no file or test names. Done should mean the update completes reliably, the form behaves as intended, and the progresses request does not fail in the reported sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100