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

Disable export POAM link if target level 1 #4440

Merged
merged 1 commit into from
Feb 14, 2025

Conversation

randywoods
Copy link
Collaborator

If the assessment is targeting Level 1, a POAM is not applicable, so the link is disabled. It is only enabled if the target level is > 1 and Level 1 has been achieved.

🗣 Description

💭 Motivation and context

🧪 Testing

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • Changes are limited to a single goal - eschew scope creep!
  • All future TODOs are captured in issues, which are referenced
    in code comments.
  • All relevant type-of-change labels have been added.
  • I have read the CONTRIBUTING document.
  • These code changes follow cisagov code standards.
  • All relevant repo and/or project documentation has been updated
    to reflect the changes in this PR.
  • Tests have been added and/or modified to cover the changes in this PR.
  • All new and existing tests pass.

✅ Pre-merge checklist

  • Revert dependencies to default branches.
  • Finalize version.

✅ Post-merge checklist

  • Create a release.

If the assessment is targeting Level 1, a POAM is not applicable, so the link is disabled.  It is only enabled if the target level is > 1 and Level 1 has been achieved.
@LaddieZeigler LaddieZeigler merged commit b18387e into develop Feb 14, 2025
2 checks passed
@LaddieZeigler LaddieZeigler deleted the feature/cmmc-target-poam branch February 14, 2025 16:21
@faulkdev
Copy link

@randywoods, @LaddieZeigler, Would you please reinstate exporting POA&M as an option for L1? Contrariwise to your assumption, our company provides L1 & L2 assessments and remediation activities, we frequently use L1 POA&Ms with companies because (1) we haven't found a single company that meets L1 out of the gate and (2) most companies seem to prefer using an xlsx POA&M as a tracker (e.g., shared through SharePoint or Google Drive). Thanks for the consideration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants