oscal-compass / compliance-trestle

An opinionated tooling platform for managing compliance as code, using continuous integration and NIST's OSCAL standard.
https://oscal-compass.github.io/compliance-trestle
Apache License 2.0
165 stars 61 forks source link

Update pull request templates to provide sensible default labels and project assignment #1642

Open butler54 opened 3 months ago

butler54 commented 3 months ago

Issue description / feature objectives

The pull request templates can be easily have labels added to get bug / enhancement labels and assign to the project

Caveats / Assumptions

Projects can automatically pick up issues based on opening of an issue. This may be easier than labelling an issue with the project (via a template) as people can avoid a template.

Completion Criteria

jpower432 commented 3 months ago

@butler54 This make sense. Part of this can be configured on the project side. There are pre-built workflows for auto-adding issues. We would just need to decide if there should be a label to filter on and what the default status of the issue should be. Right when added to the project, the default status is ToDo. If you agree with this approach, do you think it should be something like Needs Triage? Right now we use the lack of labels to indicate that the issue has not been triaged which could be improved/more explicit.

jpower432 commented 3 months ago

Discussed at the last issue review meeting. This solution could be broken down into three parts:

  1. Auto add issues
  2. Add or updates the issue templates with sane default labels
  3. For any issue that does not have a label or when issues are submitted without the templates, use something like actions/labeler.
jpower432 commented 3 months ago

The first step has been done. A workflow in the project has been created to automatically add issues to the project and put them in the New status. Once triaged they can moved the the Ready status.