Story bug to allow ramp up start times and strict end times for tiles campaigns

questions: 1. Start/end times are times or dates? Does the advertiser says start on Jan 1 or Jan 1 at 15:30? 2. Start/end mean local user time (not GMT) 3. Is it OK if check for start/end campaigns sometime during the day, not necessarily on midnight. This has a problem of ending campaign a day after it was specified by the advertiser. The reason for asking is that implementation will greatly simplify if we can check on "idle daily" event and not to set special timer for midnight checks. Would it be OK to do "idle daily" for 39 and improving functionality later.

Got some answers from jterry by email: Ideally would be local times by hour. So "7am April 30" would be 7am pacific as well as 7am eastern. Using only midnight start/stop times is okayish. A fixed-global (not local) time could be useful in some situations, but local is better.

(In reply to maxim zhilyaev from comment #1) > questions: > > 1. Start/end times are times or dates? Does the advertiser says start on > Jan 1 or Jan 1 at 15:30? With time specific campaigns, advertisers will state the hour. But typically, if the time isn't state, it's understood that the campaign will start at midnight of the campaign start date and end 11:59pm of the campaign end date. > > 2. Start/end mean local user time (not GMT) User local time. > > 3. Is it OK if check for start/end campaigns sometime during the day, not > necessarily on midnight. > This has a problem of ending campaign a day after it was specified by the > advertiser. > The reason for asking is that implementation will greatly simplify if we can > check on "idle daily" event and not to set special timer for midnight > checks. Would it be OK to do "idle daily" for 39 and improving > functionality later. See #1 Jterry, please confirm.

I already posted jterry's confirmation in comment 2.

So, it looks like http://en.wikipedia.org/wiki/ISO_8601 is the date-time format we want: Firefox console: >> dt = new Date("2015-05-01T00:00:00") Date 2015-05-01T07:00:00.000Z So, it correctly returns local time translated into GMT time (7 hours diff) node interprets "2015-05-01T00:00:00" as GMT time instead, but i do not think we are. So, we can have full range of feature requirements implemented with this time format If server sends "2015-05-01T00:00:00" client interprets it as local time, But server can send time string with time zone "2015-05-01T00:00:00.000Z" it that would mean midnight in GMT, and will start campaign then. I think there is simple way to start/end campaign on exact start/end time.

This is a story bug not implementation.

All bugs this feature/[story] bug depends on have been fixed