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

Restore implementation-status to finding.objective-status in SAR #868

Closed
2 of 3 tasks
degenaro opened this issue Mar 17, 2021 · 1 comment · Fixed by #882
Closed
2 of 3 tasks

Restore implementation-status to finding.objective-status in SAR #868

degenaro opened this issue Mar 17, 2021 · 1 comment · Fixed by #882

Comments

@degenaro
Copy link

User Story:

As an OSCAL tool developer, I would like to have implementation-status restored to finding.objective-status in SAR.

Goals:

The SSP has implemented-requirements with an implementation-status. In previous version(s) of OSCAL, the SAR finding.objective-status also had implementation-status. Having implementation-status in the finding is desirable to incorporate in the SAR, similar to the SSP.

The value must be one of the following:

    implemented
    partial
    planned
    alternative
    not-applicable

Dependencies:

N/A

Acceptance Criteria

  • All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
  • A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
  • The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.
@david-waltermire david-waltermire self-assigned this Mar 19, 2021
@david-waltermire david-waltermire added this to To do in Sprint 40 via automation Mar 19, 2021
@david-waltermire david-waltermire added this to the OSCAL 1.0.0 RC 2 milestone Mar 19, 2021
@david-waltermire
Copy link
Contributor

This work will be completed in 1.0.0 RC2

@david-waltermire david-waltermire linked a pull request Apr 7, 2021 that will close this issue
13 tasks
david-waltermire added a commit that referenced this issue Apr 7, 2021
…lementation status. Resolves #868. Fixed some spelling errors.
david-waltermire added a commit that referenced this issue Apr 7, 2021
…lementation status. Resolves #868. Fixed some spelling errors.
david-waltermire added a commit that referenced this issue Apr 8, 2021
…lementation status. Resolves #868. Fixed some spelling errors.
david-waltermire added a commit that referenced this issue Apr 8, 2021
…lementation status. Resolves #868. Fixed some spelling errors.
Sprint 40 automation moved this from To do to Done Apr 8, 2021
david-waltermire added a commit that referenced this issue Apr 8, 2021
…lementation status. Resolves #868. Fixed some spelling errors.
david-waltermire pushed a commit that referenced this issue May 21, 2021
* Adjusted metaschemas: new 'version'; json-base-uri
* Added 'complete' metaschema
* Changes to OSCAL metaschemas in view of enhancements addressing #805, #911, #67, #868.
david-waltermire pushed a commit to david-waltermire/OSCAL that referenced this issue May 27, 2021
* Adjusted metaschemas: new 'version'; json-base-uri
* Added 'complete' metaschema
* Changes to OSCAL metaschemas in view of enhancements addressing usnistgov#805, usnistgov#911, usnistgov#67, usnistgov#868.
david-waltermire pushed a commit that referenced this issue May 27, 2021
* Adjusted metaschemas: new 'version'; json-base-uri
* Added 'complete' metaschema
* Changes to OSCAL metaschemas in view of enhancements addressing #805, #911, #67, #868.
david-waltermire pushed a commit that referenced this issue Jun 7, 2021
* Adjusted metaschemas: new 'version'; json-base-uri
* Added 'complete' metaschema
* Changes to OSCAL metaschemas in view of enhancements addressing #805, #911, #67, #868.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Sprint 40
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants