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

Problem: The priority is not displayed in the email.

Luisa Seil

Hello,

I would like to send my team all non-updated issues as an email once a week. For this I use LookupIssue and then want to display selected fields in the email. This works for everyone except priority. What am I doing wrong?

{{#lookupIssues}}
{{summary}}
{{key}}
{{status.name}}
{{project.key}}
{{priority.id}}
{{assignee.displayName}}
{{created.mediumDateTime}}
{{updated.mediumDateTime}}
<a>{{url}}</a>
{{/}}

Thank you.

Accepted answers

All comments

Ste Wright

Hi @Luisa Seil

Is this in Cloud or DC?

What shows up for Priority? Or is it just blank?

And is there a reason you're using {{priority.id}} as opposed to {{priority.name}}?

Ste

John Funk

Hi Luisa - Welcome to the Atlassian Community!

Try using the custom field value for the Priority field instead:

Where 0000 is the ID of your priority field.

Luisa Seil

Hi @Ste Wright

We use DC.

It is blank.

I actually wanted priority.name. But that didn't work, so I tried priority.id, which doesn't work either.

Thank you.

Luisa Seil

hi @John Funk

So I already searched for theSmartValue and it's "priority". I used this page as a guide.

Find all available smart values for a Jira issue | Cloud automation Cloud | Atlassian Support

Is that what you mean? Or how can I find the id of my priority field?

Thank you

John Funk

Yes, have you tried to drop the .id and just use {{priority}} or {{issue.priority}}?

Luisa Seil

Hi, @John Funk

Yes, I have tried both.

I've just tried doing it without lookupissue. Then the priority is displayed, but I get a separate email for each problem. So the problem lies in the combination of lookupissue and the priority field.

Now I am trying to display all issues in one email, and the only solution I have found is lookupissue.

I know the problem has changed, but do you have any ideas?

Thank you

Ste Wright

Hi @Luisa Seil

I tried {{priority.name}} (albeit in Cloud) and it did work fine. I also tried {{priority}} which provided the ID.

Perhaps see if you can send an email with just the Priority field (still using Lookup Issues), not the others - and see what happens?

Ste

Luisa Seil

hi @Ste Wright and @John Funk ,

Thank you very much for your help.

I have solved the problem now by doing it without lookupissue and with bulk processing option enabled. And that works.

Thank you again.

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira-service-management

jira-service-desk-unknown-hosting-type