You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm trying to use automation to create a JIRA release version on Branch created starts with a certain string. It appears the Branch created trigger only fires when a branch name contains a jira ticket reference which is useless in this situation. Is that really a limitation of this trigger or am I doing something wrong?
We follow gitflow naming conventions which means release candidate branches are in the format release/xxx.
You can see the trigger fires and logs correctly when a branch starts with a JIRA ref, screen below.
Hi @Iain Johnson and welcome to the community,
to catch a branch created trigger natively the answer (from my point of view) is: yes, the branch needs to have a jira reference. This is the only connection between gut and jira. Otherwise the branch is created within your git system but how should jira detect when the link (via issue key) is not set? Jira does not observe any git system by itself but the connection between git and jira can be done via issue key (in commits and/or branch name).
Besides that I could imagine that your use case could be done with a kinda more complex solution like sending a webhook from your git system and grabbing this webhook via a automation rule.
Thanks Stefan, I've gone with a webhook solution. I guess I was assuming the GitHub/Jira integration allowed jira to be made aware of pretty much anything happening in GH regardless of whether it related to an issue or not. The trigger description certainly implies it will be pick up any branch creation, not just one with a jira ref.
We live and learn.
@Iain Johnson , hi! Glad to hear you've resolved your issue. In case you decide you try an alternative approach in the future (like a 3rd party option), check out ZigiOps here at Atlassian marketplace. It connects the two systems bi-directionally and syncs them instantly. No additional coding. If you want to see it in action, feel free to book an explanatory demo - just for further clarification.
BR, Diana (ZigiWave team)