{{issue.Story point estimate}} not showing in automated emails

Akash Mukherjee July 16, 2024

Hello, I have been trying to automate jira in a way such that we get all the details regarding any story task or bug posted on the jira board that transitions from "in progress" to "done". The email is supposed to be having all the necessary details including the story points as well but no matter what the story points are not being shown in those emails

 

| Issue Key | Summary | Assignee | Status | Transition Date | Story Points | |-----------|---------|----------|--------|-----------------|--------------| {{#lookupIssues}} | {{key}} | {{summary}} | {{assignee.displayName}} | {{status.name}} | {{changelog.status.last.updated}} | {{Issue.Story point estimate}} | {{/lookupIssues}}

This is the email query that I use. We are a team based board so I use Story point Estimate and the lookup issues jql query is :

(project in (10002)) AND (status changed FROM "In Progress" TO "Done" After -14d)

Any help is really appreciated <3

2 answers

1 accepted

2 votes
Answer accepted
Bill Sheboy
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.
July 18, 2024

Hi @Akash Mukherjee -- Welcome to the Atlassian Community!

When inside of the iterator for {{#lookupIssues}} ... {{/}} data, do not use the issue. prefix as the fields are coming from the lookup.  For example:

{{#lookupIssues}}
{{key}} -- {{Story point estimate}}
{{/}}

 

Kind regards,
Bill

Hans Polder _Devoteam_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 18, 2024

@Bill Sheboy , you rock! Thanks for the assist - this indeed works.

Like Bill Sheboy likes this
Akash Mukherjee July 18, 2024

Thank you so much sir! It indeed worked, you are amazing

 

Like Bill Sheboy likes this
Akash Mukherjee July 18, 2024

Can you also help me out in this regard. I created a new custom field called Shirt Size and I used the same format as the story points but it is not showing in the email. Can you please let me know where am I going wrong?

 

Bill Sheboy
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.
July 19, 2024

Smart values are name, spacing, and case-sensitive, and they may not exactly match the displayed name on the issue pages.  When an incorrect smart value is used, it returns null and so often fails silently in rules.

 

To find the correct smart value (or its custom field id) please use this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

The essential steps are:

  • identify an example issue with your field
  • using a browser tab, call the REST API endpoint to get the issue data, substituting in your Jira URL and the example issue's key:
yourJiraURL/rest/api/3/issue/exampleIssueKey?expand=names
  • search on the page for your field to find its exact smart value and custom field id
  • update your rule to use the correct one

If the smart value does not work, try the custom field id, such as with:

{{issue.customfield_12345}}

 

Akash Mukherjee August 11, 2024

Am sorry to bother you again but I made a small change to the {{lookupissues}} and all of a sudden the story points stopped showing in the report. I am not getting any indications either to why such thing is happening. 

The Lookup issues JQL is (status changed FROM "To Do" TO "Done" AFTER -7d) OR (status changed FROM "On Hold" TO "Done" AFTER -7d) OR (status changed FROM "In Progress" TO "Done" AFTER -7d)

 

The Email setup is 

Hi Admin,
 
Here are the issues transitioned from "In Progress" to "Done" in the last 14 days:
 
Issue Key | Summary | Assignee | Status | Story Points |
{{#lookupIssues}}
{{key}} | {{summary}} | {{assignee.displayName}} | {{status.name}} | {{Story point estimate}} |
{{/lookupIssues}}
 
Best regards,
Jira Automation

 

Bill Sheboy
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.
August 12, 2024

Hi @Akash Mukherjee 

Was the only thing changed the JQL for the Lookup Issues action?

Is this rule only running in a Team-managed project?

Please post an image of the audit log details showing the rule execution.  That will provide context to help explain this.

Akash Mukherjee August 12, 2024

yes the only thing that was changed was the jql for the lookup issues action and yes it is a team managed project so we use story point estimate. prior to the jql change your method was working just fine and give the story points on the email report. the audit log inly shows success and no other given context

 

Bill Sheboy
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.
August 12, 2024

Please post an image of the audit log details showing the rule execution.  I want to confirm which issues were returned for the lookup so they can be compared to...

Using the JQL used in the Lookup Issues action, if you try that stand-alone with Filters > View All Issues, which issues are returned with values in the Story Point Estimate field?

Akash Mukherjee August 12, 2024

Screenshot 2024-08-13 110146.png

Akash Mukherjee August 12, 2024

All the issues that were filtered by the lookup issues jql do have the story point estimate values before changing the jql they were showing using your method but eversince I made the JQL change the story points are not showing.

 

 

Akash Mukherjee August 12, 2024

when i validate the jql query and it gives a proper return of the list of issues we are looking for in the report as well

 

1 vote
Hans Polder _Devoteam_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 16, 2024

@Akash Mukherjee ,

In my instance, the field that actually has the data is not 'Story point estimate', but 'Story points':

{{issue.Story points}}

Screenshot 2024-07-17 072505.png

Akash Mukherjee July 17, 2024

Its a team run board and not a company one so I have to use story point estimate.

 

Hans Polder _Devoteam_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 17, 2024

@Akash Mukherjee ,

Ah, you are right, I missed that part. When I test it in a team managed project, it indeed needs to be the one you're using.

Screenshot 2024-07-18 062252.png

 

Before we continue, can you please share some screenshots of your entire automation rule configuration, with screenshots of the separate steps as well? 

I see the same behavior if I try it on my side. @Marc Koppelaar could you maybe spread your Automation wisdom?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events