How do I match a ticket with the build successful trigger?

[Henry Yei]

I am trying to transition tickets from from one status to another when an associated  build is successful.

However, I am unclear on how a ticket is matched to run the automation when a build is successful. None of my tickets are being matched, I can see in the audit log:

Action details:

Advanced compare condition

The following issues did not match the condition:

TIC-3407

Where does the build need to reference the ticket in order to be matched? Is it the value in build.name, or branch.name smart value only, or elsewhere?

The build is showing up in the above the "Development" section of the JIRA ticket as successful under the Github Actions section.

The TIC-3407 is in a commit message which is part of the branch that is being built. I assumed that if the appropriate build was showing up as part of the tickets development section, it was was associated and would work with the trigger, is this not supposed to be true?

[Mark Chaimungkalanont · Accepted solution]

The TIC-3407 is in a commit message

This should automatically link the ticket and if you use the "Build successful" trigger.

As far as smart values go, the best way to debug is to add a "log action" and output the smart value to the logs to see the details.

https://support.atlassian.com/cloud-automation/docs/debug-an-automation-rule/

We should have the "build" object available. You should try adding the debug 

Build: {{build}}
Name: {{build.name}}
URL: {{build.url}}
State: {{build.state}}

Hope that helps!

[Henry Yei]

I had only added build.url and build.refs, will be adding the rest of the smartvalues for the build object for further data.

[Henry Yei]

I didn't realize that the branch smartvalue is only available for when the branch is created, so it was matching nothing. For the simple notification  in this example, I should just put a slack notification webhook in github action, but I had wanted to do other jira related actions when code related to jira tickets were merged into a branch. It does not like this functionality is available. 

[Stefan Salzl]

Hi @Henry Yei ,

For better understanding and analyzing the problem:
Could you please provide more date? --> screenshot of your rule and audit log would be great to see what happens.

Best
Stefan