It's all about the answers!

Ask a question

Report Builder: Inconsistent Data - Planned Work vs Actual Work


Alick Banda (43111) | asked Jun 06 '18, 11:02 a.m.
retagged Jun 07 '18, 9:04 a.m. by Jackie Albert (1.6k14444)

 Good day,


We have picked up a couple of issues with regards to Report Builder 6.0.4, and how the time values (Planned Work, and Actual Work) are returned when a query/report is run.

In the scenario, we would like to compare the amount of time estimated for tasks, against the actual time taken.

Issue 1: Conversion of Planned Work, and Actual Work to Hours: Using the Custom Expression option, an attempt to convert the time allocated (Estimated/Actual) from seconds to hours using ($Tasks:Actual Work$/(60*60)) or $Tasks:Actual Work$/3600. If the value estimated is for 1800 (the expected value is 0.5), Report Builder returns 0 (or 0.00 if you show the result as decimal). 

Issue 2: Estimation on the task does not show the same values as report. For Example, the task has the following attributes filled in as follows:
- Estimate : 5 hours
- Correction: 4 hours
- Time remaining: 4 hours
The report when run in Report Builder shows the following values:
- Planned Work : 14,400 (in seconds) or 4 hours
- Actual Work: 0 
Could someone please guide me on the mappings of Estimation, and Correction in a task, to the attributes used in the actual report? and why is the report showing 4 hours in the report, instead of 5 hours?

Issue 3: Drill Downs of Reports: So, after the report has been generated, a Grouped Bar Graph is used to present the data that is returned, showing a bar with Estimates, and a bar with "Actuals". Both bars show that there are values that have been returned, but when drilling into the bar with "actuals", the table shows 0s (zeros), and when all "Actual" values are added from the table for example, the sum does not give the same result as that shown in the graph.

We have recreated these reports multiple times, and we seem to get the same inconsistencies across the various project areas reported against.

Could this be a known issue, a bug, or something we are missing?

Thank you.

Alick

One answer



permanent link
Ralph Schoon (55.1k23642) | answered Jun 06 '18, 11:44 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Jun 06 '18, 11:52 a.m.
Issue 2: Estimation on the task does not show the same values as report. For Example, the task has the following attributes filled in as follows:
- Estimate : 5 hours
- Correction: 4 hours
- Time remaining: 4 hours

The estimated value is in "Estimate" or in "Correction" if the latter has been set. The Correction overwrites the Estimate and the old estimate value is documentation only, as it can not be changed if a correction has been set.

So the estimated work is 4 hours and since there are still 4 hours remaining, no work has been done and the calculation is correct.

Comments
1
Alick Banda commented Jun 07 '18, 8:32 a.m.

 Hi Ralph,


Thank you for your response.

We have a use case to compare, or rather evaluate our team's estimation accuracy using the data entered in the Jazz solution. Could you please guide on:
1. Reporting on the value of the Estimation 
2. Reporting on the actual time spent.

Thank you.

Alick

Your answer


Register or to post your answer.