Fresh terminology for automation rules and components

An automation ‘rule’ is now a ‘flow', and a ‘component’ is now a 'step’. You may notice some inconsistencies in the documentation while we make this change. Read more about the updates in Automation

Automation smart values - projects

Check out how we use smart values in our Jira automation template library.

The page describes the smart values available for accessing details related to Jira projects. These smart values can be used with the Project created trigger.

project.id

Returns the ID of the project that triggered the flow.

{{project.id}} //returns 11200

project.key

Returns the project key of the project that triggered the flow.

{{project.key}} //returns NUC

project.name

Returns the name of the project that triggered the flow.

{{project.name}} //returns Project Nucleus

project.projectTypeKey

Returns the triggering project's type. Possible types are BusinessSoftwareService management, or Discovery.

{{project.projectTypeKey}} //returns Software

project.avatarUrls

Returns the triggering project's avatar URL.

{{project.avatarUrls}} // returns 48x48=https://acme.atlassian.net/secure/projectavatar?pid=11200&avatarId=10404, 24x24=https://acme.atlassian.net/secure/projectavatar?size=small&s=small&pid=11200&avatarId=10404, 16x16=https://acme.atlassian.net/secure/projectavatar?size=xsmall&s=xsmall&pid=11200&avatarId=10404, 32x32=https://acme.atlassian.net/secure/projectavatar?size=medium&s=medium&pid=11200&avatarId=10404

Still need help?

The Atlassian Community is here for you.