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

Target Start and End fields are exported with timezone shift

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

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 8.16.0
    • None
    • Plan
    • None

      Portolio's Target Start and Target End fields can be added to a JQL search. When exporting the search to a CSV file, both fields are exported in a timestamp format (i.e. 27/Sep/18 12:00 AM) using the system date field of Jira. However, both fields are date-only fields in the UI (the user doesn't have the option to pick the time, only the date).

      In other words, the UI shows the date as UTC (date only) and exports it as the system timezone used by Jira (as date-time). This shifts the date into the previous day and causes confusion. 

       

      JQL Of Portfolio Dates

      CSV Export

      Issue key,Issue id,Parent id,Status,Created,Updated,Custom field (rm.jpo.plan.common.baselineStart),Custom field (rm.jpo.plan.common.baselineEnd)
      
      ANDY-3,10102,,To Do,11/Jun/19 12:57 PM,11/Jun/19 1:54 PM,17/Jun/19 7:00 PM,30/Jun/19 7:00 PM
      ANDY-2,10101,,To Do,11/Jun/19 12:57 PM,11/Jun/19 1:54 PM,17/Jun/19 7:00 PM,30/Jun/19 7:00 PM
      ANDY-1,10100,,To Do,11/Jun/19 12:57 PM,11/Jun/19 1:54 PM,17/Jun/19 7:00 PM,30/Jun/19 7:00 PM

      In this specific example, Central Daylight Time (CDT) is 5 hours behind of Universal Time Coordinated (UTC), so the export is 5 hours behind, changing the date that is displayed in the UI and causing confusion.

       

      Expected behaviour.
      Only the date field should be exported to CSV without any shifts in hours/timezones.

            [JPOSERVER-2418] Target Start and End fields are exported with timezone shift

            Has this bug been fixed? I see it was closed out in March but do not see what the solution was. Still impacting our instance on 3.29.7. 

            Daniel Gould added a comment - Has this bug been fixed? I see it was closed out in March but do not see what the solution was. Still impacting our instance on 3.29.7. 

            This issue is also being tracked heavily under JPOSERVER-2358

            It affects exports and imports via the REST API as well as CSV exports.

            Jeffrey Thornsen added a comment - This issue is also being tracked heavily under JPOSERVER-2358 It affects exports and imports via the REST API as well as CSV exports.

            Benoit added a comment - - edited

            Great! Is it possible to change those field into a real date and time? It will be quite usefull for automation add on to add business days and hours cumulation

            Thanks

            Benoit added a comment - - edited Great! Is it possible to change those field into a real date and time? It will be quite usefull for automation add on to add business days and hours cumulation Thanks

            Was able to reproduce this on 3.29.2. Reopening the ticket.

            Mendel Liang added a comment - Was able to reproduce this on 3.29.2. Reopening the ticket.

            Benoit added a comment -

            This can be reproduced if you simply add a 1/2 day to the end date. it brings it back to one day before.

            Benoit added a comment - This can be reproduced if you simply add a 1/2 day to the end date. it brings it back to one day before.

            Hi all,

            We tried and could not reproduce the bug with timezone shifts after exporting the fields to a CSV file in the Jira issue navigator.

            If you are affected by this bug, please upgrade to the latest version of Advanced Roadmaps (3.29.0 at the time of writing).

            As a side note, date fields are exported in a timestamp format (i.e. 27/Sep/18 12:00 AM) since they use the system date field of Jira, so this works as expected.

            Best regards,

            Quentin

            Quentin Feyaerts added a comment - Hi all, We tried and could not reproduce the bug with timezone shifts after exporting the fields to a CSV file in the Jira issue navigator . If you are affected by this bug, please upgrade to the latest version of Advanced Roadmaps ( 3.29.0 at the time of writing). As a side note, date fields are exported in a timestamp format (i.e. 27/Sep/18 12:00 AM) since they use the system date field of Jira, so this works as expected. Best regards, Quentin

            Inadmissível esse tipo erro, pois tudo nosso planejamento é em cima dessas datas alvos.

            Ellen Cristina Gouveia added a comment - Inadmissível esse tipo erro, pois tudo nosso planejamento é em cima dessas datas alvos.

              1470b7239af3 Drew Zhu
              astegani Alex Stegani
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: