Reset travel statistics after Klimaticket is renewed

[Crazyphil]

Currently, it seems that the travel journal simply keeps counting up the ticket prices in the travel statistics and with it the Klimaticket gains. However, these gains should be reset every time the Klimaticket is renewed, because then the price of the ticket has to be gained again as well.

The information about when the Klimaticket is renewed is already there in the profile (given that for the ticket no bonus months or other shenanigans are added). There could also be another page where one can compare the statistics for different validity periods instead of just the current period.

[Dosenpfand]

My current use-case looks like this: I set the "Klimaticket start date" in my profile to the start date of my current ticket. That way the "Statistics" and the "Current" travel journal tab should only account for trips with date > that start date. This has the advantage of supporting special extended tickets (but i guess these are anyway not coming back) and gaps in my ticket if i don't immediately renew it. Of course it has the disadvantages of needing to set this ~ once a year and only having a single archive that are not split up by individual past tickets.

I guess we could support both my and your use case by automatically making the current start date of the ticket the start day + month of the profile + the year that this date last occurred in. E.g. if the ticket start date in your profile is 2021-12-20 and the current date is 2023-12-12-04, then the calculated start date will be 2022-12-20.

Would that work for you?

Statistics and archives per year could then also be added.

[Crazyphil]

Actually, simply setting a new start date manually would be a perfectly acceptable workaround for me. I didn't think of this (and thought that there might be data loss), and there is a high chance that one is reminded to change the date as soon as the statistics don't make sense anymore. If the start date changes automatically after a year, this is just an added bonus.

For historical statistics, one could also simply add multiple validity date ranges to the profile, so instead of using a single text field, each Klimaticket purchase is an additional entry in the database. This would also foresee eventual price increases for the ticket, which would need to be considered in those historical statistics.