You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
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".
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".
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}}.
I recommend you to place the "Log action" in case you need to debug the rule.
Feel free to post a comment if you found anything unclear.
Kenta Yamamoto
Atlassian TeamTechnical Support Engineer
Atlassian
Yokohama, Japan
8 accepted answers
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
2 comments