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.

Sign up for GitHub

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

Jump to bottom

🐛 Add application risk filter of "Unassessed" #2032

Merged
merged 4 commits into from
Aug 1, 2024
Merged

🐛 Add application risk filter of "Unassessed" #2032

merged 4 commits into from
Aug 1, 2024

Commits on Jul 31, 2024

  1. 🐛 Add application risk filter of "Unassessed" 

    Resolves: https://issues.redhat.com/browse/MTA-2816

Application risk options are one of:
  - High (red)
  - Medium (yellow)
  - Low (green)
  - Unknown (unknown)
  - Unassessed (unassessed)

Added the __Unassessed__ option to the risk filter
list on the application table to have a complete
set of risk filters.

Note: To help test risk levels, the questionnaire
`hack/import-questionnaire/assign-risk.yaml` has
been added.  The single question has a 1 to 1
mapping between answer and risk level.  As long as
that questionnaire is the only one active on the
system, it works well to quickly assign risks to
applications.

Signed-off-by: Scott J Dickerson <[email protected]>
    @sjd78
    sjd78 committed Jul 31, 2024
    Configuration menu
    Copy the full SHA
    dd5c9cb View commit details
    Browse the repository at this point in the history

  2. Add unassessed as a possible option for type Risk 

    Signed-off-by: Scott J Dickerson <[email protected]>
    @sjd78
    sjd78 committed Jul 31, 2024
    Configuration menu
    Copy the full SHA
    76c63b0 View commit details
    Browse the repository at this point in the history

  3. More type Risk work 

      - Add "unassessed" as an office `Risk` type option

  - Updated `RiskLabel` to handle undefined and arbitrary
    strings as risk inputs.  Consumers of the component
    don't need to worry about the prop quite as much anymore.

  - Where a string risk was getting looked at, force to
    lower case first so all the constants match up.

Signed-off-by: Scott J Dickerson <[email protected]>
    @sjd78
    sjd78 committed Jul 31, 2024
    Configuration menu
    Copy the full SHA
    84fbbf7 View commit details
    Browse the repository at this point in the history

  4. Use normalizeRisk() to enforce risk value stability 

    Signed-off-by: Scott J Dickerson <[email protected]>
    @sjd78
    sjd78 committed Jul 31, 2024
    Configuration menu
    Copy the full SHA
    f37aff8 View commit details
    Browse the repository at this point in the history