Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,341
Community Members
 
Community Events
176
Community Groups

Calculate productivity and efficiency using JIRA automation

Hello Everyone,

I have an original estimate on a story and time spent data, which has been logged over Story Sub-Task and on story also. Manually, it's been getting difficult to calculate the productivity of my team and how efficient they are on a story level. So, is there a way using JIRA Automation that can help me to calculate productivity and efficiency from original estimation and time spent data?

1 answer

0 votes
Sam Harding Atlassian Team Dec 05, 2021

Hi @Rahul Singh 

I am not sure what you would exactly want in order to determine productivity on a particular story, but we do provide the ability in Automation to programatically see the values of the original estimate and the time spent.

We provide smart values on an issue {{issue.timetracking.originalEstimate}} and {{issue.timetracking.timeSpent}}, which return the relevant values. If you wanted to, you could for example send an email of all open stories on a daily basis, where there is a comparison of the original estimate and the time spent. This would be achieved by:

Trigger -> Scheduled Trigger (maybe set to daily)

Lookup Issues -> Do a JQL search for open stories

Send email -> Send an email with the estimates, for example

Here are the estimates for our open stories:
{{#lookupIssues}}
Issue: {{key}}
Original Estimate: {{timetracking.originalEstimate}}
Time spent: {{timetracking.timeSpent}}
------------
{{/}} 

Or, if you want to be more particular, you can do some logic here to get more relevant data. For example, if you wanted to only send emails about stories which have had more time spent on it than the original estimate, you can filter the lookup issues JQL search to add a condition where timeSpent > originalEstimate.

Hope that helps point you in the right direction

Cheers
Sam

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events