Doing list calculation on a calculated field of type "duration" shows incorrect result. - Known Error

Doing list calculation on a calculated field of type "duration" shows incorrect result. Description Doing list calculation on a field of type "duration" which contains calculation in its the dictionary shows incorrect result.

Steps to Reproduce

1. Go to any incident form 2. Create a new field called "duration test" of the type "duration". 3. Configure the dictionary entry of "duration test" to include the attribute "max_unit=minutes" 4. Enter some values in the "duration test" field for two incident record for testing purposes. 5. Go to the incident list and do a list calculation (average, total etc) on the "duration test" column. 6. Note the result 7. Now go to the dictionary entry of "duration test" and make it a calculated field. Use a script that produces a different value from the value in step 4. 8. Now go to the incident list and reload the list

Expected behaviour: The result of the calculation will change to reflect the new values

Actual behaviour: We see that the result is calculated using the old values of the records, and not the values from the calculated field script.

Workaround This is expected behavior and by design in all currently supported releases.

Calculated fields do not update the DB until the record itself is updated. The list will still display the calculated values, but will use the stored DB values for calculations. You'll see a change in behavior if you 'saved' the records you're using in the example.

Regardless, this isn't valid because the calculated field isn't updating the DB, so there is nothing to calculate. We don't support calculating calculations.