Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Started at" field on test run is one hour behind the real execution start time #1206

Closed
shadeimi opened this issue Nov 14, 2019 · 0 comments

Comments

@shadeimi
Copy link
Contributor

shadeimi commented Nov 14, 2019

Description of problem

"Started at" field on test run is one hour behind the real execution start time

Version or commit hash (if applicable)

7.1

Steps to Reproduce

  1. Create a new test run using the xml-rpc api, invoking the TestRun.update method to close it
  2. Verify that the Start date is one hour behind
  3. Verify that the End date is correct

Actual results

Start date is one hour behind

Expected results

Start date is correct

Additional info (Python traceback, logs, etc.)

atodorov added a commit that referenced this issue Nov 25, 2019
by default Kiwi TCMS is configured for UTC time and this is
confusing some users. All timestamps are displayed according to
configured timezone.
atodorov added a commit that referenced this issue Nov 25, 2019
all of these settings can be customized by the administrator
running Kiwi TCMS. The only thing we can't easily do is display
the data in different time zones when hosting an application for
geographically dispersed team. For this reason the previous commit
displays the server time in the navigation bar.
atodorov added a commit that referenced this issue Nov 25, 2019
by default Kiwi TCMS is configured for UTC time and this is
confusing some users. All timestamps are displayed according to
configured timezone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant