User Story:
As a NIST staff OSCAL developer, in order to ensure I can quickly review and keep current on newly added issues from colleagues or active community members, I would like to have any new issue automatically added to the Issue Triage Project and its Needs Triage column automatically so I do not have to do so manually and potentially risk making mistakes.
Goals:
We had an action item from previous issue triage meetings to review why GitHub does not automatically add news issues to the Needs Triage column of respective Issue Triage project boards. Automation can only occur for columns, but no out of the box automation in GitHub will add them to the project for you. The wording of the automatic kanban projects implies this gap.
This feature is a known sticking point and heavily requested, but users and staff recommend using GH Actions to implement this.
If done properly, this automation will simply take any new issue and add it to the respective project board (if it exists). From previous discussion, we will not consider additional automation regarding other state transitions in the triage process for automation. That is out of scope. A new GitHub Actions workflow will focus on only adding to the initial addition.
If done properly, existing issues will not be modified, especially given OSCAL's sizable backlog.
Dependencies:
N/A at this time.
Acceptance Criteria
User Story:
As a NIST staff OSCAL developer, in order to ensure I can quickly review and keep current on newly added issues from colleagues or active community members, I would like to have any new issue automatically added to the Issue Triage Project and its Needs Triage column automatically so I do not have to do so manually and potentially risk making mistakes.
Goals:
We had an action item from previous issue triage meetings to review why GitHub does not automatically add news issues to the Needs Triage column of respective Issue Triage project boards. Automation can only occur for columns, but no out of the box automation in GitHub will add them to the project for you. The wording of the automatic kanban projects implies this gap.
This feature is a known sticking point and heavily requested, but users and staff recommend using GH Actions to implement this.
If done properly, this automation will simply take any new issue and add it to the respective project board (if it exists). From previous discussion, we will not consider additional automation regarding other state transitions in the triage process for automation. That is out of scope. A new GitHub Actions workflow will focus on only adding to the initial addition.
If done properly, existing issues will not be modified, especially given OSCAL's sizable backlog.
Dependencies:
N/A at this time.
Acceptance Criteria
main/masterbranch to make immediately active):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.