Hi, I am trying to accomplish a rather unusual task and wondering if automation rules can do the magic. Here is what I want to accomplish: When status of a user story is changes (for this example, status is changed from 'Backlog' to 'Elicitation' status), I want to: * Take the value in Story Points field * Calculate 80% of the value in Story Points field * Populate the answer in 'Remaining Story Points' custom field. For example, if original estimation is 100 story points, at changing status from 'Backlog' to 'Elicitation', the rules should automatically calculate 80% of the estimation and populate '80' in the 'Remaining Story Points' field. Is it actually possible to accomplish it using automation rules or another method?

Waqas bhai A.o.a please send me your no im forget your no my no 4033615667 im asim bro of amir nadeem thank u

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

How to use automation rules for calculating remaining story points

Waqas Aleem

Hi,

I am trying to accomplish a rather unusual task and wondering if automation rules can do the magic.

Here is what I want to accomplish:

When status of a user story is changes (for this example, status is changed from 'Backlog' to 'Elicitation' status), I want to:

Take the value in Story Points field
Calculate 80% of the value in Story Points field
Populate the answer in 'Remaining Story Points' custom field.

For example, if original estimation is 100 story points, at changing status from 'Backlog' to 'Elicitation', the rules should automatically calculate 80% of the estimation and populate '80' in the 'Remaining Story Points' field.

Is it actually possible to accomplish it using automation rules or another method?

Accepted answers

All comments

Bill Sheboy

Hi @Waqas Aleem

I believe that is possible by various methods, including automation rules. However I am unclear why one would do this; it seems to redefine the meaning of "story points", particularly ignoring the ambiguity of relative sizing measures.

What problem are you trying to solve? Knowing that may help the community to offer suggestions to help. Thanks!

Kind regards,
Bill

Waqas Aleem

I know it is rather unusual to reduce story points estimation based on status transition. My organization is embracing agile but still producing traditional project management reports. Story points are considered a measure of effort required instead of size or complexity of the work item. One of the reports we are asked to produce displays ‘remaining effort’ based on status of the user stories. For example, a user story in the backlog is considered 0% done, one in QA status is considered 60% done and one in UAT status is considered 80% done. Hope it helps.

Bill Sheboy

Thanks for that information, @Waqas Aleem

As the organization is where you describe in their transition, you could also try: use story points with no changes, and add a "progress measure", based on your workflow, until it is no longer needed. That progress measure could be the percentage you mention, updated on issue transitions. And at team retrospectives discuss how it is helping and how to evolve its usage.

To get you started on creating your rule for the progress measure, please review this documentation and examples:

Waqas Aleem

Thanks.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud