AutoMaxGuides
GitHub and Jira
Check runs, PR comments and deduplicated issues on GitHub; issues, links and transitions on Jira.
What you'll learn
How the GitHub and Jira providers are configured per project with secret names only, what each does on a finished run, how issues are deduplicated by scenario fingerprint, and how tags link scenarios to existing issues.
Configure
integrations:
github:
enabled: true
owner: siri1410
repo: AutoMax
checkRun: true
prComment: true
createIssueOnFailure: smoke # never | smoke | always
labels: [automax, test-failure]
tokenEnv: GITHUB_TOKEN
jira:
enabled: true
baseUrl: https://acme.atlassian.net
projectKey: SHOP
issueType: Bug
emailEnv: JIRA_EMAIL
tokenEnv: JIRA_API_TOKEN
createIssueOnFailure: always
transitionOnPass: Done
linkTaggedScenarios: trueOnly variable names are stored; values come from the environment where automax runs.
What happens after a run
Link scenarios to issues
@ui @regression @jira:SHOP-42 @github:123
Scenario: Discount code appliesautomax integrations sync -p demo-shop scans features for these tags, creates links, and refreshes their status. The run viewer shows the status next to the scenario.
Commands
bun run automax integrations test -p demo-shop --provider github
bun run automax integrations notify --run-id <id> --from-files --dry-run
bun run automax integrations sync -p demo-shop
bun run automax integrations links -p demo-shop--from-files builds the summary from the run directory, so notifications work without a database.