Create a Wazuh Dashboard issue
Pick the right issue template, check for duplicates first, then fill the template verbatim and hand off a ready-to-file body.
Workflow
Copy this checklist and track progress:
- [ ] 1. Classify intent → choose issue template (ask only if ambiguous)
- [ ] 2. Issue-first check: search existing issues for duplicates
- [ ] 3. Fill the chosen .github/ISSUE_TEMPLATE/*.md verbatim
- [ ] 4. Apply the real Wazuh label for the intent (`type/bug` / `type/enhancement` / `level/task`) + `untriaged`; ignore stale frontmatter labels
- [ ] 5. Emit the ready-to-file body + report (default stop; gh issue create only if asked)
1. Classify intent → choose template
Map the user's intent to a template. Ask the user only when genuinely ambiguous between two rows.
| Intent | Template | Labels (from template frontmatter) |
|---|---|---|
| Something is broken | bug_report.md |
bug, untriaged |
| New capability / improvement | feature_request.md |
enhancement, untriaged |
| Document a shipped feature | documentation.md |
(no frontmatter — no default labels) |
| Track OpenSearch version compatibility work | compatibility_request.md |
request/operational, level/task, type/maintenance |
| Engineering task or improvement (not a bug/feature/doc gap) | task_template.md |
level/task |
2. Issue-first duplicate check
Before drafting, search for an existing issue covering the same problem:
gh issue list --search "<keywords>"
gh search issues "<keywords>" --repo wazuh/wazuh-dashboard-notifications
On a likely match, surface it to the user and ask whether to proceed with a new issue or comment on the existing one instead.
3. Fill the template
Reference the chosen file under
.github/ISSUE_TEMPLATE — read it first and
fill it verbatim; do not inline template bodies in this skill.
repo-specific (wazuh-dashboard-notifications): this repo's real label taxonomy (verified via
gh label list --repo wazuh/wazuh-dashboard-notifications) istype/bug,type/enhancement,type/maintenance,level/task,request/operational,untriaged, etc. — there is no barebugorenhancementlabel.bug_report.mdandfeature_request.mdstill carry the stale upstreambug/enhancementnames in their frontmatter — see step 4 for the real labels to apply instead.compatibility_request.mdandtask_template.md's labels (request/operational,level/task,type/maintenance) all exist as-is.bug_report.mdandfeature_request.mduse the frontmattertitleprefix ([BUG]/[FEATURE]) — keep it..github/workflows/add-untriaged.ymlauto-applies theuntriagedlabel to every opened/reopened/transferred issue, regardless of the template's own labels — sountriagedwill end up on the issue either way..github/ISSUE_TEMPLATE/config.ymldoes not setblank_issues_enabled, and only definescontact_links(OpenSearch Community Support, AWS/Amazon Security) — it does not disable blank issues.
4. Labels
Several issue templates in this repo were inherited from the upstream
OpenSearch Dashboards fork and still declare stale labels in their
frontmatter (bare bug, enhancement) that don't exist as real labels here
— GitHub silently drops any label that doesn't exist instead of erroring, so
filing the template as-is can result in no type label at all. Standardize on
the real Wazuh label set instead of trusting the frontmatter verbatim:
| Intent | Real label to apply |
|---|---|
| Bug / defect | type/bug |
| Feature / enhancement | type/enhancement |
| Engineering task / chore | level/task |
| Every issue | untriaged — applied automatically on open/reopen/transfer by .github/workflows/add-untriaged.yml, no manual action needed |
Do not invent labels beyond this set, and do not invent an approval workflow.
5. Emit the ready-to-file body + report
Default deliverable — stop here. Output the filled issue body plus a short report for the human to review:
Issue pre-flight
- Template: <file>
- Labels: <label list>
- Duplicate check: no matches found / possible match: <issue-url>
- Command to open it: gh issue create --template <file> --label "<labels>"
Only run gh issue create when the user explicitly asks you to open the
issue.