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

Jira automation can't find "story points" field

Lawrence Lam_cdhe24

I am using Jira Deverloper Cloud. I have created a very simple Jira automation rule that creates a task whenever a sprint is create. The new task have 2 fields populated by the automation.

a. sprint = next sprint

b. story points = 0.25

This automation rules last ran successfully on Aug.26, 2020. Today when I created a new sprint the automation rule created the new task, but failed to find the story points field. (see diagram below "automation error"). What is strange is that the automation rule only offers "story points" as a field to populate (see diagram below "automation fields"), but the actual field in the task it populated successfully on Aug.26 was "story point estimates". "Story points estimates" field is on the "task" issue type (see diagram "task fields').

Can someone tell me if I am doing some thing wrong or this is a bug in Jira?

```````````````````````````` automation error ````````````````````````

automation error.jpg

``````````` task fields ```````````````````````

task fields.jpg

````````````````````` automation fields ```````````````````````

automation fields.jpg

Accepted answers

All comments

Henrique Degan

Ola sujiro fazer um teste com outro campo criado, na mesma automação ou em uma automação manual, teste, ve se carimba o campo?

Coloque aqui se deu certo.

Andy Heinzer

Hi @Lawrence Lam,

Sorry to hear about this problem. I understand that this is a next-gen project and you are trying to setup an automation rule that creates a new issue and sets the Story point field. Thank you so much for the detailed screenshots, it really makes it a lot easier to understand what you are trying to do and the results you get here. I took a closer look at this and I found that I experienced the same problem, even with a completely different trigger.

So I created a bug ticket for this over in JRACLOUD-75140. I found that the error is trying to actually set a different Story Point custom field in Jira here, and not really the custom field that is specific to that next-gen project. Next-gen projects manage custom fields a lot differently than classic projects do. In next-gen projects, custom fields only have a context limited to that project. However the field you are selecting here, and the field automation is trying to set is not really the custom field "Story Point Estimate" that exists in that project.

The good news is that I found a work-around for this.

First in the Choose fields to set, uncheck Story points (this is technically the wrong field)
Then at the bottom of the page, scroll down to More options,

In more options, manually set the field using json like so:

{
    "fields": {
        "Story Point Estimate": 57
        }
}

Save/publish run

This will set that field correct to a value of 57 when the automation rule is run.

Again, sorry for the inconvenience, I agree that the interface should not be showing that specific field in this case. In the meantime, I hope that this work-around will help you to get past this problem in the short team.

Regards,

Andy

Henry Yei_fexq30

Also looking for a solution here to read the Story Point Estimate for a condition before setting it to a value (if not set, set to default story point)

Henry Yei_fexq30

I was using advanced compare and could not find a smart value for next-gen Story Points, but a JQL condition of Story point estimate = null worked fine.

Michael Wolfgram

Starting with Andy's suggestion, I tried to use JSON in a cloning automation I am creating to clone a story (including the estimate). I want the story point estimate to be the trigger issue's story point estimate, but get the following error: "Error creating issueOperation value must be a number (customfield_10016)"

It all works fine if I hard-code a value where I have the italicized code below. Does anyone see what I did wrong?

{
"fields": {
"Story Point Estimate":"{{triggerIssue.Story point estimate}}"
}
}

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-desk-cloud