Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Done
-
prod/bigpicture-jiracloud-2019-04-26, prod/biggantt-jiracloud-2019-04-26, prod/bigpicture/jiraserver/2020/11/20/8.0.12, prod/biggantt/jiraserver/2020/11/20/8.0.12
-
None
-
Tree
-
BigPicture, BigGantt
-
JIRA server, JIRA cloud
-
5
-
-
Sprint 2019/11, Sprint 2019/12, Sprint 2019/13, Sprint 2019/14
-
61 weeks, 3 days, 22 hours, 35 minutes, 10 seconds -
0 -
0 -
0 -
0 -
0 -
0 -
Description
Prerequisities:
Prepare instance with clean mysql database
**
- The issue also occurs on Cloud, but it is impossible to check server's time zone there (although it is suspected to be UTC+0)
- Time zone is affected by DST
Reproduction steps (for Server apps):
- Open Jira and navigate to Jira administration -> System -> System info
- Note the server's time zone set in System Time
- Set your PC's time zone to earlier than or equal to the server's: for example GTM +1 [Warsaw]
- Open any Program in BigPicture/BigGantt
- Proceed to Gantt module
- Create a new artificial task with any date
- Set your PC's time zone to later than server's: for example GTM -3 [Brasil]
- Create another artificial task with any date
- Change duration of second artifial task to one day longer or one day shorter
Actual result:
The second artificial task after resizing/shortening is moved one day to the past.
Expected result:
Both artificial tasks are created on the selected days.
Workaround
N/A
Attachments
Issue Links
- is duplicated by
-
ONE-29142 Period of just created basic task is shifted by one day
-
- Closed
-