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

Smart value {{issue.issuetype.name}} doesn't return any value

Pauline Dupuy

Hello there,

First and foremost, i'd like to thank this community that allow me to find every answer i was looking for so far.

HOWEVER, i'm stumbling on a stupid problem.

I'm trying to use the smart value {{issue.issuetype.name}} in my automation, so the email that is sent shows the issue type name in my list of task along with summary, key etc..

My automation is as follows :

Trigger : scheduled every monday at 9am

1. Lookup issues

2. Send email (content below):

{{#lookupIssues}}
<a href="{{url}}">{{key}}</a> - {{summary}} - {{issue.issuetype.name}}
{{/}}

Everything works fine BUT no value from the smart value {{issue.issuetype.name}} is returning in the email, it's just blank.

The type of issues are not custom.

I really don't understand what is wrong.

Thanks !

Accepted answers

Walter Buggenhout

Hi @Pauline Dupuy and welcome to the Community!

I am not sure if these smart value keys are case sensitive, but I would not be surprised if this does matter. From the documentation, issueType has a capital letter 'T':

{{issue.issueType.name}}

Hope this helps!

All comments

Walter Buggenhout

Hi @Pauline Dupuy and welcome to the Community!

I am not sure if these smart value keys are case sensitive, but I would not be surprised if this does matter. From the documentation, issueType has a capital letter 'T':

{{issue.issueType.name}}

Hope this helps!

Pauline Dupuy

Thanks for your reply Walter, i already tried that, and it's not case sensitive

Walter Buggenhout

Have you tried to just leave out the initial issue part? I notice that it is not being used for key and summary either. So:

{{issueType.name}}

Tobias H

I believe it is as @Walter Buggenhout wrote in his latest reply, drop the issue before issueType and it should work.

I have a scheduled automation in place to post new additions (last 24h) from our backlog to our teams Slack channel and in it I use an almost identical code as what you wrote in the initial question.

{{#lookupIssues}}
<{{url}}|{{key}} - {{Summary}}> [{{issueType.Name}}]
{{/}}

Tobias H

Comes out looking like this:

(If you copy my code, feel free to drop the brackets around the issueType if you don't like how it looks. And perhaps move the > behind summary to behind key instead, if you don't wish for the summary to be clickable.)

Pauline Dupuy

Yes that's it.
I had already tried this but without the capital T !
So both your answers are good in the end

Thanks a lot, you saved my day.

Pauline Dupuy

I've made this change yes after Walter's answer and it works fine. Thanks

Have a nice day

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation