search

remy / retrobot

🤖 A slack bot for retrospectives
https://remysharp.com/2016/08/22/remote-retrospectives-with-retrobot
97 stars 44 forks source link

Support for multiple teams #7

Open batjko opened 7 years ago

batjko commented 7 years ago

Hi there,

I really like this idea (and the amount of time that can be saved this way). However, we have a couple of teams, each of whom usually hold their own retrospectives. I understand from the blog post, that currently the bot holds a single state and you'd need to run a new bot for each additional team that wants to use it.

It would be great if the bot could keep track of which channel it is holding a retro in (e.g. #retro-team1 vs. #retro-team2 etc.) and conduct separate retros based on that.

Just an idea.

Many thanks!

remy commented 7 years ago

Happy to take a PR or if it benefits your company, I'd be happy to discuss sponsored development. Feel free to email me on remy@leftlogic.com

On Wed, 29 Mar 2017, 09:42 Patrick Metzdorf, notifications@github.com wrote:

Hi there,

I really like this idea (and the amount of time that can be saved this way). However, we have a couple of teams, each of whom usually hold their own retrospectives. I understand from the blog post https://remysharp.com/2016/08/22/remote-retrospectives-with-retrobot, that currently the bot holds a single state and you'd need to run a new bot for each additional team that wants to use it.

It would be great if the bot could keep track of which channel it is holding a retro in (e.g. #retro-team1 vs. #retro-team2 etc.) and conduct separate retros based on that.

Just an idea.

Many thanks!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/remy/retrobot/issues/7, or mute the thread https://github.com/notifications/unsubscribe-auth/AAA1hIgEsRSKoQIow4cHhTzopehWSuBMks5rqhl5gaJpZM4MsrDn .

batjko commented 7 years ago

Probably not anytime soon, but at least the idea is logged in case we or somebody else get to make that update someday. ;)

On Wed, Mar 29, 2017 at 9:47 AM Remy Sharp notifications@github.com wrote:

Happy to take a PR or if it benefits your company, I'd be happy to discuss sponsored development. Feel free to email me on remy@leftlogic.com

On Wed, 29 Mar 2017, 09:42 Patrick Metzdorf, notifications@github.com wrote:

Hi there,

I really like this idea (and the amount of time that can be saved this way). However, we have a couple of teams, each of whom usually hold their own retrospectives. I understand from the blog post https://remysharp.com/2016/08/22/remote-retrospectives-with-retrobot, that currently the bot holds a single state and you'd need to run a new bot for each additional team that wants to use it.

It would be great if the bot could keep track of which channel it is holding a retro in (e.g. #retro-team1 vs. #retro-team2 etc.) and conduct separate retros based on that.

Just an idea.

Many thanks!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/remy/retrobot/issues/7, or mute the thread < https://github.com/notifications/unsubscribe-auth/AAA1hIgEsRSKoQIow4cHhTzopehWSuBMks5rqhl5gaJpZM4MsrDn

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/remy/retrobot/issues/7#issuecomment-290024780, or mute the thread https://github.com/notifications/unsubscribe-auth/AG8xJMDMGpKOh42iUlu8EYUZa-vDj2Cxks5rqhqYgaJpZM4MsrDn .