View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003901SOGoWeb Calendarpublic2016-11-16 05:102016-11-17 02:59
Reporterryanhess Assigned Tofrancis  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionunable to reproduce 
Platform[Client] MicrosoftOSWindowsOS Version7
Product Version3.1.5 
Summary0003901: Cannot Add Calendar Event with Same Start and Stop Date
Description

When you try and add a calendar event in webmail selecting a start date in the future, you cannot select a start date on the same date even with a time later than the start time on the same date. Typing in the date or using the calendar selector always results in the end date advancing a full day ahead of the start date.

Steps To Reproduce

Sign in to webmail.

Click Calendar icon.

Click Create a New Event.

Enter a Title for event.

Select a start date in the future.

Notice the end date advances one day beyond selected start date.

Additional Information

No matter how you try to enter the start or end dates (text or calendar selector), you cannot get the event to have start and end dates on the same date.

TagsNo tags attached.

Activities

francis

francis

2016-11-16 20:36

administrator   ~0010875

Can you reproduce the problem on http://demo.sogo.nu/?

What browser do you use and what is your configured timezone?
ryanhess

ryanhess

2016-11-16 20:55

reporter   ~0010876

I logged in to the demo as sogo1 and could not reproduce the same issue/error. However, my test calendar events do not immediately appear after clicking save. I had to log out of the calendar and sign bck in to see my event added on the 18th. Is this normal?

The browsers we've tested on are IE11, Firefox and Chrome. All produce the same results. The time zone is set to America/Chicago.

Anything else I can do to help test?
francis

francis

2016-11-16 21:08

administrator   ~0010877

You should see your new event immediately unless the calendar to which it has been saved is disabled.

I can't reproduce this problem on neither Chrome nor Firefox.
ryanhess

ryanhess

2016-11-16 21:13

reporter   ~0010878

Would you be able to try reproducing it from one of your browsers logging into our setup?
francis

francis

2016-11-16 21:16

administrator   ~0010879

Sure. Send me the credentials by email.
ryanhess

ryanhess

2016-11-16 21:26

reporter   ~0010880

Should I just add them to this ticket or do you want to send me your email address?
ryanhess

ryanhess

2016-11-16 23:04

reporter   ~0010883

We upgraded to 3.2.1 and this issue appears to be resolved.

Issue History

Date Modified Username Field Change
2016-11-16 05:10 ryanhess New Issue
2016-11-16 20:36 francis Note Added: 0010875
2016-11-16 20:55 ryanhess Note Added: 0010876
2016-11-16 21:08 francis Note Added: 0010877
2016-11-16 21:13 ryanhess Note Added: 0010878
2016-11-16 21:16 francis Note Added: 0010879
2016-11-16 21:26 ryanhess Note Added: 0010880
2016-11-16 23:04 ryanhess Note Added: 0010883
2016-11-17 02:59 francis Status new => closed
2016-11-17 02:59 francis Assigned To => francis
2016-11-17 02:59 francis Resolution open => unable to reproduce