- attached Time Sheet Sun.png
In Time Sheet, "Lock time frame" is locking 1 day before the picked date in pop-up calendar
Only if picked day is from Tue to Sat. If picked day is Sun, it locks 1 day after.
Env: latest Chrome Windows 7 Pro 64-bit JIRA 6.3.4
Comments (26)
-
Account Deleted -
Account Deleted - edited description
-
Hi Lucas,
Could you please check whether your JIRA Profile Timezone corresponds to your actual timezone (browser)?
Thank you.
-
Account Deleted From JIRA Profile: "Time Zone: JIRA default (GMT-03:00) Sao Paulo", which is the same as the computer. I tried reverting daylight saving setting and still no luck. Reproduced in IE, anonymous Chrome tab and Firefox in Ubuntu, same behavior.
Looks like there is a "skip weekends" mechanism which is not working correctly:
- (Picked - Selected)
- Mon - Mon
- Tue - Mon
- Wed - Tue
- Thu - Wed
- Fri - Thu
- Sat - Fri
- Sun - Mon
-
Oh, so if you enable Show Weekends option, it is working fine?
-
Account Deleted Found the problem. If JIRA timezone is less than GMT+0, you're considering the day before, probably because date picker returns "11/16/2015 00:00" then adds timezone, becoming "10/16/2015 22:00" (assuming GMT-2). Possible solution: add 12h to the date picker value.
"Show Weekends = No" is working fine, it skips days with no log entry, this is why my table above skips some days.
-
I will check it.
But I don't understand your comment about "skip weekends" mechanism.
-
Account Deleted Just ignore it. I was trying to reverse engineer the bug. My confusion was because if "Show Weekends = No" it still shows weekends with work log, and this is fine.
FYI, this bug is minor. Issue
#716is top priority for us. -
Account Deleted Amending the comment above: "Found the problem. If JIRA timezone is less than GMT+0, you're considering the day before, probably because date picker returns "11/16/2015 00:00" then adds timezone, becoming "11/15/2015 22:00" (assuming GMT-2)."
-
- changed status to resolved
fix issue
#721: ignore time part for lock date→ <<cset a64912881a7f>>
-
Version 2.9.3.5 is available with the fix.
-
Account Deleted - changed status to open
This issue is back in version 2.9.3.8, still related to timezone.
If JIRA timezone is less than GMT+0, the day before is picked.
-
Account Deleted -
assigned issue to
-
assigned issue to
-
Hi Lucas,
I've tried with GMT-3 Sao Paulo and it's working properly. Could you please check using browser Developer Tools what does the following request look like in your case? It should containg startDate date only with no time part, e.g.: http://localhost:2990/jira/rest/timesheet-gadget/1.0/timesheet.json?baseUrl=http%3A%2F%2Flocalhost%3A2990%2Fjira&gadgetTitle=&startDate=2016-01-11&...
Thank you.
-
Account Deleted Andriy, I'm not sure how to reach this request, could you give more info?
Update: changing timezone did not solve the issue, which makes me think it can be something else. Resetting jira.date.picker. and jira.date.time.picker. did not solve it either.
-
Hi Lucas,
Using browser Developer Tools, in Network tab, there should be listed requests performed when you select lock date. One of them should be /timesheet.json, that I'm interested in.
Thank you.
-
Account Deleted Got it. There is something odd between the click and the request.
Clicking 13-01-2016: http://jira/rest/timesheet-gadget/1.0/timesheet.json?baseUrl=http%3A%2F%2Fjira&gadgetTitle=&startDate=2016-01-12&targetUser=&targetGroup=&collapseFieldGroups=false&excludeTargetGroup=&numOfWeeks=1&reportingDay=&projectOrFilter=&projectid=&filterid=&projectRoleId=&weekends=false&showDetails=true&sumSubTasks=false&showEmptyRows=false&groupByField=&moreFields=&offset=0&monthView=false&sum=day&_=1452701829664
In the case above the Element for the pop-up calender shows: <td class="day day-13 today">13</td>
-
Hi Locas,
I can reproduce it if my computer timezone does not correspond to JIRA timezone. But JIRA notifies me about it with message like: Your computer's time zone does not appear to match your JIRA time zone preference of (GMT+01:00) Prague.
Can it be the case?
Thank you.
-
Account Deleted Andriy, not exactly. I could reproduce it now, it has to do only with the computer timezone. JIRA timezone does not matter, JIRA notification message is also not relevant.
In short: if computer timezone is less than GMT+0, the issue happens. It looks like the time part of lock date is not being ignored.
-
Ah, right, I see it now, thank you for your help, will be fixed soon!
-
- changed status to resolved
really fix issue
#721: do not over complicate it - use date string from calendar→ <<cset 149b8a35ad32>>
-
-
Account Deleted Verified, issue is resolved.
-
Great, thank you for confirmation!
-
- removed version
Removing version: 2.9 (automated comment)
-
- removed component
Removing component: Time Sheet report and gadget (automated comment)
- Log in to comment