Calendar day picker selects the day before the one I choose

[Iago Docando]

I'm trying to add the festivities for 2020 to my normal calendar in Service Desk but even though I'm seeing the correct date selected in the box, it is registrered as the prior date whenever I click on the "Add" button.

I'm pretty puzzled. Of course I've resorted to simply select one day later than the day I actually want but I was hoping that maybe someone has encountered this behaviour before and already has a better solution ready to share...

Thanks in advance :)

EDITED: In my experience doing this, once populating every festivity and testing a couple of extra test dates, it has never failed for the 1st of january and a couple of times it has worked as intended. Honestly... it would be better if the behaviour would have been allways the same, even if wrong.

[Petter Gonçalves]

Hello @Iago Docando

Thank you for reaching out.

Per your description, I believe that when you add a holiday to the calendar related to your Service Desk SLAs, your SLA panel adds an extra day to the "within" and "remaining" time. Is that correct?

I believe you might be facing the following bug:

- SLA panel adds an extra day to the "within" and "remaining" time if there is a holiday in the calendar 

Feel free to vote and watch the bug to increase its priority and also receive notifications about any updates.

As a workaround, you may disable the improved SLA rendering feature as per this KB as a workaround to avoid causing any confusion to your Service Desk agents. Please note that disabling this feature will also change the unit of the SLAs displayed to your agents: They will no longer be displayed in Years, months, weeks or days unit, but only in hours and minutes.

If you are facing something different, can you please provide us a screenshot to better display where is the problem you are talking about?

[Iago Docando]

Thank you for your interest but I don't think that's the same bug I'm experiencing. They might be related though, so I have voted for the one you've linked.

My problem comes not when I create one issue and there's a holidays calendar in place that might interfere with the SLA to resolution... it comes much earlier actually, when I'm setting up the holidays calendar.

[Petter Gonçalves]

Hello Iago,

Thank you for your answer.

Could you please provide us any screenshot displaying where is the exact behavior you're facing? Make sure to hide any sensitive information from the Screenshot.

I believe your issue may be related to some timezone configuration, however, I need the screenshot to better understand the problem you are facing and try to reproduce/further troubleshoot it.

Thanks!

[Iago Docando]

mmm... I'm afraid I can't replicate the issue at the moment. I will add a couple of FABRICATED screenshots to ilustrate what I experienced a couple of days ago. 

[Petter Gonçalves]

Hello @Iago Docando

Thank you for your answer. 

I believe you had some incoherences in your current timezone that might have caused this error.

In order to further investigate it, I suggest you the following steps in case the problem reproduces again:

1 - Check on your Atlassian.logs what is returned when you add the calendar date

2 - Check on the javascript console of your browser if any errors are returned

Let us know when you have the chance to check the steps above.

[Iago Docando]

I can't see anything out of the ordinary in the logs.

As for the developer tools... I'm seeing a lot of deprecated JS in the screen where I must set up the calendar. Also [Deprecation]chrome.loadTimes() ... instead use standarized API: Paint Timing.

I'm not sure what that is but it sounds suspicious ^_^