Jira
Issue links, release notes and change requests.
At a glance
Section titled “At a glance”| Category | Issues & change management |
| Authentication | OAuth 2.0 (3LO) or API token |
| Provider id | jira |
What it does
Section titled “What it does”- Link issues found in commit messages
- Generate release notes
- Jira change-request gates (Business and up)
- Transition issues on deploy
Set up
Section titled “Set up”- Create an API credential in the issue tracker.
- Add the integration in Slipway and map projects.
- Reference ticket keys in commit messages; Slipway links them to releases.
- For change gates, add a
change_ticketgate to the environment protection rules.
Configuration
Section titled “Configuration”Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.
provider: jiraconfig: site: acme.atlassian.net project_keys: [PAY, CORE] transition_on_deploy: production: DoneRelated
Section titled “Related”- Integrations overview
- Secrets for how credentials are stored and masked
- Webhooks and events for the events integrations subscribe to