Adding request type to automation email

[Mihir Ruparelia]

Hello, 

I wonder if its possible to in the email body to show the request type. 

For example

Hi,

Please see this {{request.type}} created by {{reporter.displayName}}. 

For more information, please see <a href="{{issue.url}}">{{issue.key}} - {{issue.summary}}</a>

I suspect what I have written is incorrect. Any ideas please?

[Mihir Ruparelia · Accepted solution]

@Patricia Francezi many thanks will test it now

[Patricia Francezi · Accepted solution]

Hi @Mihir Ruparelia 

You should use {{Request Type.name}} to achieve your goal. 

I also suggest you have this page in your favorites https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

This will helps you anytime you have the same question

[Mihir Ruparelia]

@Patricia Francezi that didn't work its not the biggest issue in the world. thank you though.

[Patricia Francezi]

I guess the issue you triggered didnt have the request type filledup. 

Remember, Issue type and Request type (or customer request type) are different fields.

When we create an issue via Jira UI (not the portal) we need to select the request type and its optional, unless you have it as required field. 

[Mihir Ruparelia]

The request type field is auto populated based on the title of that form. But it did not seem to add it to the automation email. 

Thanks for the help though I will continue to see if I can make it work :)

[Aaron Williams]

@Patricia Francezi to revive an old thread, I'm having this issue as well, I've tried a variety of versions of inputting the field into the email body and it gives a blank result but if I put it in the subject line it comes up.

I'm trying to output a table of requests so there are a few different Request Types to display, and I've verified they are not null. Any ideas?

[Bill Sheboy]

Hi @Aaron Williams 

I recommend creating a new question, and linking back to this one.  That will ensure more people see it to contribute, as only people following this older thread may see it.

When you post your new question, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Kind regards,
Bill

[Aaron Williams]

Thanks, @Bill Sheboy, I'm currently drafting up the new question already but definitely wanted to try my luck tagging @Patricia Francezi and @Mihir Ruparelia just on the off-chance they may see this and have the answer!