Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Adaptavist Script Runner: enforce branch names with an EXISTING Jira issue number?


I'm using Adaptavist Script Runner to enforce branch naming standards. The pre-receive hooks prevent pushes from remote repos and the script event handler prevents creating wrongly named branches in the Bitbucket web UI. However, it only checks that the name conforms to the regex.

The way it's implemented, I could create a branch with a validly formatted jira issue, such as "story/MYPROJ-1234". However, jira issue "MYPROJ-1234" may not exist in jira. I'd like to make it so it will only allow branches named with validly formatted Jira issues that also exist in Jira.

Is there a way in Script Runner to take a Jira issue number and search Jira issues somehow to make sure it's an existing issue?

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events