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

Access to development-wise smart values in Jira Automation

Jira automation users tend to miss out that smart values - development (i.e., branch, commit, pull request) are only available via the DevOps triggers. I was one of those, to be honest. This article introduces a tip on how to make it accessible via any triggers such as the "Scheduled".

 

(1) Create a trigger

As an example, I'll make the commit URL accessible in a component hooked by any triggers. As mentioned before, those development-wise smart values are only available via the trigger corresponding to the entity which you want to access. That means, in my case, I need to choose the "Commit created".

devops-triggers.png

(2) Set entity property

Then set the value {{commit.url}} as an issue property. You can name the key whatever you want. That is it! As the entity property is accessible via any triggers, now you can retrieve the latest commit URL at any component. For instance, you can refer to the stored value with {{issue.properties.commitUrl}}.

set-issue-entity.png

 

(3) Optional: how to debug the rules

I recommend you to place the "Log action" in case you need to debug the rule.

audit-log.png

 

Feel free to post a comment if you found anything unclear.

2 comments

M Amine
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 26, 2020

thank you @K_ Yamamoto for this great tip. Automation is really helpful.

Like K_ Yamamoto likes this

is there a way to get the branch name where the commit has been made during a commit created trigger?

Like Olga Dayneko likes this

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events