[estimate] Add accumulators
Activity
Show:

Laurent NonnenmacherJuly 7, 2021 at 4:27 PM
Ça serait bien qu’on puisse dans le futur avec une grammaire de formules, genre COUNT(*) ou COUNT(@property = value) ou AVG(@Estimate, @Estimate\ \Max\)). C’est sûr que tu pourrais stocker juste SUM/MIN/MAX/AVG, mais si tu as envie d’inventer une grammaire, peut-être devrais-tu déjà stocker SUM(*), …
Adrien RagotJuly 7, 2021 at 4:23 PM
We should implement SUM/MIN/MAX/AVG/COUNT / - (“-” displays a blank field), even for the MVP,
We should always calculate in Java,
The calculation should run on the property, up to .getGlobalLimit(), and if there are more results, return an error (Preferably return a structured result, with both the result + the error message).
Resolved
Details
Details
Assignee

Reporter

Sprint
None
Story Points
5
Components
Requirement Yogi
Linked requirements
Requirement Yogi
Linked requirements
Created June 7, 2021 at 3:10 PM
Updated December 21, 2021 at 11:48 AM
Resolved August 17, 2021 at 3:30 PM
In the Estimate table
Add the possibility to sum the estimate.
Use the config wheel icon to add an extra line "Sum Total" which adds a line after all the requirements → No, the line is always present, and the “configure” allows to select between sum/avg/min/max/count/counta. 1 icon for each total.
This line displays a readonly line with the Sum of the Estimated avg and Estimated max.
This line has a different background color
It seems that Requirements are alphabetically sorted and sorting is not available.
Only support SUM accumulator (not avg, not min, not max, nothing else) → Is it for the MVP? If so, ok, but then, don’t display the config icon.
Precisions:
the last line with the Total SUM is always displayed in Estimate screen (and the content is configurable after)
the sum all of items in the column (except strings)
the total is not saved saved in database and is calculated real time (java)
The total is not refreshed on every ‘blur’ but with a refresh button (and put a visual indicator, like the save button when a matrix is modified)
In this story:
change DB structure to not override INLINE/EXTERNAL, but same DBPropertyName for same DBProperty.property
Search with externaproperty@Estimate vs @Estimate to search EXTERNAL or INLINE (and there is no fallback, and remove the start * if EXTERNAL - but need to see how to distinguish types)
Change the freeze baseline to only include INLINE