jeherve
commented
5 days ago It worked. The action added a Blocker label, added the issue to the project (with the matching priority), and since it was a blocker issue, product ambassadors were warned in slack, here: p1731004543435969-slack-CN2FSK7L4
Let's now triage the issue manually. We'll add a label that we know matches a team that wants to be warned in slack: https://github.com/jeherve/jetpack/blob/8079b1de770daeb8178623e1fa4cc262100a55d8/.github/workflows/gardening.yml#L73-L79
We'll then add the "Triaged" label to indicate that the issue was triaged. We should see this reflected in the project board details.
Impacted plugin
Jetpack
Quick summary
Initially, the action will parse the issue contents and should be able to automatically determine a priority, a platform, and a plugin label. It should also be able to add this bug to a project board used to track bugs, while also editing the task on the board to match the priority label used in the issue.
Steps to reproduce
Some steps to reproduce. This will be a very important (blocker) issue.
A clear and concise description of what you expected to happen.
No response
What actually happened
No response
Impact
All
Available workarounds?
No and the platform is unusable
If the above answer is "Yes...", outline the workaround.
No response
Platform (Simple and/or Atomic)
Simple
Logs or notes
No response