Skip to content

Vamsi krishna created an interactive list of open issues#1482

Closed
vamsikrishna1704 wants to merge 16 commits into
developmentfrom
Vamsi_Krishna_Create_an_interactive_list_of_open_issues
Closed

Vamsi krishna created an interactive list of open issues#1482
vamsikrishna1704 wants to merge 16 commits into
developmentfrom
Vamsi_Krishna_Create_an_interactive_list_of_open_issues

Conversation

@vamsikrishna1704
Copy link
Copy Markdown
Contributor

@vamsikrishna1704 vamsikrishna1704 commented Jun 21, 2025

Description

image
image

Related PRS (if any):

This backend PR is related to the #3683 frontend PR.

Main changes explained:

  • Controller handles fetching open issues with or without parameters(projectIds, tag, startDate, endDate)
  • Controller handles updating an issue contents like name or status.
  • Controller handles deleting an issue.
  • Router routes all the requests to respected controller functions.

How to test:

  1. check into current branch
  2. do npm install and npm run build to build and then npm start to run this PR locally
  3. Clear site data/cache on browser
  4. log as admin user
  5. go to Dashboard→ Reports→ Total Construction Summary → Issue Tracking
  6. Verify all the functionalities in both light and dark themes.

Screenshots 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

Copy link
Copy Markdown
Contributor

@Venk-rgb Venk-rgb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested with Frontend PR #3683. Everything working as expected. Good job.

PR.3683.-.FE.mov

Copy link
Copy Markdown
Contributor

@boppanapraveen boppanapraveen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked with Frontend PR #3683, all looks good.
#1482

kedarnath1999
kedarnath1999 approved these changes Jun 26, 2025
Copy link
Copy Markdown

@kedarnath1999 kedarnath1999 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Logged in as admin, but I am getting 404

@Deekshith010905
Copy link
Copy Markdown
Contributor

image
Tested the Issue Tracking section under Dashboard → Reports → Total Construction Summary. The UI loaded correctly, but no issue data was displayed. A 404 error was shown when fetching open issues, indicating a missing or incorrect API endpoint. Filtering is not functional due to this error.

@Juhitha-Reddy
Copy link
Copy Markdown
Contributor

3683 + 1482 PR - 2
3683 + 1482 PR -1
Tested locally with corresponding frontend (#3683) and backend (#1482) branches.

Verified:
Page loads correctly with no console errors.
All functionalities behave as expected in both light and dark themes.
UI remains consistent and responsive across themes.

const controller = require('../../controllers/bmdashboard/bmIssueController')(buildingIssue);

IssueRouter.route('/issues')
IssueRouter.route('/issues/open')
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)) };
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor

@jaydeep138 jaydeep138 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor

@shashank-madan shashank-madan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes work as expected. Tested with the corresponding frontend PR (Review comments)

Copy link
Copy Markdown
Contributor

@harshavarma29 harshavarma29 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor

@saikrishnaraoyadagiri saikrishnaraoyadagiri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, Reviewed this PR, all filters are working as expected.
image
image

Copy link
Copy Markdown

@sankargalla sankargalla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I verified backend PR #1482, and the APIs are fetching data as expected.

PR 1482(1)

@ManviKishore
Copy link
Copy Markdown
Contributor

Changes work as expected, tested through the Frontend branch.

Copy link
Copy Markdown

@harika-majji harika-majji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check the frontend pr for detailed comments.

Copy link
Copy Markdown

@harika-majji harika-majji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added detailed comments in the frontend PR. Functionality works as expected, but there are a few frontend issues that need to be addressed.

Copy link
Copy Markdown

@srushti2403 srushti2403 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked with PR #3683, works well with light and dark mode.
Screenshot 2025-08-26 at 10 45 34 PM
Screenshot 2025-08-26 at 10 45 59 PM

Copy link
Copy Markdown

@MeronTeweldebrhan MeronTeweldebrhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
⚠️ Some header text (e.g., Longest Open Issue inside the Issues Tracking dropdown and Planned vs. Actual Costs Tracking) has low contrast, making it hard to read.
❌ 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.”

Screenshot 2025-09-23 190925 Screenshot 2025-09-23 190959 Screenshot 2025-09-23 191022

Copy link
Copy Markdown

@laynet laynet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything I tested I already wrote in PR #3683 OneCommunityGlobal/HighestGoodNetworkApp#3683 (review)
I've also included a screenshot of the console errors
PR 1482 console error

Copy link
Copy Markdown
Contributor

@akshith312 akshith312 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provided Feedback on Related FE PR 3683

@dunstanad
Copy link
Copy Markdown

The code is not working as expected.
Error:
-Unable to fetch data (AxiosError) for projects in list of issues.

error

@sanjeev29
Copy link
Copy Markdown

Reviewed this locally with the related frontend PR - 3683. Works as expected.
PR-3683

Copy link
Copy Markdown
Contributor

@sumedhkumar96 sumedhkumar96 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@one-community one-community added Do Not Review Do not review or look at code without full context Needs New Developer This is a PR that is partially developed but needs someone new to take it over and finish it. and removed High Priority - Please Review First This is an important PR we'd like to get merged as soon as possible labels Oct 18, 2025
@apoorvajainrp21
Copy link
Copy Markdown
Contributor

The expected code is not working. I have provided a screenshot of the error in PR3683.

@Vinay944924
Copy link
Copy Markdown

Hi Vamsi,
I have tested the PR locally and provided the detailed explanation in the frontend PR.

@Sriamshreddy000
Copy link
Copy Markdown

Tested this PR locally along with the related frontend PR. Everything works as expected
Left detailed feedback and screenshots in the frontend PR for reference.

@one-community
Copy link
Copy Markdown
Member

Redone with this PR: #2032

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Do Not Review Do not review or look at code without full context Needs New Developer This is a PR that is partially developed but needs someone new to take it over and finish it.

Projects

None yet

Development

Successfully merging this pull request may close these issues.