Use workflow triggers for company-managed projects
The following are the triggers you can add to your work items' workflows out of the box. All the triggers below require an integration with a code repository, like Bitbucket or Github, or an integration with other Atlassian development products, like Bamboo or Crucible.
Read more about configuring workflow triggers.
Read more about extending your Jira site.
Default workflow triggers
Pull request created
Automatically transitions the work item when a related pull request is created in a connected repository.
Pull request merged
Automatically transitions the work item when a related pull request is merged in a connected repository.
Pull request declined
Automatically transitions the work item when a related pull request is declined in a connected repository.
Pull request reopened
Automatically transitions the work item when a related pull request is reopened in a connected repository.
Branch created
Automatically transitions the work item when a related branch is created in a connected repository
Commit created
Automatically transitions the work item when a related commit is made in a connected repository
Deployment successful
Automatically transitions the work item when a related Bamboo deployment is successful.
Deployment failed
Automatically transitions the work item when a related Bamboo deployment failed.
Review started
Automatically transitions the work item when a related review is started in Crucible
Review abandoned
Automatically transitions the work item when a related review is abandoned in Crucible
Review submitted for approval
Automatically transitions the work item when a related review is submitted for approval in Crucible
Review closed
Automatically transitions the work item when a related review is closed in Crucible
Review rejected
Automatically transitions the work item when a related review is rejected in Crucible
Review summarized
Automatically transitions the work item when a related review is summarized in Crucible
Was this helpful?