feature request: name retros

[Trevoke]

As a multi-squad facilitator,
I want to name the retros
So that I remember what is what later when I reopen the app.

Ideally has text with today's date in the name and we can add some text e.g. squad name

[vanderhoop]

hey @Trevoke, you're not the first person to suggest this, and in past lives I've said this calls for users to be able to create 'explicit teams', but that's a much larger lift than allowing folks to name a retro, though it'd likely result in duplicate data entry.

alas, I think naming a retro could be an optional field within the 'lobby' and 'prime directive' stages of the retro, as that's at the start of the retrospective, and those UIs are pretty lightweight at the moment. (I'd like to avoid crowding the more interactive interfaces). Thoughts?

[vanderhoop]

I also gave a moment's consideration to making the /retros index a Phoenix liveview, and allowing facilitators to name retros after the fact, but it's unlikely that folks will visit the index shortly after participating in a given retro, so that might defeat the purpose in the name of using a cool technology. (sigh)

[vanderhoop]

Note: I'm (currently) against adding retro name to the creation interface—which, right now, is just a button— as I want to keep the barrier to entry incredibly low, but I could be talked out of that if the deal is right.

[vanderhoop]

Another idea, what if there were an ever present text input, labeled 'Retro Name:' available to the facilitator in the header in all stages prior to retro close? Here, to the left of 'Built by Stride':

---

Would it crowd that region of the interface? Yes. But maybe we avoid the label and just have Placeholder text of 'Name this retro!'?

[Trevoke]

I think the ability to name the retro during the entire retro is a good idea. I also think that it's possible to have the current retro name (the timestamp, etc.) be the default provided name, and people don't have to change it -- but they can if they want. Barrier to entry remains low, only those who care have to make a change. As a bonus, this particular behavior can be anywhere, including the lobby / prime directive sections, or the header. What do you think?

…

On Wed, Jan 29, 2020 at 9:04 AM Travis Vander Hoop ***@***.***> wrote: Another idea, what if there were an ever present text input, labeled 'Retro Name:' available to the facilitator in the header in all stages prior to retro close? Here, to the left of 'Built by Stride': [image: image] <https://user-images.githubusercontent.com/4386645/73363203-83e25600-4265-11ea-9fd0-be99bd78e847.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#555?email_source=notifications&email_token=AAAQSSPVIEWQKPTCG2EYIJTRAGEGBA5CNFSM4KIOGH3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKHJJ6Q#issuecomment-579769594>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAQSSI4G3I2LOR44J4AIULRAGEGBANCNFSM4KIOGH3A> .

[mrenoch]

+1 to naming retros. We've enjoyed using this tool and have found it more challenging to review historical retros w/out any accompanying metadata (name, participants, etc).