Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Pauline Dupuy February 16, 2023

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 !

2 answers

1 accepted

3 votes
Answer accepted
Walter Buggenhout
Community Champion
February 16, 2023

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 February 16, 2023

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

Walter Buggenhout
Community Champion
February 16, 2023

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}}
Like # people like this
Pauline Dupuy February 17, 2023

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.


Like # people like this
0 votes
Tobias H
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2023

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 16, 2023

Comes out looking like this:

lookupissue.png

(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 February 17, 2023

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

Have a nice day 

Like Tobias H likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events