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

Automatically Remove Issues from Triage Board When Closed #1302

Closed
7 tasks done
aj-stein-nist opened this issue Jun 8, 2022 · 1 comment · Fixed by #1335
Closed
7 tasks done

Automatically Remove Issues from Triage Board When Closed #1302

aj-stein-nist opened this issue Jun 8, 2022 · 1 comment · Fixed by #1335
Assignees
Labels
Developer Experience Issues around enhancing and optimizing work for development of NIST OSCAL artifacts enhancement LoE: Small Scope: CI/CD Enhancements to the project's Continuous Integration and Continuous Delivery pipeline.
Milestone

Comments

@aj-stein-nist
Copy link
Contributor

aj-stein-nist commented Jun 8, 2022

User Story:

As a NIST OSCAL developer, in order to improve efficiency and reduce impact on developer bandwidth to perform ongoing triage of issues, I would like to have improved automation to remove the card from the Issue Triage board once its issue has been closed as complete.

Goals:

This had been discussed internally with Dave and the NIST OSCAL dev team. This work is a continuation of #1209. We now automatically bring in issues to the triage board, it is now time to balance this out and make sure they get removed.

Dependencies:

N/A

Acceptance Criteria

{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}

@aj-stein-nist aj-stein-nist added enhancement LoE: Small Scope: CI/CD Enhancements to the project's Continuous Integration and Continuous Delivery pipeline. Developer Experience Issues around enhancing and optimizing work for development of NIST OSCAL artifacts labels Jun 8, 2022
@aj-stein-nist
Copy link
Contributor Author

@david-waltermire-nist I did look through the backlog and did not find this issue created previously, but we talked about it enough. PRs incoming after some more testing when I unify the two two jobs into one workflow file.

@aj-stein-nist aj-stein-nist self-assigned this Jun 8, 2022
@aj-stein-nist aj-stein-nist added this to the OSCAL 1.0.5 milestone Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/OSCAL-forked that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/oscal-content-forked that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/oscal-content-forked that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/OSCAL-forked that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/OSCAL-forked that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/OSCAL-forked that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/oscal-content-forked that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/metaschema that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/oscal-tools that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/oscal-tools that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/oscal-tools that referenced this issue Jun 8, 2022
aj-stein-nist added a commit to aj-stein-nist/oscal-tools that referenced this issue Jun 8, 2022
david-waltermire pushed a commit to usnistgov/oscal-content that referenced this issue Jun 13, 2022
david-waltermire pushed a commit to usnistgov/oscal-tools that referenced this issue Jul 1, 2022
aj-stein-nist added a commit that referenced this issue Jul 5, 2022
OK, we aren't done yet. First, we started with #1303 to resolve #1302. AJ thought he "fixed it" with c09ec10 then Dave rightfully noticed he had only fixed the board removal job, not creation when adding it in c09ec10. Subsequently, AJ realized that the necessary column should be "Needs Triage" and not "To do" from his test repo. So, we will make sure we fix up the last copy-paste error once and for all.
david-waltermire pushed a commit that referenced this issue Jul 5, 2022
OK, we aren't done yet. First, we started with #1303 to resolve #1302. AJ thought he "fixed it" with c09ec10 then Dave rightfully noticed he had only fixed the board removal job, not creation when adding it in c09ec10. Subsequently, AJ realized that the necessary column should be "Needs Triage" and not "To do" from his test repo. So, we will make sure we fix up the last copy-paste error once and for all.
nikitawootten-nist pushed a commit to nikitawootten-nist/metaschema-xslt that referenced this issue Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment