uha longest open issues chart logic #2002
Open
+135
−127
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
uhakruthi1
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes and enhances the Longest Open Issues chart by properly supporting multiple projects per issue.
This is a PR replacing PR1988, which i updated db url.
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.
Related PR :
Related front end Pr : PR#4441
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:PR#4441
screenshot :
after db update front changes works as expected.