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

story point estimate is not found when sum story points of all subtasks with automation

Michael WANG_1hk3o4

Hi ,

i want to sum story points with automation in jira, and made this logic.

Action details:

Issue condition

The following issues passed:

PORTAL-475

Edit issue

Additional fields contains invalid field(s) in 'update' or 'fields' section.

Story point estimate

i checked it, there is no "story point estimate" field for user story and task backend, but there is for web frontend. but it's ok for subtaks. which field i should use?

how can i fix it ? many thanks

Accepted answers

All comments

Stefan Salzl

Hi @Michael WANG

for better understanding and further investigation: could you please explain what you are trying to solve with your automation rule from a use case perspective? What is your setting? when should the rule be triggered? which issues do you have in place? which story points from where would you like to sum and whaat for? what should they be used for?

Could you also share a screenshot of your current automation rule?

Best
Stefan

Michael WANG_1hk3o4

Hi @Stefan Salzl ,

what I want to do is to sum the story points of all subtasks automatically for one user story or task. and I created a new automation rule for it. and I activated the "story points" for estimation in the project setting=>feature.

I will attach the screenshot I have made in the automation rule.

The issue comes in the 3rd step "Edit issue fields", I can't find the "Story point estimate" in the dropdown list. and so, the rule can't run well.

looking forward to your solutions!

Stefan Salzl

Is your project team-managed or company-managed?

Could you please also share a screenshot of the configuration of your "edit issue fields" action?

Best
Stefan

Stefan Salzl

Guess I´ve got the problem already:

There is a different field for the estimation in team-managed and company-managed projects.

Within team-managed projects this field is called "Story point estimation". Unfortunately (as you already pointed out correctly) this cannot be chosen in the dropdown field so the advanced edit function via JSON needs to be used. I tried this in my environment and it worked (see the screenshot):

I´ll add this here as text so you can copy this directly:

{
"fields": {
"Story point estimate": {{issue.subtasks.Story point estimate.sum}}
}
}

Please give it a shot and let me know if it works.

Best
Stefan

Welcome!

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

Quick Links

Find more posts tagged with

automation