Calculate number field to calculate story points from subtask to task , task to story ,story to epic

Question

Hello All,

I want a calculate number field to calculate story points as below:

A Task "is linked with" several (N) USTIBB(subtask)
A Story is a "Parent of" several (N) Task.
An Epic is a "Parent of" several (N) Story.
In the example we have 4 Tasks: Task 1, Task 2, Task 3, and Task 4.
Each Task "is linked with" several USTIBB containing defined Points.
USTIBB Issue Type is a catalog of types of Tasks and can be linked several times to the Tasks.
Story A sums Points for Task 1 (1+2+13=16) and Task 2 (3+8+20=31), total 16+31=47.
Story B sums Points for Task 3 (0,5+2=2,5) and Task 4 (13+20=33), total 2,5+33=35,5.
Epic One sums Points for Story A (47) and Story B (35,5), total 82,5,.

I have found this solution , but i want to also include task and subtask in a single query.

sum(fieldValue({10106}, issuesUnderEpic(%{00015})))

Regards,

Mateusz Sołowianiuk_f8cfkk · Answer

Hi @Rohitkumar Gupta

If you are willing to use a WBS-based solution for your projects, BigPicture's Gantt module has fully-customizable Column Views allowing you to aggregate the data on the parent task's level (please see Column Configuration section for more details).

In case you find that this meets your expectations, I encourage you to give our plugin a try here - no installation required.

I hope that this clarifies.

Best regards,

Mateusz Sołowianiuk

SoftwarePlant Support

Dave Rosenlund (Trundl) · Answer

Hi, @Rohitkumar Gupta. @Nic Brough -Adaptavist- is right. Summing "up" from sub-tasks would be a very unusual approach for estimation purposes. However, if your organization is disciplined about doing things this way, it can be done.

But not with Jira out of the box (AFAIK) -- you will need a Jira app from the Atlassian Marketplace.

As Nic suggested, a scripting tool would be one way. I see customers using ScriptRunner or Power Scripts most often. A project management solution that is built-around WBS concepts, like BigPicture or Structure for Jira, can also be used.

Structure for Jira has a built-in "sub over sub-items" feature that would automatically do what you describe on a wholesale basis -- even if the Jira issues live in different Jira projects (full disclosure, I work for the company that makes Structure).

-dave [ALM Works]

Sivarama Krishna K · Answer

As per JIRA Structure Story & Task are at same level.

You can not make a Task under Story.

I am not sure who is guiding you to proceed this way, the concept is going wrong.

0.5 story point is assigned to one Sub-Task. It is very much not correct.

Story Point should start with 1. Not below that. Better read How to estimate Story Point.

As per my knowledge JIRA Supports 2 level of structure and 3 level of concept

Even though EPIC & Story are issues in JIRA, you can link EPIC and Story.

We follow the below structure in practice.

1. EPIC --> Story --> Technical Task (Agile Methodology)

2. EPIC --> Task --> Sub-Task (Task Management)

In our understanding Story is explained in general terms. So, Technical Tasks required to do actual work.

Task is a technical item. So, any dependent activities can be added to complete the task. Else, we can continue with EPIC & Task. Sub-Task is optional.