Open dongbohu opened 7 years ago
Currently, @scrum-lord opens issues for two days in advance. This guarantees that the next workday always has an open issue. The goal here is that you should always be able to post future tasks.
@dongbohu moving to 1-day in advance would partially address your issue. To fully address it, we would need to get Travis to run its cron jobs in the afternoon. Perhaps we could do this with trial and error (there is no hour of the day setting).
@jaclyn-taroni @cgreene thoughts?
If there's no easy way to specify the hour, my inclination is to not put too much effort into nailing down the time. However, it's up to you guys how important it is.
I'm not sure I follow @dongbohu's concern. I will add that I have posted two days in advance, so I like the current setup for that.
In https://github.com/greenelab/scrumlord/commit/9d43aa334e957ff1f5c7b7b7df25ed747ee6f891, I configured --workdays-ahead=1
, so now @scrum-lord should only open issues for 1 day in advance.
Let's see how we like this for a few weeks. If we think two days ahead was better, we'll revert.
It would be nice to have the eScrum issues that are after today created in the late afternoon of today (instead of in the morning). That way when users add their own activities in the morning, the issue at the top will be always the one to update.