You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Everyone,
I have a requirement to filter the value of the Time log minus (-) original estimate or vice versa.
Scenario:
Let's say the Original estimate is 4 days and I have logged the work for 5 days and I need to return the value in a field with the value 1 day ( time log - original estimate).
Please let me know if there are any alternatives to achieve this.
Note: We are hosted on Cloud instance and not using any Add-ons
Thank you in advance
Hello @Sai kiran P
There is a field called remainingEstimate that is set each time Time is logged. Does that fulfill your need?
Also a good potential solution. The "remaining estimate" field simply returns "0" when the time logged exceeds the estimate entered. And of course issues with time logs and no time remaining is different than issues without time logs (meaning the remaining estimate field is null.) Ex:
JQL: remainingEstimate = "0"
vs.
JQL: remainingEstimate is empty
For what it's worth, if you want to access the "remaining estimate" field using an automation smart value, use: {{issue.remaining estimate}}
Fun stuff!
Rachel Wright
Author, Jira Strategy Admin Workbook
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sai kiran P ,
I have an idea for you. Try using Jira Cloud's built-in automation feature to do the calculation and then filter over estimated and under estimated issues by the calculated result.
Create an automation to periodically subtract the original estimate from the time spent. Then either dump the response into a custom number field or flag the issue in some way. (Ex: add a label named "under-estimated" or "over-estimated") Then you can query/filter/report on the response, label, or whatever way you used to identify the issues you're looking for.
The smart tags (variables) you'll need to use are:
Here's the formula I used. Note: For math functions, prepend {{#=}} to open the calculation and append {{/}} to close it.
In this formula, I've converted both values to seconds, using "divide(3600)".
I created a simple (manual) automation, that just logs the result of the calculation, to test this idea. Here's what my super simple automation looks like:
Here's my sample Jira issue with an original estimate of 4 days and a worklog of 5 days. Note: Jira shows 5 days as 40h. (5d x 8h (my application's default) = 40h)
And there's the result showing the number written to the log.
In the above screenshot, the difference between 4d and 5d is "8" meaning and excess of 8 hours over the estimate. If there was a surplus of 1d, the result would show as "-8".
If this isn't what you're looking for, I hope it leads you to a final solution!
Rachel Wright
Author, Jira Strategy Admin Workbook
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your response.
This is what I'm exactly looking for, Can you help me with the configuration?
I want this to result in a custom field, How do I configure it can you please help?
Thanks in advance!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Woohoo! Glad to hear it @Sai kiran P .
Notes and considerations:
Automation rule specifics:
Here's how I set up my automation.
Here's the calculation I used: {{#=}}{{issue.timeSpent.divide(3600)}}-{{issue.original estimate.divide(3600)}}{{/}}
Here's what my completed rule looks like:
Additionally, I chose to post the calculated result to the log, just so I can check my math. The log action is is shown in the above screenshot and the result is shown in my Nov 29 message.
Hope this helps!
Rachel Wright
Author, Jira Strategy Admin Workbook
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.