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; } } }

Jira smart value {{issue.description}} not fetching the issue description in auto email

Shreyash Kulkarni_59xiej

I have created an automation rule

It will be triggered when issue is transitioned to Done status - the rule will crosscheck the issue type and component and send an email.

All the smart values return the content except the {{issue.description}} one. What could be the reason?

Ive tried adding the description while creating the subtask itself but it still doesnt return the ticket description.

Please let me know what else I can try and what could be the reason.

Update - for anyone facing a similar issue, please check if there exists a custom field with the same name in your project and swap the jira smart value with {{issue.customfield_10xx}}

Screenshot 2023-08-03 172248.png

Accepted answers

Jack Brickey

The "description" field in the subtask is a custom field while the "description" field in primary issue types are system fields . While you can successfully use {{issue.Description}} for primary issues you need to use the Custom field ID {{issue.customfield_10xx}} for subtasks.

All comments

Jack Brickey

Hi @Shreyash Kulkarni , it should work. Dumb question...is the description field blank? Can you add a log action to your rule and log the {{issue.description}} then check the audit log results?

Tomáš Vlach_z6iizm

Hello @Shreyash Kulkarni

is there possibility that there are another smart values in the actual body of the description?

Tom

Bill Sheboy

Hi @Shreyash Kulkarni

Adding to Jack's questions:

For a question like this, please post images of your entire automation rule, the specific action (without extra highlighting/annotation), and of the audit log details showing the rule execution.

Those will provide context for the community to offer ideas. Often where in a rule actions occur impacts behavior and so seeing the images may help. Thanks!

And also...what type of project is this: company-managed or team-managed? Have you checked if there are multiple fields named "description" leading to a problem with the smart value resolving correctly?

Kind regards,
Bill

Shreyash Kulkarni_59xiej

Hi, @Bill Sheboy . Thanks for your thoughtful guidance. It is a company-managed project.

Here is the entire automation rule.

Screenshot 2023-08-04 112616.png

Here is the subtask description and comment

Screenshot 2023-08-04 113310.png

@Jack Brickey I have added log action to the rule and checked the audit log.

Screenshot 2023-08-04 113643.png

Jack Brickey

Thanks for the details @Shreyash Kulkarni

I note that your email component uses Summary. Does that work? Does the email have the Summary? The log component references Description and is blank which, unless the Description is indeed blank, has me scratching my head. It works ok for me. At this point I would suggest the following actions:

attempt a simple test rule in another project: trigger manual, action comment add description to comment
failing the above, contact Atlassian support

@Bill Sheboy , any other observations/ideas?

Shreyash Kulkarni_59xiej

Hi, @Tomáš Vlach

There aren't any smart values in the actual body of the description.

Jack Brickey

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

jira-software-cloud