Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #4983] Client timezone is not converted #1232

Closed
icinga-migration opened this issue Oct 31, 2013 · 4 comments
Closed

[dev.icinga.com #4983] Client timezone is not converted #1232

icinga-migration opened this issue Oct 31, 2013 · 4 comments
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/4983

Created by mhein on 2013-10-31 11:45:27 +00:00

Assignee: mfrosch
Status: Closed (closed on 2014-03-12 12:09:01 +00:00)
Target Version: 1.11
Last Update: 2014-03-12 12:09:01 +00:00 (in Redmine)

Icinga Version: 1.10.0
Icinga Web Version: 1.10.0
IDO Version: 1.10.0
OS Version: Linux
DB Type: MySQL
DB Version: 5.6.13
Browser Version: Chrome 28.0

As a user I want to use system timezone to send commands.

At present JS date input fields are display client timezone and not the system one. This leads into different states when commands are executed in icinga.

Changesets

2013-11-20 14:34:52 +00:00 by elippmann d10f0b7

Command forms: Display date/time fields as UTC

fixes #4983

2013-12-09 15:46:04 +00:00 by elippmann 9f30a09

Command forms: Display date/time fields as UTC

fixes #4983

Relations:

@icinga-migration
Copy link
Author

Updated by elippmann on 2013-11-20 14:11:06 +00:00

  • Status changed from New to Assigned
  • Assigned to set to elippmann

@icinga-migration
Copy link
Author

Updated by elippmann on 2013-11-20 14:35:43 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset d10f0b7.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-03-12 12:07:37 +00:00

  • Status changed from Resolved to Assigned
  • Assigned to changed from elippmann to mfrosch
  • Target Version changed from 1.10.1 to 1.11

Various users report this behaviour being broken. We should check this before 1.11 release, I'll investigate later on this too.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-03-12 12:09:01 +00:00

  • Status changed from Assigned to Closed

Sorry, #5713 is the current issue for further discussions.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant