Skip to content

Conversation

@uhakruthi1
Copy link

Description

This PR fixes and enhances the Longest Open Issues chart by properly supporting multiple projects per issue.

Key changes:
• Updated backend response to include projectId and projectName for each issue.

This makes multi-project issues visually clear and prevents ambiguity in the chart.

how to test:

add console.log the results to check if the res is similar are not

npm install, npm run build, npm start

related frontend pr: OneCommunityGlobal/HighestGoodNetworkApp#4441

screenshot :
Screenshot 2026-01-06 at 12 36 26 AM

@uhakruthi1 uhakruthi1 changed the title feat(api): create backend API for fetching longest open issues uha-create backend API for fetching longest open issues Jan 6, 2026
Copy link

@Anusha-Gali Anusha-Gali left a comment

Choose a reason for hiding this comment

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

Hi Uha,

I have reviewed your PR locally and have mentioned my comments in frontend pr. Also as mentioned in your description - i am unable to see any console.log statements.
Screenshot 2026-01-06 at 5 20 30 PM

@uhakruthi1
Copy link
Author

Hi Uha,

I have reviewed your PR locally and have mentioned my comments in frontend pr. Also as mentioned in your description - i am unable to see any console.log statements. Screenshot 2026-01-06 at 5 20 30 PM

Add console statement in the code to see the ouput similar to mine in the code.

@Anusha-Gali
Copy link

Hi Uha,
I have reviewed your PR locally and have mentioned my comments in frontend pr. Also as mentioned in your description - i am unable to see any console.log statements. Screenshot 2026-01-06 at 5 20 30 PM

Add console statement in the code to see the ouput similar to mine in the code.

Sure Uha, i assumed the statements were already present. Nevertheless could you please have a look into the frontend pr where i had mentioned a UI issue. Once that is fixed i will review both the PR's. Thank you

@uhakruthi1
Copy link
Author

Hi Uha,
I have reviewed your PR locally and have mentioned my comments in frontend pr. Also as mentioned in your description - i am unable to see any console.log statements. Screenshot 2026-01-06 at 5 20 30 PM

Add console statement in the code to see the ouput similar to mine in the code.

Sure Uha, i assumed the statements were already present. Nevertheless could you please have a look into the frontend pr where i had mentioned a UI issue. Once that is fixed i will review both the PR's. Thank you

I dont think so, the fix is in frontend, may be the data from the backend might be wrong, just texted you in the slack.

Copy link

@Anusha-Gali Anusha-Gali left a comment

Choose a reason for hiding this comment

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

Hi Uha,

Thanks for updating the code. The Db.js changes please do not push it into development might cause errors.
Screenshot 2026-01-07 at 10 14 53 PM
Screenshot 2026-01-07 at 10 15 00 PM
Screenshot 2026-01-07 at 10 15 08 PM

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants