Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

How to access branch name from issue automation

I have an automation (my first) which I am trying to set up, where an issue being transitioned to Awaiting Testing will run a bitbucket pipeline kicking off smoke tests on the branch associated with the ticket.

It seems the branch smart values are not available, so what would be the recommended way to be able to get this information? 

Thanks for your assistance

 

Screenshot 2022-02-18 at 14.02.00.png

1 answer

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 18, 2022

Hi @Stanford Kamau 

The branch smart values are currently only available with the Branch Created trigger: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/

There are some suggestions to make them available with other triggers for the issues.

A couple of possible work-arounds would be to:

  • save the branch name somewhere (e.g. issues, entity properties) when the Branch Created trigger fires (with a different rule), or
  • to try calling the source control tool's API.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events