Find out time spent on stories for each developer

Posted by
Emma Foster Oct 17, 2018 4:54:00 PM

Time tracking is important for agile software development as it allows project managers to better estimate, gives visibility into how time is managed and spent as well as knowing what an organisations resources are working on ensuring they are aligned with overall business goals. 

For a high-level overview of activities and progress across an organisation, time, resources and project information may be scattered in spreadsheets. This lack of centralised data and visibility may become a liability to business growth.

Many organisations are now using JIRA and JIRA Service Desk as a tool to track their agile software development projects and processes. By aligning how teams are entering and tracking their time against stories, bugs or tasks within JIRA it means that project managers can roll-up that information to gain insight into resource allocation, efficiency and productivity.

Benefits gained by tracking time:

Project Planning: Calculate your work in progress as well as your work throughput and average lead time helping you to plan ahead, refine delivery dates and react to changing circumstances. See how changes to team structure or size can affect progress and spot early warning signs of bottlenecks.

Resource Management: Ensure that the right resources are working on the right tasks at any given time. Track if work is arriving faster than your team can cope. Team members and project managers can see how they’re spending their time and make better decisions for resource allocation in the future.

Real-time Insights: Get the most up to date and accurate picture how teams and projects are performing. 

Account Management: Leverage JIRA's rich dataset to answer the seemly simple but often intractable question: Are we on budget? 

Extracting JIRA's rich dataset into high-level KPIs using ServiceClarity gives agile project managers the flexibility to create customisable, real-time, data rich KPIs to monitor team performance and make continual process improvements. Using JIRA time tracking and ServiceClarity we will look at how to find the time spent on stories for each developer. 

ServiceClarity provides a set of unique data collectors specifically for working with your JIRA data. These range from simple issue counters to time trackers and also more specialised JIRA ServiceDesk SLA trackers. The value that these ServiceClarity JIRA data collectors provide builds upon the JIRA’s own query capabilities: the JIRA Query Language (JQL).

ServiceClarity leverages all of the power of JIRA’s JQL search to ensure that your ServiceClarity KPIs are tracking just the right JIRA issues, enabling you to track specific projects, user groups and status changes. For a Completed Time Spent on Stories KPI we need to consider the following JQL query within our ServiceClarity metric:

{base_jql} AND issueType = 'Story' AND status = 'Done' AND (resolutiondate >= '{START_OF_DAY}' AND resolutiondate <= '{END_OF_DAY}') AND timeestimate is not EMPTY and timespent is not EMPTY

Within this JQL query we are selecting the types of issues we are trying to find, which is stories:

AND issueType = ‘Story’

Then we need to select the stories that have already been completed: 

AND status = 'Done'

We then track the issues that have been resolved between the start and the end of the day:

AND ( resolutiondate >= ' { START_OF_DAY } ' AND resolutiondate <= ' {END_OF_DAY} ' )

We tell JIRA to provide only data that has estimates and time recorded on them:

AND timeestimate is not EMPTY and timespent is not EMPTY

 The base JQL is defined in the ServiceClarity connector and might include the project name:


 Our Completed Time Spent on Stories metric will now look like:


Above you can see breakdown has been added as a collection configuration this gives us the option to see completed time spent on stories broken down by priority, client, assignee, Epic Link or Sprint. 

Now we have the correct raw metric data we can quickly convert this metric to a KPI to start using it within our reports and share data with the team. To format the raw data correctly and display the breakdowns required the following KPI Calculation Configuration can be used:

//Use metrics variable to get the latest value of the KPIs metric
var completed = metrics.getLatest('Completed Time Spent - Stories');

//Use the latest metric value and convert to hours var value = completed.value(0) / 3600;

//Convert the metric breakdowns to hours using the scale function
var breakdown = completed.breakdown().scale(1 / 3600);

// Return the numeric value for our metric and the breakdown metadata for the metric return { value : value, breakdown : breakdown }

Our KPI is ready and collecting data in the correct format, it is available in our KPI library and can be added to reports in order to visualise and keep an eye on our targets. We will also be able to see the trend over weeks, months or years and the breakdown for each range by assignee (developer).


Along with this initial KPI you can see how breaking out more KPIs and analysing time in different ways, across different projects can help track and refine processes.


Read our article on Are we on Budget? as another example of tracking time and extending it to cost analysis. ServiceClarity and time tracking gives project managers deep insight into a projects activity but also a clear instant view of project performance that can be shared to internal teams or high-level executives.

Time tracking gives an organisations C-Level Executives an overview of work outcomes and whether a project aligns with the overall company goals. Is more time being spent on R&D? or How much time is being spent on fixing existing products?

Time tracking allows for visibility and awareness so it can be tracked and improved. 

You can start tracking your JIRA time today, sign up to our 7-day free trial:

JIRA KPI reporting free trial


Topics: JIRA, DevOps Reporting, DevOps, Agile, Time Tracking

Subscribe to Email Updates