Issue Creation

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.

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-alerting

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-alerting): bug_report.md and feature_request.md are upstream-inherited templates with full frontmatter (name, about, title, labels) and are shown as chooser cards. Their claimed bug/enhancement labels are stale — see step 4 for the real labels to apply.

compatibility_request.md is accurate: all three of its labels (request/operational, level/task, type/maintenance) exist in the repo and its title is a template you fill in (Compatibility with OpenSearch (version)), not a [PREFIX] tag.

documentation.md has no frontmatter at all — no name/about/title/ labels — so it won't show as a chooser card and applies no default label. It is not really meant for a person to file manually here: the .github/workflows/create-documentation-issue.yml workflow appends a PR link to it and files it as an issue in the upstream opensearch-project/documentation-website repo (label documentation, title Add documentation related to new feature) whenever a PR in this repo is labeled needs-documentation. If the user wants a documentation issue filed in this repo instead, use documentation.md's body as free-form content with no default labels.

config.yml only declares contact_links (OpenSearch community support, AWS/Amazon security reporting) — it does not set blank_issues_enabled: false, so blank issues remain allowed alongside the templates. Regardless of template, .github/workflows/add-untriaged.yml auto-applies the untriaged label to every new issue on open/reopen/transfer — so the actual end-state label set always includes untriaged, even where the template's own frontmatter can't deliver it.

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:

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.