Page MenuHomePhabricator

PageTriage uses server rather than local time
Closed, ResolvedPublic


...while the rest of the interface uses local time (I believe there's a preference attached, or something)

Version: master
Severity: normal



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:03 AM
bzimport added a project: PageTriage.
bzimport set Reference to bz43365.

Nischay: could you explain how times displaying a few hours off is a high priority bug? :/

Yes, looking at a reviewer can get annoyed with "a few hours off", also showing different times at different places is really not a good thing. If a single reviewer gets annoyed and stops contributing it sounds like a high priority thing to fix to me.

I am interested in fixing this but waiting for some experts' feedback.

Sure, but that doesn't necessarily make it high priority. "it's leaking data" would make it high priority. "The API for this extension is broken" would be high priority. I highly doubt anyone is resigning in disgust from having anything to do with new page patrolling because the timestamps are two hours off. Setting to normal and CCing Ryan Kaldari in so he can provide any advice you need re a fix.

I think this is a good idea. This brings the behavior of PageTriage more in line with other MediaWiki interfaces. I also think it's fine to implement this in the API since otherwise we would have to compensate for the timezone on the client-side which is much more difficult.

Change Merged. I believe this is fixed now.