I am looking to create an automation where: * When a release is created * If it has a specific value inside it's description field then * issues will be created under it How do I handle the condition part?

Hi @yanivlt you can access the new version (if the creation is the trigger) with smart values. For version, you can use: * {{versions.name}} - Returns the name of the affects version * {{versions.description}} - Returns the description of the affects version. * {{versions.archived}} - Returns true if the affects version is archived, and false if not. * {{versions.released}} - Returns true if the affects version is released, and false if not. * {{versions.releaseDate}} - Returns the affects version's release date. Can be combined with other date and time See Automation smart values - issues | Cloud automation Cloud | Atlassian Support for more info. For your case it should look something like this:

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Creating automation with condition on release fields

yanivlt

I am looking to create an automation where:

When a release is created
If it has a specific value inside it's description field then
issues will be created under it

How do I handle the condition part?

Accepted answers

Rebekka Heilmann (viadee)

Hi @yanivlt

you can access the new version (if the creation is the trigger) with smart values.

For version, you can use:

{{versions.name}} - Returns the name of the affects version
{{versions.description}} - Returns the description of the affects version.
{{versions.archived}} - Returns true if the affects version is archived, and false if not.
{{versions.released}} - Returns true if the affects version is released, and false if not.
{{versions.releaseDate}} - Returns the affects version's release date. Can be combined with other date and time

See Automation smart values - issues | Cloud automation Cloud | Atlassian Support for more info.

For your case it should look something like this:

Screenshot 2024-05-12 131649.png

All comments

Rebekka Heilmann (viadee)

Hi @yanivlt

you can access the new version (if the creation is the trigger) with smart values.

For version, you can use:

{{versions.name}} - Returns the name of the affects version
{{versions.description}} - Returns the description of the affects version.
{{versions.archived}} - Returns true if the affects version is archived, and false if not.
{{versions.released}} - Returns true if the affects version is released, and false if not.
{{versions.releaseDate}} - Returns the affects version's release date. Can be combined with other date and time

See Automation smart values - issues | Cloud automation Cloud | Atlassian Support for more info.

For your case it should look something like this:

Screenshot 2024-05-12 131649.png

yanivlt

Thanks, tried it but not working.

Suggestions

Rebekka Heilmann (viadee)

The smart value is wrong.

It needs to be version without the "s" -> {{version.description}}

The reference is from the Issue section, so for when you access the fix version of an issue. It's a bit confusing.

I tested that on my site and it definitely works.

Screenshot 2024-05-12 151801.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation