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

Adding time spent from all issues

Jordan Berry

I am running into a wall when trying to get this to work. What I would like to do is to sum up all of the time spent on all of the issues linked on an epic, and then all of the epics linked to specific issue.

So it would look something like this (Lets say Theme is the custom issue type)

Theme <- Epics <- Story/Tasks

Is there any way to do this with OOTB, Automation, or with the JMWE plugin?

Accepted answers

Alex Koxaras -Relational-

Hey @Jordan Berry

Unfortunately the way I approach this problem was with automation and with lookupissue smart value. Lookupissue smart value can only be used with specific values (Smart values - general | Jira Service Management Cloud | Atlassian Support). As stated in the previous link that @Trudy P Claspill provided, you'll see a workaround for story points, which utilizes the "Create Variable" action within the automation.

I'm not aware if you could use JMWE, since anything from JMWE will be inside the workflow, thus you'll lose the ability of a "listener" (unless JMWE has a listener of its own).

Scriptrunner most likely would be my choice for calculating anything.

Cheers,
Alex

All comments

Trudy P Claspill

Concerning trying to do this with Automation you might be able to leverage some of the lessons learned in this post:

https://community.atlassian.com/t5/Jira-Software-discussions/Calculate-the-sum-of-original-estimates-of-all-issue-types-to-an/td-p/1660572

(Credit to @Alex Koxaras -Relational- and @Bill Sheboy )

Jordan Berry

Oh this is brilliant. My only issue would be with Story Points, as our teams use that field. Is the .sum function available on fields other that Story Points?

Alex Koxaras -Relational-

Hey @Jordan Berry

I'm not aware if you could use JMWE, since anything from JMWE will be inside the workflow, thus you'll lose the ability of a "listener" (unless JMWE has a listener of its own).

Scriptrunner most likely would be my choice for calculating anything.

Cheers,
Alex

David Fischer

JMWE for Jira Cloud actually offers "Event-based Actions", which is the equivalent of event listeners (which it uses behind the scenes).

Bill Sheboy

Hello all,

Just thinking about another way to solve this from automation:

use a webrequest action to call the REST API for a JQL search, selecting the issues you care about
parse the response using text match() function with RegEx to build a list of the originalestimate nodes, saving as a created variable. If there are grandchild sub-tasks, use aggregateorginalestimate instead
Convert the created variable to a list with split() function, and then use list's sum function to add up the values.

I haven't tried it but I expect it should work.

Best regards,

Bill

Alex Koxaras -Relational-

@David Fischerdidn't know about that! But it's quite good to know that you have this functionality implemented inside JMWE!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud