githubnext / githubnext/gh-aw-test
Suggested test: copilot/jira-create-issue
- Dominant language
- Shell
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
## Motivation
github/gh-aw#57814 — "Add first-class Jira safe outputs" merged upstream, adding `jira-create-issue`, `jira-update-issue`, `jira-add-comment`, `jira-add-label` with credential isolation via `JIRA_BASE_URL`/`JIRA_USER_EMAIL`/`JIRA_API_TOKEN`. No coverage exists in `gh-aw-test`.
## Proposed test
- **Workflow file**: `test-copilot-jira-create-issue.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `jira-create-issue`
- **Variant**: standard
## Minimal test prompt sketch
Configure `safe-outputs: { jira-create-issue: {} }` with a `samples:` block for deterministic compile/emit validation. Prompt: "Emit a jira_create_issue safe output describing a test issue."
## New fixtures or secrets needed
Full end-to-end validation needs a Jira Cloud instance + `JIRA_BASE_URL`, `JIRA_USER_EMAIL`, `JIRA_API_TOKEN` secrets — none currently exist for this repo. Initial coverage can be samples-only (compile + safe-output-item validation), same limitation as the Linear suggestion.
## Notes
Related to the sibling Linear and Azure DevOps safe-output PRs (#57816, #57796) merged the same day — all three follow the same "external ticketing system safe output" pattern and could share a triage discussion about whether/how to provision live credentials for gh-aw-test.
> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/33609783863) · copilot · auto · 83.2 AIC · ⌖ 8.02 AIC · ⊞ 8.8K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-test+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-test%2Fsuggest-new-e2e-tests%22&type=issues)
Contributor guide
No contributing guide indexed for this repository
Research direction
Create test-copilot-jira-create-issue.md with a workflow_dispatch trigger, the copilot engine, jira-create-issue safe output, and a samples block. Start by comparing the related Linear and Azure DevOps safe-output tests or suggestions. Done means the workflow compiles and safe-output-item validation passes with deterministic sample data; live Jira credentials are not required for initial coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100