Skip to content

Jira

Issue links, release notes and change requests.

Category Issues & change management
Authentication OAuth 2.0 (3LO) or API token
Provider id jira
  • Link issues found in commit messages
  • Generate release notes
  • Jira change-request gates (Business and up)
  • Transition issues on deploy
  1. Create an API credential in the issue tracker.
  2. Add the integration in Slipway and map projects.
  3. Reference ticket keys in commit messages; Slipway links them to releases.
  4. For change gates, add a change_ticket gate to the environment protection rules.

Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.

provider: jira
config:
site: acme.atlassian.net
project_keys: [PAY, CORE]
transition_on_deploy:
production: Done