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
Thanks! But I'm not sure that tying it into "reporting period" was really a good idea. Because what's for example a "1 year" reporting period as typical configured in dashboard? It's a period ending today and starting 365 days ago. In full accordance with that, the widget after you changes shows:
either events starting from 2024-01-12 (sorting direction: ascending)
or, events up to today, in descending order (sorting direction: descending)
First of the above is rather specialized and not very useful info, 2nd is more or less useful (assuming a user doesn't look at dashboard every day and want to know what they missed over the last few days). But the most useful info is upcoming events (ex-dividends, earnings releases all affect the share price and thus investment decisions), and that's exactly what "reporting period" widget can't show right away. If you look at the previous "event widget patch", then it apparently also was tied into reporting period, you can tell that by the fact that there were workarounds applied against the issue as described above: Fix current month and current year reporting period interval to include
dates in the future .
Apparently, the idea was to switch to "current month/year" reporting period specifically for the event list widget (away from "a period in the past" as normal for the entire dashboard). But that would still lead to problems on the period edges, like it wouldn't show events across a year transition like we just had.
But why all that? "Securities: Date reached" aka FollowUpWidget worked perfectly with it's "date in the future" vs "date in the past" setting, IMHO events shouldn't be tied into "reporting periods". (Reporting periods are to study performance across different timeframes, while events and not performance-related (at least per se)).
The text was updated successfully, but these errors were encountered:
This ticket is to capture discussion from #4431 , now closed, so it's not lost.
@pfalcon wrote in #4431 (comment)
Thanks! But I'm not sure that tying it into "reporting period" was really a good idea. Because what's for example a "1 year" reporting period as typical configured in dashboard? It's a period ending today and starting 365 days ago. In full accordance with that, the widget after you changes shows:
First of the above is rather specialized and not very useful info, 2nd is more or less useful (assuming a user doesn't look at dashboard every day and want to know what they missed over the last few days). But the most useful info is upcoming events (ex-dividends, earnings releases all affect the share price and thus investment decisions), and that's exactly what "reporting period" widget can't show right away. If you look at the previous "event widget patch", then it apparently also was tied into reporting period, you can tell that by the fact that there were workarounds applied against the issue as described above: Fix current month and current year reporting period interval to include
dates in the future .
Apparently, the idea was to switch to "current month/year" reporting period specifically for the event list widget (away from "a period in the past" as normal for the entire dashboard). But that would still lead to problems on the period edges, like it wouldn't show events across a year transition like we just had.
But why all that? "Securities: Date reached" aka FollowUpWidget worked perfectly with it's "date in the future" vs "date in the past" setting, IMHO events shouldn't be tied into "reporting periods". (Reporting periods are to study performance across different timeframes, while events and not performance-related (at least per se)).
The text was updated successfully, but these errors were encountered: