Linked design automation triggers

[Harsh Jain]

Hey everyone, 

I linked a design on a JIRA ticket and added an automation when the design update triggers. The design update trigger works well but is also fired when design status is being changed. This doesn't seem to be the expected behaviour. Moreover, the design status which is populated in the smart value ({{design.status}}) is always none.

Can someone please help with this.

[Mohanraj Thangamuthu]

Hello, Good day. Could you elaborate the automation rule use case more. What I understand is when an issue is linked a rule is getting triggered, unable to get the exact issue.

[Bill Sheboy]

Hi @Harsh Jain -- Welcome to the Atlassian Community!

Adding to the above suggestions, please note the {{design}} smart value is only available with the design-related rule triggers: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-design/

Perhaps if you provide more context that will help the community to offer better suggestions:

• What problem are you trying to solve?  That is, "why do this?"
• Provide an image of your complete rule (in a single image file)
• Provide an image of the audit log details showing the rule execution
• Explain what is not working as expected, and why you believe that to be the case

Kind regards,
Bill

[Harsh Jain]

@Mohanraj Thangamuthu  @Bill Sheboy This is related to the linked design automation triggers - Link

What I am facing is that according to the docs mentioned, a linked design update trigger should be triggered when the design linked is updated in Figma - which is working fine. But, this trigger is also invoked whenever the design status is being changed (from none -> ready_for_development).

Second issue that I am facing is that according to this doc - {{design.status}} should contain the smart value of the design status. But what I am getting is none always. All the other smart values are populated successfully.

Can you please help with these issues. 

Thanks,
Harsh

[Bill Sheboy]

Once again, for automation rule questions please post images of the complete rule and audit log details.  Those provide context for the community to offer suggestions.  Thank you.

Without seeing those...

Please consider Figma is an external tool, and integration with built-in features like automation rules likely requires dynamically looking up information in Figma.  This can both create delays and impact where the smart values can / cannot be used in a rule.  Thus the {{design.status}} smart value may not be present / accessible in some rule actions.

You can test this hypothesis by writing this expression to the audit log, testing your rule, and then reviewing the log:

design status = >>{{design.status}}<< and design status name = >>{{design.status.name}}<<

If there is a value in the log, but not with the action where you use the smart value, it is a timing problem.  That could be solved by first saving the value using the Create Variable action and then using the variable later.

Also it is likely any updates to the linked design are detected as "updates" for the trigger, including a change of status.  I checked the Atlassian public backlog and did not see this behavior in any suggestions / issues, so perhaps work with your Jira Site Admin to contact the Atlassian Support team to ask what the behavior should be: https://support.atlassian.com/contact/#/