Is it possible to sum up all estimates (original and remaining) for a particular role that match a JQL query using the ScriptRunner aggregateExpression? For example the following JQL query returns the original and remaining estimates for the project:
project = LOAD and issueFunction in aggregateExpression("Total Estimate for all Issues", "originalEstimate.sum()", "Remaining work", "remainingEstimate.sum()")
How to reference the original and remaining estimate values in the time tracking by roles field to be summed up?
Alternatively, is there another way to achieve the described functionality (aggregate the total estimated / remaining work in the estimate by role fields)?
Hi Vedran, unfortunately due to the way that the aggregateExpression supplied by Script Runner works it cannot be used to sum up the values stored in the Project Role specific estimations.
However, you can use the Reports (Estimates Report By Roles) supplied with our plugin to achieve this. In the latest version we added the ability to filter the report issues via an existing JQL filter.
Note that if upgrading to a new version of the plugin from an old version the JIRA server may need to be restarted in order to see this new JQL option when generating a report. (This is a requirement on JIRA's side as it caches the report configuration pages).
Let me know if the above does not solve your requirements & we can work on adding additional features if possible.
Thank you Steven, I just noticed that the functionality to include a JQL filter in the report, that should suffice. I do have one more question however - in your documentation (page 26 of 1.0.7 document) it states:
The issues overall Original / Remaining estimates will be a total of all Project Role Specific estimates.
However, in my experience if the original estimate (the JIRA system field) is not set manually, it will not have an aggregate value of all Project Role estimates; instead its value will be blank (null). I would like to have the aggregate value of all per-role estimates in the "main" original estimate field. How can this be achieved?
Hi Vedran, the plugin should already be automatically calculating and updating the Systems built in original estimate value. However this will only occur if you use the plugins Custom fields for specifying your role specific estimates & logging time.
There are two main Custom Fields that do this for you:
Time Tracking (By Roles)
Log Work (By Roles)
It is suggested that in your screens you remove the built in Original / Remaining estimates for the projects that you wish to use the Role specific estimates for as adjusting those values will cause the issues role specific estimates to be out of sync with the issues overall original / remaining values. When this occurs the plugin will default back to using the issues single value for original / remaining.
If you have all this configured & changing Original / Remaining values via the Time Tracking (By Roles) or via the Log Work (By Roles) Custom Field is not updating the issues original estimate value (the system one) then something is not working correctly for you.
I am updating the estimates via TIme Tracking (by Roles) field, and this does NOT get reflected in the system Original Estimate (part of the Time Tracking) field. The system Original Estimate is left blank (null) regardless of any updates to Original Estimate (part of the Time Tracking by Roles).
What can be done to troubleshoot this?
Just to add - after logging work, it seems that the system original/remaining estimate fields get populated. However, before any work is logged, the system fields remain blank.
Hi Atlassian Community! This is Teresa from the Jira Service Desk team. On June 19th, I’ll be hosting a webinar “Asset Management: The Role of Context in ITSM” with Atlassian Partne...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events