Suggested test: copilot/jira-create-issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
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.
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 · copilot · auto · 83.2 AIC · ⌖ 8.02 AIC · ⊞ 8.8K · ◷
- Dominant language
- Shell
- Stars
- 8
- Forks
- 5
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-test
-
suggested new test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-test#16875 ·
-
agentic-workflows suggested new test
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-test#16262 ·
-
suggested new test
Difficulty 2/5 1-2 days Newbie friendliness 78/100
githubnext/gh-aw-test#15805 ·
-
suggested new test
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
githubnext/gh-aw-test#15094 ·
-
suggested new test
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-test#15092 ·
All issues in githubnext/gh-aw-test
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·