Vamsi krishna created an interactive list of open issues#3683
Vamsi krishna created an interactive list of open issues#3683vamsikrishna1704 wants to merge 23 commits into
Conversation
…ighestGoodNetworkApp into Vamsi_Krishna_Create_an_interactive_list_of_open_issues
…ighestGoodNetworkApp into Vamsi_Krishna_Create_an_interactive_list_of_open_issues
…ighestGoodNetworkApp into Vamsi_Krishna_Create_an_interactive_list_of_open_issues
✅ Deploy Preview for highestgoodnetwork-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
boppanapraveen
left a comment
There was a problem hiding this comment.
Checked with Frontend PR #1482 all looks good.

PrasanthBhimana
left a comment
There was a problem hiding this comment.
I have tested the new Issue Tracking table implementation and it functions as expected. The table now supports advanced filtering by date range and multiple project selection, and clicking on tags correctly filters the issues. The “Options” dropdown in each row provides smooth interaction for renaming, deleting, or closing issues. The inline editing feature for issue names works well, and changes are reflected properly after multiple refreshes. The component displays consistently in both light and dark modes with no UI glitches. Overall, the update enhances usability and meets the functional requirements effectively. Approving the PR.
Saicharan1505
left a comment
There was a problem hiding this comment.
Tested PR-3683:
Verified the interactive issue list with all required functionalities:
-
Tag filter toggle correctly filters and clears issues by tag
-
Date range and multi-project dropdowns fetch and display matching issues
-
"Options" dropdown works for rename, delete, and close actions
-
UI consistent across both dark and light modes
Everything looks good and matches the expected behavior as per the spec.
marcusyi1
left a comment
There was a problem hiding this comment.
Reviewed all functionality under Issue Tracking and on light mode and dark mode everything is working as expected.
PR3683.mov
|
Tested locally with corresponding frontend (#3683) and backend (OneCommunityGlobal/HGNRest#1482) branches. Verified: |
jaydeep138
left a comment
There was a problem hiding this comment.
Tested this locally — the Issue Tracking section is working as expected. The date filter, issue renaming, tag selection, and project filtering functionalities are all functioning correctly. Issues update appropriately based on the selected filters, and all related UI elements (tags, person, action menu) are displaying as intended. Everything looks good.



shashank-madan
left a comment
There was a problem hiding this comment.
The main functionality changes are working as expected. The selected date range is correctly passed to the backend to filter and fetch issues within that range. Multi-project selection accurately filters issues by the selected projects. Clicking a tag button filters the issues by that tag, and clicking it again clears the filter, functioning as intended. Issue options allow for updating issue names and statuses, as well as deleting issues, all without errors.I verified all described functionalities in both light and dark mode. The implementation aligns with the behavior shown in the attached video. Everything looks good. Approving this PR
Total.Construction.Summary.-.Google.Chrome.2025-07-11.11-33-33.mp4
Total.Construction.Summary.-.Google.Chrome.2025-07-11.11-34-34.mp4
There was a problem hiding this comment.
I have tested the feature locally using admin credentials. It is working fine for most of the scenarios, but when I am selecting the 'virtual' tag, the complete row is getting removed. Please check the video below for reference.
Recording.2025-07-13.003436.mp4
saikrishnaraoyadagiri
left a comment
There was a problem hiding this comment.
Hi, Reviewed this PR, all the filters are working as expected. but when we move to page 2 and apply a filter as shown in video reference and after applying filter we got results only sufficient for page 1, the results are in page 1 but as we applied filter in page 2 we are still staying in page 2 but as per the filter page is invalid now. To improve the user experience and ensure relevant data is displayed immediately, we should automatically reset the pagination to page 1, if there are no enough results to display in the filter applied page.
saikrishna.PR.3683+1482.mp4
sankargalla
left a comment
There was a problem hiding this comment.
I verified Frontend PR #3683 in both light and dark modes, and all the functional and UI requirements are working as expected.
karnati007
left a comment
There was a problem hiding this comment.
Hi @vamsikrishna1704, As the changes in the code resolved merge conflicts by keeping the functionalities working as expected. I am satisfied to approve the PR. Thank you.

b1343d5 to
7bef733
Compare
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.
I followed the testing instructions and logged in as admin. When I was asked to sign in again after navigating to “total construction summary” it didn’t reroute me after i logged in, but I was able to get to the page by using the dropdown again.
Upon opening the “Issues tracking” dropdown I immediately had an error. The error persisted after reset and after choosing a date range. Error persisted after a hard refresh. I cleared data, logged out and back in as admin, error persisted.


The reset button did work after I selected dates, but the error never went away and I was never able to test anything/no data was ever displayed. Dark mode behaved the same.
Hi @laynet, based on the error that you posted, it seems that you have not checked in the HGNRest to my branch. Try checking into |
Hi @MeronTeweldebrhan, you are checking the 'Longest open issues' which is not my task. You have to check the 'List of Issues table' which is the one I worked on. Also you have to check into my branch in HGNRest to see the issues data. Try the suggested steps and verify the features and functionalities of the task. |
sumedhkumar96
left a comment
There was a problem hiding this comment.
Tested the changes made by the dev by running the frontend and the backend code locally. All the features listed are implemented and it works as expected in both light and dark modes. But there is a section which is on the right side of "List of Issues" called the "Longest Open Issues", that part needs work but I think those changes were made by a different dev which needs a fix.
|
Hi Vamshi, I tested this PR along with the related backend PR while logged in as an admin user. In the Issues Tracking section, the table functions correctly in both light and dark modes. The "Longest Open Issues" UI seems like it might need a bit of rework, though I assume that’s being handled in a separate PR by a separate dev. |
|
Redone with this PR: #4800 |























Description
Related PRS (if any):
To test this frontend PR you need to checkout the #1482 backend PR.
…
Main changes explained:
…
How to test:
npm installandnpm run start:localto 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)
Total.Construction.Summary.-.Profile.1.-.Microsoft.Edge.2025-06-21.15-35-28.mp4