Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-2459

Target start/end field depends on system user timezone

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 2.18.0, 2.27.0, 3.6.0
    • Historical
    • None

      Summary

      Target start/end fields are stored incorrectly on the Issue history.

      Environment

      • user.timezone set to any "western" timezone (eg. America/Sao_Paulo)

      Steps to Reproduce

      1. Set a Target end value
      2. Verify Issue history

      Expected Results

      Issue history displays the same value specified

      Actual Results

      Issue history displays the day before the date specified

      Solution / Workaround

      1. Set system user timezone to UTC at Jira JVM properties
        -Duser.timezone=Etc/UTC
        • Note that different user and system timezones can result in the behavior described in JRASERVER-41646
      2. Restart Jira

            [JPOSERVER-2459] Target start/end field depends on system user timezone

            Stasiu added a comment -

            Dear all,

            I would like to inform you that the Jira DC Development team has reviewed the following issues: JSWSERVER-21994 and JPOSERVER-2459. After careful consideration, we have determined that they describe the same issue. Therefore, all issues will be merged into JSWSERVER-21994, while the other issues will be closed. If you would like to keep track of the problem, please vote and watch JSWSERVER-21994.

            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Daniel Dudziak
            Jira DC Senior Software Engineer

            Stasiu added a comment - Dear all, I would like to inform you that the Jira DC Development team has reviewed the following issues: JSWSERVER-21994 and JPOSERVER-2459 . After careful consideration, we have determined that they describe the same issue. Therefore, all issues will be merged into JSWSERVER-21994 , while the other issues will be closed. If you would like to keep track of the problem, please vote and watch JSWSERVER-21994 . Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Daniel Dudziak Jira DC Senior Software Engineer

            The underlying issue with Target Start and Target End date are tracked in https://jira.atlassian.com/browse/JPOSERVER-2358

            Please follow that issue for any further updates.

            Benjamin Morgan (Inactive) added a comment - The underlying issue with Target Start and Target End date are tracked in https://jira.atlassian.com/browse/JPOSERVER-2358 Please follow that issue for any further updates.

            We are experiencing the same problem with multiple date fields in Jira 8.0.3 w/ Portfolio for Jira 2.27.0. 

            SMAtlassianMber added a comment - We are experiencing the same problem with multiple date fields in Jira 8.0.3 w/ Portfolio for Jira 2.27.0. 

            Omar Rashid added a comment - - edited

            Warning - Apply the work around listed in this bug will expose the linked bug here which will offset your releases date in Jira by -1d if your system and user time zones end up being different post fix..

             

            https://jira.atlassian.com/browse/JRASERVER-41646

            Omar Rashid added a comment - - edited Warning - Apply the work around listed in this bug will expose the linked bug here which will offset your releases date in Jira by -1d if your system and user time zones end up being different post fix..   https://jira.atlassian.com/browse/JRASERVER-41646

              Unassigned Unassigned
              malmeida Marcus Silveira
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: