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

{{issue.Story Points estimate}} can not be retrieved in automation

Alex Artyomov

I am trying to write an automation that needs to get the story point data from the issue.

The problem is that neither {{issue.Story Points estimate}} nor {{issue.Story Points}} return any values:

I tried this in Audit log:

```

Issue: {{issue.key}}. Start date will be set to: {{now}}. Story Points estimate is: {{issue.Story Point estimate}}. Story Points is: {{issue.Story Points}}. Ceiled Story Points estimate is: {{issue.Story point estimate.ceil}}. Due Date will be set to {{issue.created.plusBusinessDays(issue.Story point estimate.ceil)}}

```

And this is what I get:

```

Issue: FTA-136. Start date will be set to: 2021-06-23T06:18:44.7+0000. Story Points estimate is: . Story Points is: . Ceiled Story Points estimate is: . Due Date will be set to

```

Screen Shot 2021-06-23 at 10.01.49.png

Accepted answers

All comments

Bill Sheboy

Hi @Alex Artyomov -- Welcome to the Atlassian Community!

Here are some follow-up questions which may help the community to offer you suggestions:

Are you using a company-managed or a team-managed project? Company-managed uses {{issue.Story Points}} and team-managed uses {{issue.Story Point estimate}} please note the capitalization and that the one for team-managed is singular, not plural, for Story Point.
What is the issue type of the item you believe is missing the values? When you view that item do you see the story point field with values on the page?
Would you please post an image of the audit log from the rule execution where you believe it should be showing the values?

Thanks, and best regards,

Bill

Alex Artyomov

@Bill Sheboy

1. We are using team managed project.

2. This is the log message format that I am using:

Issue: {{issue.key}}. Start date will be set to: {{now}}. Story Points estimate is: {{issue.Story Point estimate}}. Story Points is: {{issue.Story Points}}. Ceiled Story Points estimate is: {{issue.Story Point estimate.ceil}}. Due Date will be set to {{issue.created.plusBusinessDays(issue.Story Point estimate.ceil)}}

An example result that I am getting:

As you can see the value for Story Points estimate field is empty.

The value is set in the issue:
Screen Shot 2021-06-24 at 0.11.19.png

Bill Sheboy

Hi, Alex. Thanks for that information, and please try to keep your responses in one thread. That will help the community members when they look in the future to see if there are alternative answers to a question. Thanks!

Okay, now that we know you are using a team-managed project, you may remove the other values from that logging message, and...

Why are you trying to use ceiling for {{issue.Story Point estimate}} as that is usually an integer value, right?
Let's try this: create a new log action and re-type in that smart value by itself. That will rule out any bad characters in the value.
Next, check with your site admin to confirm there is one-and-only-one field named "Story Point estimate" in your project.

Alex Artyomov

Hi Bil,

- We are using story points as a float values

- I created a log action just with {{issue.Story Point estimate}} value and the result is the same: I don't get any value for it:

Screen Shot 2021-06-29 at 9.18.29.png

- I am the project admin and I can confirm that there is one-and-only-one field named "Story Point estimate" in our project:

Screen Shot 2021-06-29 at 9.20.46.png

Bill Sheboy

Thanks for that information, Alex. I am stumped, and I suggest that you submit a defect to Atlassian Support to see what they can find. They have more access to internal logs than customer users do.

As site admin for a paid instance, you may submit a defect here: https://support.atlassian.com/contact/#/

Once you hear from them, please post back here so the entire community can benefit from what you learn. Thanks!

Daniel Grunwald_khax4z

Hi @Alex Artyomov and @Tom Pradat

as it turns out the docs are wrong, as I learned from Atlassian-Support:

"Please note that the actual smart value for the team managed project's stoprt point is - issue.Story Point estimate (without s in Point)."

VInay Naik_yth3fs

This is the correct answer.

Changing {{issue.Story Points estimate}} to {{issue.Story Point estimate}}

did the trick for me.

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

cloud

jira-software

jira-software-cloud