Martin Edenhofer

@MrGeneration Is this issue still present? Or has it decreased/disappeared since Zammad 5.0?

For me the export of accounted time should stay in the admin interface, since the export is related to an admin / system sync task (export accounted time to transfer...

> > For me the export of accounted time should stay in the admin interface, since the export is related to an admin / system sync task (export accounted time...

Thanks for the summary. It's IMO 100% correct. > We could push something on websocket to make UI aware about this. E.g. show „You were inactive too long, please reload“...

> @martini But this is no new situation or? What exactly? The Issue with login already exists for a while. I just discovered it also for `authenticator app token screen`...

JFI: Currently its a standard behavior, if a ticket is closed, all online notifications are set to seen automatically. https://github.com/zammad/zammad/blob/develop/app/models/ticket.rb#L21C19-L21C45 -> https://github.com/zammad/zammad/blob/develop/app/models/ticket/sets_online_notification_seen.rb#L9 -> https://github.com/zammad/zammad/blob/develop/app/jobs/ticket_online_notification_seen_job.rb If this is not done for...

Related https://github.com/zammad/zammad/issues/4708, https://github.com/zammad/zammad/issues/4324

Solution proposal: Advantage of the new implementation: Works in all browsers (will fix https://github.com/zammad/zammad/issues/4708 and https://github.com/zammad/zammad/issues/4324 too). Change for users: Shortcuts also work without hotkeys (such as `ctrl+alt`) in the...

> Cannot render time in a different time zone than agent's browser is set to. For example, user may want to lock Zammad timezone to one's home time zone when...

> This should also work correctly when rendering dates on the back end side, e.g. in notification templates. Right now we use the system timezone (`timezone_default`) for rendering dates in...