Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Hierarchy leafWiki
You are here:
  • Forums
  • Development

Content

Project Activity Report - Incorrect time reference.

Added by Mike Lewis almost 7 years ago

Using OP 5.0.11. Just noticed while looking at a projects activity that there is an incorrect time reference. See screenshot attached. Note the current date and time on my system clock (8:46 AM of Jan. 29, 2016). Note the items under “Today” are tagged for 19:23… about 11 hours into the future, according to my system time. These entries should be placed with the activities on January 28. Obviously, this is a timezone issue and the system is not completely processing the appropriate date based on the user’s timezone. (The time is right, as this user, Brian, does most of his work in the evening.) My guess is the date is being processed off UTC+0, or something close to that.

User Brian Oxee works in US Eastern Time (UTC –5)
User Mike Lewis (me) works in US Mountain Time (UTC –7). The screen shot is referenced on US Mountain Time.

If Brian did indeed log his hours at Jan. 28 19:23 UTC –7, WET (UTC+0) would have been Jan. 29 02:23, CET (UTC+1) would have been Jan. 29 03:23.
(Even if Brian logged his hours at 19:23 UTC –5, WET and CET would still already be Jan. 29 00:23 and Jan. 29 01:23 respectively.)

Not sure if there is already a work package opened on this (couldn’t find any in a quick search). Just thought I’d bring it to attention if it hasn’t already.

Wrong time reference in activity report.


Replies (5)

RE: Project Activity Report - Incorrect time reference. - Added by Robin Wagner almost 7 years ago

Hi Mike,

thanks for your post.
Could you check if the time zone in your account settings (User name > My account > Settings) has been set correctly?
The chosen time zone is not based on your system settings but on the settings chosen in OpenProject.
If no time zone is chosen, the time zone defaults to GMT+0 / UTC+0.

Best,
Robin

RE: Project Activity Report - Incorrect time reference. - Added by Mike Lewis almost 7 years ago

Hi Robin,

Just double checked and confirmed that my timezone setting is already set for Mountain Time (US & Canada) (GMT/UTC –7), Brian’s is already set for Eastern Time (US & Canada) (GMT/UTC –5). I believe the time is right, it’s just not on the right day. That is why it looks odd in my previous screen shot that the activity was logged “Today at 19:23” when 19:23 hadn’t even happened (for me, or anyone) yet.

Attached is an updated screen shot. Notice there is additional activity for January 29th that appears above the entries Brian had made. (Activity is listed most recent at the top, so look carefully at the times as you move down.) Brian’s entries should be associated with January 28th. I have confirmed this by looking in a Cost Report for his logged hours, which reports that line item as the 28th, not 29th.

Activity entries sorted most recent at top. Note how there are three entries tagged "19:23" at the bottom ("start") of January 29. These should be grouped with Jan. 28.

Normally we won’t see this because most times our activity is logged between the hours of 07:30 GMT/UTC –7 and 16:00 GMT/UTC –7, at which point GMT/UTC +0 will have not yet crossed the midnight meridian, thus still within the same date. Brian, on the other hand, does most of his work for us in the late evening in the Eastern US, which would mean that GMT/UTC will have already passed midnight.

I can understand how this would not have been detected by someone testing this if their timezone was set same as (or very close to) UTC/GMT +0.

Thanks for looking into this,

- Mike

RE: Project Activity Report - Incorrect time reference. - Added by Robin Wagner almost 7 years ago

Hi Mike,

thanks for your detailed response.
You’re right: I could reproduce the behavior: The day displayed in the activity seems to be based on the date UTC+0.
We didn’t encounter this error before since we’re close to UTC+0 (UTC+1).

I opened a bug report to track this issue:

Thanks for reporting this issue.

Best,
Robin

RE: Project Activity Report - Incorrect time reference. - Added by Oliver Günther almost 7 years ago

Hey Mike,

I believe I found and fixed the underlying issue. The activity times should be correct (or rather, I could not provoke invalid times using extreme time zones), but the grouping of activities in specific dates were performed using UTC time,
while the content of that group may contain several dates in the user’s time zone.

The fix is likely being published in the next patch release (5.0.15).
If that should not solve the problem, please report back in the tracking work package

Many thanks for your thorough analysis and report!

Best,
Oliver

RE: Project Activity Report - Incorrect time reference. - Added by Ben Bornemann almost 6 years ago

Dear all,

Experiencing the below described issue, I have looked for a general “system” time-zone but found no such setting.
I am using OpenProject 6.1.3 (Mysql2) and am experiencing an issue that is very similar to the one in this thread:

Setup:

  • Server and all users work in UTC+1

Actual behaviour

  1. System notifications, sent to the user from the email address openproject@[ourserver.com] state a time 2-3 hours in the future.
  2. When activities / time spent is displayed by date, work performed in the late evening is grouped to the next day.

Expected behaviour

  1. System notifications, sent to the user from the email address openproject@[ourserver.com] should state the time at which the activity, e.g. a work-package update was actually performed.
  2. Activities / time spent should be grouped to the date on which it was actually performed

Best regards,

Ben

  • (1 - 5/5)
Loading...