Open butler54 opened 4 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.
Discussed at the last issue review meeting. This solution could be broken down into three parts:
actions/labeler
.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.
@butler54 I added some YAML-based issue templates to another project. Wondering if you think they would work to satisfy this issue as well? If so, I can do something similar here.
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