Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edited VulnerabilityCard Severity Level Formatting (CRASM-1056) #748

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

hawkishpolicy
Copy link
Collaborator

@hawkishpolicy hawkishpolicy commented Dec 30, 2024

  • Added formatting of severity levels that match Vulnerability Bar Graph to the VulnerabilityCard component.
  • This resolves formatting issues for both the Latest Vulnerabilities and Most Common Vulnerabilities cards in Risk.

  • All severity levels are title case.
  • Null, N/A, undefined, and empty strings are now displayed as "N/A".
  • Any severity level that is not "Critical", "High", "Medium", "Low", or "N/A" is displayed as "Other".

🗣 Description

💭 Motivation and context

  • Provides formatting of irregular severity levels.
  • Closes CRASM-1056

🧪 Testing

  • tested locally

📷 Screenshots (if appropriate)

Screenshot 2024-12-30 at 3 27 16 PM Screenshot 2024-12-30 at 3 27 01 PM Screenshot 2025-01-03 at 10 00 43 AM Screenshot 2025-01-03 at 10 09 47 AM

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • Changes are limited to a single goal - eschew scope creep!
  • All relevant type-of-change labels have been added.
  • I have read the CONTRIBUTING document.
  • These code changes follow cisagov code standards.
  • All new and existing tests pass.

✅ Pre-merge checklist

  • Revert dependencies to default branches.
  • Finalize version.

✅ Post-merge checklist

  • Create a release.

- Added formatting of severity levels to match Vulnerability Bar Graph.
- All severity levels are title case.
- Null, N/A, undefined, and empty strings are now displayed as "N/A".
- Any severity level that is not "Critical", "High", "Medium", "Low", or "N/A" is displayed as "Other".
@hawkishpolicy hawkishpolicy changed the title Edited VulnerabilityCard Severity Level Formatting Edited VulnerabilityCard Severity Level Formatting (CRASM-1056) Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant