Reply To: Default range selector buttons behave unintuitively

[efraga]

Hi Vishwas,

Thanks for the release to fix the YTD behavior. It is appreciated.

Unfortunately, I still can’t use the 1M, 3M, etc. buttons because their behavior can also be unexpected based on their limited description. Based on the labelling a user might equally expect “1 month from selected start date”, “1 month from selected end date”, “1 month from first reading”, or “1 month from last reading”. Only in reading the documentation will they find out which and this isn’t ideal.

Consequently, I will likely have to remove these buttons completely and implement my own.

I would propose instead that these buttons should read “last 1M”, “last 3M”, etc. and they should always give the last 1 month, 3 months etc. of data from the current date which would at least be more expected based on the new labelling.

You could equally change the label defaults to something like “1M before selected end date” and keep the existing behavior but I find this text a little long for a button. Maybe there could be a shorter way of saying the same thing but I can’t think of it at the moment.

Thanks again anyway for the release.

Regards,
Chris