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

Update storypoint value of parent addition or subtraction

nicolas lembeye

Hello guys !

I found a way (via this link : 3 Easy Ways To Sum Jira Story Points - Agile Docs Software) to sum up story point into Parent tasks in Jira. The problem i have is the following :

Let's say i have a task with 0 storypoints.

Step 1 :

I create 1 sub-task with 1 storypoint --> Task get updated and now displaying 1 storypoint

Step 2 :

After review with Team, i change sub-task storypoint to 5 --> Result should be task is now displaying 5 storypoint.

But instead task is displaying 6 storypoint (1+5).

Do i have a jql request instead of this one : {{triggerIssue.Story Points}} + {{issue.Story Points}} ?

Thanks a lot

Accepted answers

Bill Sheboy

Hi @nicolas lembeye

Let's disregard any concerns around assigning story points to subtasks for now...

One safer way to do this summation with an automation rule is to always sum the total completely, ignoring any plus/minus changes over time. To do this, branch to the parent and use the sum function: {{issue.subtasks.Story points.sum}}

Kind regards,
Bill

All comments

Robert Wen_Cprime_

The problem I see on this is that you want {{triggerIssue.Story Points}} to be cleared when you change {{issue.Story Points}}. This may collide with the case when you add additional sub-tasks at a later time.

Bill Sheboy

Hi @nicolas lembeye

Let's disregard any concerns around assigning story points to subtasks for now...

Kind regards,
Bill

Tobias C_

And by the way.. story points for sub-tasks? I have one team who also did this. I asked them why they do this kind of micromanagement.

Lean manager might say this is waste. Estimations don´t get better if you calculate every little step. Esp. if the time invested for trying to estimate little things is higher than the time for resolving the sub-task/s.

If the sub-tasks have high story points it might be a sign to think about story splitting and also creating value for the customer with every splitted story.

https://www.atlassian.com/agile/project-management/user-stories

Cheers
Tobias

nicolas lembeye

Hello Bill,

I'll try this out today. But seems a viable solution. Thanks a lot.

nicolas lembeye

Yeah i agree, i just didn't found a list of all JQL request for Storypoint so i was a bit confuse.

nicolas lembeye

@Tobias C_

Well, we can argue about this you're right. I'm working on Embedded system and we don't really use User Stories. Our architecture is mostly Epic-->Task-->Sub-task.

Still learning the good way for project configuration in such configuration for new-comer Agile Team.

I am willing to listen your point of view if you have time.

Tobias C_

You are right Nicolas.

If Tasks / Sub-Tasks work for you - it´s fine, because it depends always on the working context.

Most important answer in agile context is: "It depends".

Scrum does not say one has to use "User Stories".

Listen to the customer and inspect what is needed to create epic stuff iteratively (and maybe Jobs-to-be-done can bring also some insights).

All the best
Tobias

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server