RealDevSquad / RealDevSquad/website-backend
Some inactive feature need investigation and discussion with product
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Issue Description
In website status, we have a feature to close the task when it's GitHub status is closed but on backend we are not saving GitHub issue
Expected Behavior
Current Behavior
Screenshots
Reproducibility
- This issue is reproducible
- This issue is not reproducible
Steps to Reproduce
Severity/Priority
- Critical
- High
- Medium
- Low
Additional Information
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.
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 tracing the backend flow for website status updates and how GitHub issue data is handled. Confirm with the product team what behavior is intended; the issue is done when the decision is documented and the backend behavior matches it, including whether GitHub issue data must be saved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript, node.js
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100