When Jira triggers stop working

Stephan Köllen 11-04-2019

troubleshooting configuration

We added some convenient triggers to our Jira installation that allow us to automate specific processes.

For example you can let your issues transition on certain git actions in connected repositories. Create a new related branch to an issue? Most probably you want to start working on the issue (set it to "In Progress"). Or you might like to transition an issue to "Ready for Release" when a related pull-request was merged.


If your set up triggers simply stop working you may try some simple troubleshooting:



Read on for what a trigger is and an overview on how to set it up.


In order to set triggers for Jira projects you need to dive in workflows that are attached to your projects.

Simply spoken, these workflows describe or define which steps an issue goes through till it is resolved. E.g.:

The issue-movement from one step to another is described as a transition. Transitions on the other hand can get triggered through simple actions like using the jira interface (pull an issue in a new kanban column) or through automated "hooks".

So we can go to the attached workflow, create or view the respective transition and create triggers for that transition.

Connected git

Connected version control accounts help Jira to be aware of related issues. After an account is connected, we can relate to issues via their identifier (or issue key, e.g. KEY-111). So use this key within your branch name or your commits to inform Jira, that this branch / commit is related to the issue at hand.

So in order to work properly, your Jira app needs to know of your code-repository actions that happen there. So sometimes if your trigger is not working, when creating new repositories or other changes occurre, you might check your connected repositories or refresh them.

Re-add your trigger

Recently on of my transition triggers stopped working while no settings were changed. Well, turn it off and on again.

This did the trick.