Bug: name mismatch when renaming recurring meeting

[jordanh]

Issue - Bug

1. Enter a retro meeting that has been set up with recurrence
2. Rename the meeting
3. Navigate back the dashboard, note the name does not match (even after pressing refresh)

See this Loom: https://www.loom.com/share/55b16964192b481fabe4307d42144038

• How serious is the bug? P3
• OS: macOS
• Browser: Chrome

Acceptance Criteria (optional)

Users can:

• Rename (and override) the latest (open) meeting in a recurrence series

Estimated effort: 1 hour to triage. More if root cause is already identified.

[iamhks]

Hi @jordanh
I replicated the bug and here are my observations:

I setup a recurring retro:

Post that I opened the meeting:

As you see for the first instance of the meeting the Date is automatically appended in the title. That means each meeting is a unique instance. When a user edit's the title for a meeting they are just updating that specific instance. This is particularly helpful if we want to make a note of important meetings for example:
"Retro - All Hands"
"Retro - Christmas"
and the regular recurring meeting will continue like "Retro - Jan 29"
Hence, this might be the intentional design is what I feel.

The bug actually is once you edit in recurrence settings from the home page you get a server error, that shouldn't happen.

I looked into it and observe that once you refresh; the edited meeting name does update! So we just need to fix how the response is handeled in the front end. What do you think?