Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Adding time spent from all issues

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?

2 answers

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 and @Bill Sheboy )

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?

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

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

Like Alex Koxaras likes this

Hello all,

Just thinking about another way to solve this from automation:

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

Best regards,

Bill

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

I have something functioning with JMWE, but for some reason, it doesnt fire on issue updated (When logging time) or when Time Tracking changes. I noticed your solution listens to the Time Tracking field @Alex Koxaras , have you had any issues with it actually getting hit when logging time/work?

Hi @Jordan Berry ,

The only thing that I've noticed, which to me is rather important, is that it takes a quite significant amount of time to calculate it (above 1sec). Other than that, with normal use of the fields, you shouldn't encounter any problem imo.

Alex

This may just be a silly question, but how do you get it to trigger? Just by logging time? Or am I missing something fundamental?

By selecting the appropriate trigger. In our case it would be "Value Change" trigger. Try something like the following:

Screenshot 2021-04-29 095403.png

Like Bill Sheboy likes this

@Jordan Berry and yes. You trigger it when somebody is logging time.

Ahh. See that is not triggering in my instance. I have opened a ticket with Atlassian and they confirmed there was an issue

Hmm.. that's bad luck, but on the bright side it's good that Atlassian confirmed the issue. Now all they have to do is resolve it :)

If it's ok with you, let me know what was the problem.

Hi, community!

That sounds like this existing defect, which includes a suggested work-around:

https://codebarrel.atlassian.net/browse/AUT-2171

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

94 views 0 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you