I am having trouble forcing Jira Automate to execute my rule that starts with `Branch Created` trigger. My GitHub for Jira app is set to have access to all repositories. When I simply push a new branch with name `release/test` to origin, the rule does not execute. I've also tried adding a specific JIRA issue as well as smart commits into the latest commit and then pushing the new branch to origin with no effect. We are on next-gen projects only.
I suspect only branches created that have a ticket name as part of its name trigger this rule. If so, is there any other way to do what I want?
Screenshot of my test Automate rule.
Hi @Henry Yei
I believe that you are correct that the issue must be referenced in the branch name. Please see these two documentation pages for details:
https://support.atlassian.com/jira-software-cloud/docs/automation-triggers/
https://support.atlassian.com/jira-software-cloud/docs/configure-development-tools/
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.