Add support for Descriptions in Group Chats

[marcaaron]

Coming from https://expensify.slack.com/archives/C05RECHFBEW/p1712957571237659

Problem

When we implemented Group Chats we did not give the ability to add a Description. This is largely do to the fact that we undertook a large migration of Group DMs over to Group Chats and are now harmonizing these two similar designs (Rooms & Groups).

Solution

When this ticket is done we should have the ability to add a Description to a "Group Chat" at creation and also update that description from the "Report Details" page.

Additionally, we should have the ability to create a description at the time when a Group Chat is created.

And lastly, we should ensure that:

• The CREATE action message + invitee "whisper" message includes the room description. Here's how it works for rooms:

• The email sent when inviting a user should display like this:

Subject: # [inviter] invited you to [RoomTitle] Body: [RoomDescription]

Backend changes:

I'd suggest we follow the existing pattern of reusing any possible code from Auth related to Rooms. In this case, the commands would be:

CreatePolicyRoom and UpdateRoomDescription. We create Group chats when calling OpenReport so reusing CreatePolicyRoom directly would be incorrect here.

Frontend changes:

Once we can support Group chat descriptions in the backend we can open this up to a contributor to wire up the UI changes and API.

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01472e1c18fbc629f5
• Upwork Job ID: 1780332023202934784
• Last Price Increase: 2024-04-16

[melvin-bot[bot]]

Job added to Upwork: https://www.upwork.com/jobs/~01472e1c18fbc629f5

[melvin-bot[bot]]

Triggered auto assignment to @isabelastisser (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[melvin-bot[bot]]

:warning: It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time :warning:

[melvin-bot[bot]]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @c3024 (Internal)

[isabelastisser]

Waiting for engineering assignment.

[isabelastisser]

Not overdue.

[JmillsExpensify]

@isabelastisser I'm going to take this one on, if you don't mind. Trying to get a handle on what remains for the group chat implementation.

[JmillsExpensify]

Still in the queue for group chats.

[JmillsExpensify]

Still in the queue.

[JmillsExpensify]

Same.

[JmillsExpensify]

Not a priority

[JmillsExpensify]

Not a priority.

[JmillsExpensify]

Still not a priority