Bug 343453 - Event viewer does not display timezone
Summary: Event viewer does not display timezone
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: timezones (show other bugs)
Version: 4.14.2
Platform: unspecified Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-28 12:38 UTC by Tim Ruffing
Modified: 2018-01-31 17:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Ruffing 2015-01-28 12:38:01 UTC
The event viewer (right click on event -> "Show...") does not offer a possibility to show the time as in an original calendar entry, i.e., as "time XX:YY in timezone Z".

This information is only shown in the "Edit" dialog. This is fine actually except for read-only calendars. For these calendars, there is just no way to access this information. I admit that the information itself is probably useful only in rare cases, but there should be some way to access it. 

I don't know how to integrate this best. Maybe something like a tooltip on the local time, which should still be displayed by default?

Reproducible: Always
Comment 1 Allen Winter 2015-03-08 00:56:03 UTC
I think it would be useful to have the ability to show the datetimes with the timezone contained in the calendar entry.  in the case where that timezone is different from the system timezone.

would make sense in the incidence viewer as well.

tooltips might be good enough, but yes I agree with this wish
Comment 2 Denis Kurz 2017-06-23 20:01:18 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-01-31 17:14:05 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.