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

The Mitigation field must be populated if the requirement Status is 'Applicable - Does Not Meet' #578

Closed
aaronlippold opened this issue May 5, 2023 · 2 comments · Fixed by #587
Closed

The Mitigation field must be populated if the requirement Status is 'Applicable - Does Not Meet' #578

aaronlippold opened this issue May 5, 2023 · 2 comments · Fixed by #587
Assignees
@ejaronne @vanessuniq

Comments

@aaronlippold
Copy link
Member

No description provided.

@vanessuniq
Copy link
Contributor

What should be the behavior? prevent the control from being saved if mitigation field is empty?

@rlakey
Copy link
Contributor

rlakey commented Jun 5, 2023

I would say the control couldn't be locked. There are many times we will save controls in this scenario where we haven't determined a mitigation yet but will have one by the time we are done with that component.

@vanessuniq vanessuniq linked a pull request Jun 6, 2023 that will close this issue
Constrain requirement for locking Applicable -Does Not Meet and Applicable - Inherently Meets controls #587
Merged
@vanessuniq vanessuniq mentioned this issue Jun 6, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ejaronne ejaronne

@vanessuniq vanessuniq

Labels
None yet
Projects
None yet
Milestone
No milestone
4 participants
@aaronlippold @rlakey @ejaronne @vanessuniq