You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 9, 2021. It is now read-only.
Different metric types do not necessarily need a range of time. For instance, metrics that are simple counts of something only involve a single point in time.
We should make it so that the time period is not a required field for cards. The period field should still be passed to the Service methods, if it's provided.
The text was updated successfully, but these errors were encountered:
Different metric types do not necessarily need a range of time. For
instance, metrics that are simple counts of something only involve a single
point in time.
We should make it so that the time period is not a require field for
cards. The period field should still be passed to the Service methods, if
it's provided.
Yes, we still require an effective date parameter for the card. What we're not requiring is the time period parameter.
In the current metrics, the time period parameter is set to 30 days. This makes sense for calculating "the percentage of reports that are responded to on time". More precisely, it is:
The percentage of reports [submitted within 30 days]
Within 30 days of what? Now? Yesterday? October 17th?
The percentage of reports - submitted up to 30 days before some arbitrary effective date.
All metrics are going to require support for an effective date declaration. Its this day range declaration that should be optional.
Different metric types do not necessarily need a range of time. For instance, metrics that are simple counts of something only involve a single point in time.
We should make it so that the time period is not a required field for cards. The period field should still be passed to the Service methods, if it's provided.
The text was updated successfully, but these errors were encountered: