Vamsi krishna created an interactive list of open issues#1482
Vamsi krishna created an interactive list of open issues#1482vamsikrishna1704 wants to merge 16 commits into
Conversation
Venk-rgb
left a comment
There was a problem hiding this comment.
Tested with Frontend PR #3683. Everything working as expected. Good job.
PR.3683.-.FE.mov
|
Verified: |
| const controller = require('../../controllers/bmdashboard/bmIssueController')(buildingIssue); | ||
|
|
||
| IssueRouter.route('/issues') | ||
| IssueRouter.route('/issues/open') |
There was a problem hiding this comment.
The POST route is currently defined as /issue/add, while other routes use /issues/.... For consistency, consider renaming the POST endpoint to /issues (without /add). Alternatively, make all endpoints follow either the singular (/issue/...) or plural (/issues/...) naming pattern for consistency across your API routes. This will improve maintainability and clarity for consumers of the API.
| } else if (startDate) { | ||
| query.createdDate = { $gte: new Date(startDate) }; | ||
| } else if (endDate) { | ||
| query.createdDate = { $lte: new Date(new Date(endDate).setHours(23, 59, 59, 999)) }; |
There was a problem hiding this comment.
Here, new Date(endDate) is constructed twice. You can refactor by creating the date object once, setting its hours, and then using it. For example:
const end = new Date(endDate);
end.setHours(23, 59, 59, 999);
Then use end in your query.
This improves readability and performance by avoiding unnecessary object creation.
jaydeep138
left a comment
There was a problem hiding this comment.
Tested this in coordination with the frontend, and everything is working as expected from the UI side — filters, data updates, and overall functionality are all behaving correctly. Just implement the two minor suggested changes on the backend, and everything should be good to go.
shashank-madan
left a comment
There was a problem hiding this comment.
Changes work as expected. Tested with the corresponding frontend PR (Review comments)
harshavarma29
left a comment
There was a problem hiding this comment.
I have tested the backend separately in Postman using 'In-person' and 'Virtual' tags as params. It correctly returns only the associated issues for each tag.
However, in the frontend PR, when selecting the 'Virtual' tag, it displays an empty result instead of showing the associated issue for 'Virtual' tag.
Recording.2025-07-13.013516.mp4
sankargalla
left a comment
There was a problem hiding this comment.
I verified backend PR #1482, and the APIs are fetching data as expected.
|
Changes work as expected, tested through the Frontend branch. |
harika-majji
left a comment
There was a problem hiding this comment.
Added detailed comments in the frontend PR. Functionality works as expected, but there are a few frontend issues that need to be addressed.
…ist_of_open_issues
…ist_of_open_issues
…ist_of_open_issues
MeronTeweldebrhan
left a comment
There was a problem hiding this comment.
PR Review Feedback
Testing Outcome
✅ Logged in as an admin user and navigated to Dashboard → Reports → Total Construction Summary → Issues Tracking.
✅ Verified functionalities in both light and dark modes; overall layout and pages appear fine.
❌ Data under A List of Issues fails to load, responding with error:
“Error fetching open issues with filters: AxiosError: Request failed with status code 404.”
laynet
left a comment
There was a problem hiding this comment.
Everything I tested I already wrote in PR #3683 OneCommunityGlobal/HighestGoodNetworkApp#3683 (review)
I've also included a screenshot of the console errors

akshith312
left a comment
There was a problem hiding this comment.
Provided Feedback on Related FE PR 3683
sumedhkumar96
left a comment
There was a problem hiding this comment.
Followed the instructions and tested the functionalities by running both frontend and backend locally. The changes work as expected. Screenshots and comments are provided in the frontend PR-3683
|
The expected code is not working. I have provided a screenshot of the error in PR3683. |
|
Hi Vamsi, |
|
Tested this PR locally along with the related frontend PR. Everything works as expected |
|
Redone with this PR: #2032 |











Description
Related PRS (if any):
This backend PR is related to the #3683 frontend PR.
…
Main changes explained:
…
How to test:
npm installandnpm run buildto build and thennpm startto run this PR locallyScreenshots or videos of changes:
Frontend Demo: (Light theme)
Dashboard.-.Vamsi.Krishna.Owner.-.Profile.1.-.Microsoft.Edge.2025-06-21.15-33-17.mp4
Frontend Demo:(Dark theme)
https://github.com/user-attachments/assets/6796d55c-c58f-4a1a-b427-327bc6f41325