How do i find the time tracked on an issue(which spans multiple Sprint) for the desired Sprint?

Question

We have the same task that spans multiple Sprints.

Obviously they are not broken to an epic is the primary issue here.

But lets say an engineer works on an issue ISV001 as below.

Sprint 1

1. Sprint 1 time tracks 2 hrs in ISV001.

2. Sprint 1 is completed.

3. When the utilization is pulled this will reflect correctly as 2 hrs for that issue ISV001.

Sprint 2

1. Sprint 2 commences.

2. Sprint 2, time tracks 4 hrs in ISV001.

3. Sprint 2 is completed

When the time tracking is pulled for Sprint 2 will this will say 6 hrs on the issue ISV001 for that engineer (or) 4 hrs?

Is there a way to get 4 hrs of utilization in Sprint 2 for that engineer/issue using JQL?

Iryna Komarnitska_SaaSJet_ · Answer

Hi @Kishorekumar Neelamegam ,

Try to use the add-on Cost Tracker for Jira Cloud by my team.

In it, you can create time reports using JQL filters.

Example of time report:

Here for you 30-day trial to understand if app good for you. Enjoy and have good results in your work!
P.S. Also, in our article, we describe, how you can estimate the sprint cost in Jira.

Rahul_RVS · Answer

Hi @Kishorekumar Neelamegam

If you would be interested in a mktplace app to get detailed time spent reports, you can try out our add-on.

For your specific use case, the app allows you to filter for time entered between specific date ranges. So if you enter sprint start and end dates, it will show the time spent with that specific period only.

Worklogs Time Reports

The app provides the following features.

* Worklogs Report :* Create reports for time entered by your team members
* Filter/Categorize/Group By your worklogs data

* Timesheets : View/Enter time spent for multiple issues and multiple days from a single screen
* Dashboard gadgets

Disclaimer : I work for the vendor who built this app

Trudy P Claspill · Answer

Hello @Kishorekumar Neelamegam

Jira does provides only the simplest reporting for time tracked against an issue.

To get what you want you would need to look at using a third party app from the Atlassian Marketplace, or using the REST API to extract the worklog records for each issue and parse through them yourselves to figure out which ones are for which sprint.