Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I'm building an email that sends ticket data to a user. It's a manual trigger and seems to be working just fine except for Issue Type. I can't get it to populate the Issue Type field in the table. Below you can see what I'm using for that field. I'm using the {{#lookupIssue}} function to get my tickets.
I've used: issueType.displayName, Issue Type, customfield_10106, customfield_10106.displayName, Type.name and many more.
I will put the entire code below
All
{{#lookupIssues}}{{/}}
Issue Type | Issue Key | Assignee | Title | Description | Story Points |
---|---|---|---|---|---|
{{issueType.displayName}} | {{key}} | {{assignee}} | {{summary}} | {{description}} | {{Story Points.format("#")}} |
I guess everything I read online was true. It looks like the issueType field is a custom field and thus does not show up in a {{lookupIssues}} response. The way I got around this was to: branch off of the original ticket, use JQL as the "Type of Related Issues", make sure "Process all issues produced by this trigger in bulk" is checked, add table code to my email using the {{#issues}} code {{/}} to render the table.
Hope this helps someone.
Make sure you make the email recipient "Initiator" unless you have a group or specific person you want the email it to Always go to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This smartvalue works on my Jira instance.
{{issueType.Name}}
I hope this works for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nope. Strange how this is the only field that will not display.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Marc - Devoteam This didn't work in the table but did work as a log action. Any thoughts on why? Could it be because it's part of a lookupIssue function?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I put the {{#lookupIssues}} function in a log action and it does not show the Issue Type field info.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register Now
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.