Bug Fix - Priority score of an issue is not displayed

[winterji]

This PR fixes the issue I raised - #206

No priority scores were displayed for project's issues.

What this does

Adds another location within the json response from snyk where to get the value of a priority score of an issue.

Notes for the reviewer

See commit changes - added a new attribute of an issue to unifiedIssuesTypes.ts and referenced the new location in SnykIssuesComponent.tsx.

[stefanbuck-snyk]

Thank you for your contribution! 🙌

I reviewed the changes, and everything looks good overall. However, I noticed one issue: the column is currently named priority score, but in reality, it could represent either priority or risk score. Unfortunately, there’s no way to distinguish this from the API response at the moment.

To make it clearer, how about renaming the column to priority/risk score? Let me know what you think!

[winterji]

Thank you for your review!

I understand. What if we named it just "Score" then? Snyk also displays it just as score - see attached image.

However, "Priority/Risk Score" would also work, but just "Score" could save some space in the table.

[stefanbuck-snyk]

Agreed, using just 'Score' is a better choice as it aligns with how it's labeled in our app and also less clutter in the table.

[winterji]

I renamed the column in the last commit. If I forgot about something, let me know.

[stefanbuck-snyk]

I’d like to pull and test these changes in our Backstage installation before merging, just to ensure everything works as expected.

[stefanbuck-snyk]

The release pipeline is currently broken and needs to be fixed first. I’ll work on getting this resolved asap

[winterji]

Ok. Thanks for approving and merging it. Let me know when you'll release new version with these updates, so I can update it in our backstage.

[stefanbuck-snyk]

🎉 This PR is included in version 2.5.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀