Skip to content

Tighten bug report template traceability #269

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ExplodingUFO merged 1 commit into from
May 14, 2026
Merged

Tighten bug report template traceability #269

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 29 additions & 1 deletion .github/ISSUE_TEMPLATE/bug_report.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,11 @@ assignees: ""

Describe the problem directly.

## Traceability

- Related GitHub issue or PR:
- Related Beads issue:

## Reproduction

1.
Expand All @@ -24,6 +29,12 @@ What should have happened?

What happened instead?

## Regression scope

- First affected AsterGraph version or commit:
- Last known good version or commit:
- New regression, existing defect, or unsure:

## Environment

- AsterGraph version:
Expand All @@ -39,7 +50,20 @@ What happened instead?
- Support-bundle attachment note:
- Claim-expansion status:

## Verification
## UI / Screenshots

- [ ] no UI impact
- [ ] UI impact; screenshot or visual proof attached
- [ ] UI impact; screenshot still needed
- [ ] unsure

## Blocking impact

- Blocks PR or stack:
- Blocks release lane:
- Blocks adopter route or support boundary:

## Current verification

Which lane or command shows the problem?

Expand All @@ -48,6 +72,10 @@ Which lane or command shows the problem?
pwsh -NoProfile -ExecutionPolicy Bypass -File .\eng\ci.ps1 -Lane contract -Framework all -Configuration Release
```

## Expected fix verification

Which command, proof marker, screenshot route, or acceptance check should prove the fix?

## Notes

Anything else that helps narrow the failure.
Loading