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
I suggest to add the ability to sort by the maximum metric found in any of the stacks concerened.
There is already an average and a sum, including percentages, so I presume this request is in accordance with the guidelines.
I am analyzing a sort of "non-cumulative" metric, blocked time per occurrence. Since the total is heavily influenced by what the user actually did and how often, I cannot really use that. The average works in general, but hides the biggest problems. The maxium, in my case, is the user's worst observed case which is what I'm out for.
The text was updated successfully, but these errors were encountered:
This is interesting. It is not obvious to me how to do this in a way that is both easy to implement and easy both users that care about the feature and those that don't. It seems like doing this in a way that is intuitive requires the ability to configure columns, which is non-trivial work.
It is worth thinking about, but if the feature becomes non-trivial we would want some thumbs up reactions from the community before investing (as well as someone willing to invest in it).
I suggest to add the ability to sort by the maximum metric found in any of the stacks concerened.
There is already an average and a sum, including percentages, so I presume this request is in accordance with the guidelines.
I am analyzing a sort of "non-cumulative" metric, blocked time per occurrence. Since the total is heavily influenced by what the user actually did and how often, I cannot really use that. The average works in general, but hides the biggest problems. The maxium, in my case, is the user's worst observed case which is what I'm out for.
The text was updated successfully, but these errors were encountered: