Report on time spent across all issue types in given period

Is there a pure JQL query (without an add-on) to get this?

I want to report on how much time was spent over the past 30 days doing production support vs. forward development. I can get the below collection, but using the SumofTimeSpent column, there is no way I can come up with to discern time logged only in the past 30 days. In other words, I need to find out the sum of work logs recorded in the past 30 days and determine how much was against production support and how much was against story. By the way, alll work logs in my instance are on subtasks - there is nothing on the parent, by design.

issuetype in ("Production Support", "Story")
updated >= -30d

3 answers

Anything, gang? Is there something similar that you do to answer this type of question?

...let me ask it another way then...why is the work log object not accessible via JQL? How do we get time out of JIRA between a given duration?

Without Tempo (I am probably going to go there for next year), how do you solve this, gang? There must be someone out there trying to get similar type of data? Thx in advance.

I'm interested in this as well, but I see know answers that don't involve a plugin. It seems odd that this isn't built-in functionality. The work logs are all timestamped...

Wish I could have helped.

I ended up purchasing the Tempo Timesheets add-on for my atlassian cloud. While Tempo is good, there is a fundamental flaw that no one anywhere seems to care about...

Tempo Timesheets, as of this writing at least, continues to have no concept of issue lineage so there is no such report that can identify the parent issue to which the subtasks beloing to for roll-up billing information. So, if in your instance, you have no work logs on parent issues like me, and you're expecting to be able to get a report presenting all of the story summaries with the hours spent on each, you cannot achieve this. For my billing needs, I'm forced to yield a pretty nice Tempo report displaying an Account, but I must also cobble together a secondary report that presents the list of parent issues that were worked with that data. Those interested in a billing perspective, don't care to read all of the low level subtask summaries, but they certainly need to understand the top level parents (stories, etc) that defines the business capabilities to assess where the money was spent.</endrant>

Ouch. Sorry you're dealing with that. That too seems like something that should be built-in functionality in Tempo... It's very odd that these otherwise amazing tools have these types of "gotchas" that I'd assume many people are not happy about...

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,206 views 13 19
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot