Smart values in automation rule no longer working

Question

We have some automation rules that are triggered upon branch creation, using the smart value {{branch.repository.name}} we have some condition logic.

All the rules worked previously, but recently, this smart value has stopped working. When I check it, I see that it is no longer supported (unavailable smart values). Please see the attached screenshot.

Bill Sheboy · Answer

Thanks for confirming that...I just recreated that message from the "help" and so I wonder if it is a documentation error.

Please show images of a complete rule and the audit log details for one that was working and is not any longer.

Are you able to identify when it stopped working, and if any changes occurred in your source control / pipeline tooling configuration?

If you just write the {{branch.repository.name}} to the audit log and test the rule, does it contain the value as expected?

Joris Huisman · Answer

Hi Bill,

Thank you for your response.

This rule is triggered by branch creation, so it should give me the branch smartvalues. As I mentioned before, it has been working consistently for the past years, but it recently stopped functioning. I haven't made any updates to this rule. I have added a printscreen of an empty project, as you can see the smart values are unavailable on a branch creation trigger.

Kind regards,

Joris

Bill Sheboy · Answer

Hi @Joris Huisman -- Welcome to the Atlassian Community!

The message does not indicate the smart value is not supported.  What is means is for the current context in the rule, the smart value is not available.

The branch-related smart values are only available with the branch-related, rule triggers:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--branch--

Kind regards,
Bill