Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduler #2

Open
eelzon opened this issue Oct 14, 2014 · 4 comments
Open

Scheduler #2

eelzon opened this issue Oct 14, 2014 · 4 comments

Comments

@eelzon
Copy link
Owner

eelzon commented Oct 14, 2014

Would be nice to set a daily time for standups to occur. (Comes with a "!when" function to ask when the next standup is; also comes with the requirement that you can't start a new standup when one is occuring.)

@xiaozhupa
Copy link

Setting a time would be super useful!

I think what you need to have is also an ability to force start the standup and perhaps list the people who were absent in that morning standup. It is similar to absent staff in the workplace.

@zethussuen
Copy link

+1. Would love to just have something simple like...

!when
bot: what time do you want to schedule standups?
m-f 9am

If a standup is in session, automatically close like @xiaozhupa said. IMO if you haven't finished a standup within 24h, it's pretty much useless.

@sos4nt
Copy link
Contributor

sos4nt commented Sep 15, 2015

This can be easily achieved via IFTTT by using the Post a daily reminder to a Slack channel recipe.

screenshot

@sos4nt
Copy link
Contributor

sos4nt commented Sep 15, 2015

Sorry, the above doesn't work. Unfortunately Slack is posting all bot messages under the same name, i.e. "slackbot". morgenbot has to ignore its own messages and - due to that limitation - ignores all bot messages, including the one from the IFTTT bot. 😞

ithcy pushed a commit to ithcy/morgenbot that referenced this issue May 19, 2016
Improve command parsing, add prefix_only param
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants