📣 Automation Update: {{object.Name}} Now Returns Name Attribute

[#1]

Hi Atlassian Community! 👋

We’re always listening to your feedback and working to make Assets more reliable and intuitive. Today, we want to share an update on bug fix for an issue affecting automation rules that use the {{object.Name}}. smart value & Label.

What was the issue?

A bug was identified regarding the behaviour of the {{object.Name}} smart value in automation rules containing Assets components. The root cause was traced to a scenario where, if the label attribute was changed from the default Name attribute, {{object.Name}} would return the value from the label attribute instead of the intended Name attribute. As a result, automation rules using {{object.Name}} may have returned unexpected values, potentially impacting your workflows and data accuracy.

What’s changing?

We are rolling out a fix that restores the intended behavior of {{object.Name}}smart value. You can now expect the {{object.Name}} smart value to correctly return the value from the Name attribute, regardless of which attribute is set as the label.

This change brings clarity and consistency to your automation rules, so you can trust that your data is accurate and your workflows run as expected.

Why does this matter?

This change may alter the output of your existing automation rules that use {{object.Name}}Smart Value, potentially affecting downstream processes, work items, and communications.

What action do I need to take?

Review your automation rules - If you have rules that use {{object.Name}} with Assets components (such as triggers, actions, or conditions involving Assets), please review them to ensure they’ll continue to function as intended. The output of these rules may change now that {{object.Name}} returns the correct attribute. Proactively reviewing your rules will help prevent any unexpected disruptions.

FAQ

Q: Will my automation rules break?
A: No. your automation rules will not break or throw errors as a result of this fix. However, the data returned by the {{object.Name}} smart value may change to reflect the correct Name attribute. This could impact downstream processes, work items, or communications that rely on this value. We recommend reviewing your rules to ensure they continue to deliver the results you expect.

Q: When will this change be rolled out to my instances?
A: Our goal is to minimise the disruption and provide as much lead time as possible to review automations rules. We understand that this change might lead to silent changes in smart values output. Hence, we are following a cautious and gradual rollout out schedule.

Q: How will I know that this fix has been rolled out to my instances?
A: There are no UI changes that can be used as a signal, however, you’ll notice that the {{object.Name}} smart value in your automation rules now return the value from the Name attribute, not the label attribute. This can be tested directly in automation using Log action. It’s recommended to review Automation rules early and check for expected {{object.Name}} and label outputs.

Q: Do I need to update my existing automation rules?
A: It is recommended to review any automation rules that use {{object.Name}}, especially if you’ve customised label attributes in your Assets schema. While rules won’t break, the output may change, so a quick review will help you avoid any issues.

Q: Does this fix affect other smart values or only {{object.Name}}?
A: This fix specifically addresses the {{object.Name}} smart value. Other smart values are not impacted by this change. If you use other object attributes in your rules, their behaviour remains unchanged.

Need help?

If you need assistance or believe this change has impacted your automaton rules, reach out to support referencing this article and JSDCLOUD-13400. 

Thank you!

Your feedback directly shapes our roadmap and helps us deliver a better product for everyone. If you have further suggestions or encounter any issues, please let us know in the comments below.

Kind regards,
Michael Fedulov
Product Manager, Assets (Cloud)

[Bill Sheboy]

Hi @Michael Fedulov 

Thanks for this information.  Yes, and...one way teams may check for impacts to validate this change is:

• export all of the rules in their sites / products,
• search the resulting JSON for the smart value, and
• review those specific rules to determine any necessary changes / testing required.

Kind regards,
Bill