search

magfest / ubersystem

MAGFest's Ubersystem - handles ticketing, staffing, analytics, volunteers, and tons more
http://magfest.org
GNU Affero General Public License v3.0
47 stars 54 forks source link

Incorrect times in header for staffer signup #663

Closed tronster closed 9 years ago

tronster commented 9 years ago

Setting up a shift for 9am to noon. Go to "Staffer sign ups" to assign that shift; the header of the web-page shows "2-5pm Friday". Seems header is just wrong, because it does properly assign the shift.

bds002 commented 9 years ago

Tronster - Email me please - bsmart@magfest.org (stops@magfest.org) - What department are you working with? I was able to setup shifts for Staff Ops, Staff Support and Chiptunes without issue.

Please let me know the department and the day you are looking at.

EliAndrewC commented 9 years ago

Weird, I haven't noticed that issue, but this does sound really annoying. I'll take a look over the weekend.

bds002 commented 9 years ago

Eli- I see what he is talking about now.. This has to be resolved for Shift Sign-ups.....

If you compare Shifts under Calender View https://prime.uber.magfest.org/m13/jobs/index?location=80341158

And then change the drop down box to show Signups View.

You lose Friday morning's shifts ... Calendar view shifts start at 8am... Signups View shifts don't start till 1pm

EliAndrewC commented 9 years ago

Huh, weird. I'll check that out; I suspect this might be a bug relating to the fact that our datetime objects have timezones attached, and there have been a few places where I didn't properly update the code to account for that. This will probably be a one-line fix, which I agree we definitely need to make before shift signup goes live.

tronster commented 9 years ago

I assume you guys are on it; I was witnessing this in the MIVS (indie) dept. Hit me up if you need any other information from me.

JennyTruss commented 9 years ago

I saw this same thing just now. I have shifts that start at 8am, but when I switch, it says they start at 1pm.

EliAndrewC commented 9 years ago

I just made a merge request with a fix for this, so it'll be deployed to production within the next few days.