[Payment due 2024-03-15][$250] [Mentions v2] Handle the new action type ACTIONABLEREPORTMENTIONWHISPER

[rlinoz]

HOLD #39508

When a user that is member of the policy tries to mention a room that doesn't exist we will send a whisper back asking if they want to create the room they just mentioned, this whisper type will be ACTIONABLEREPORTMENTIONWHISPER .

Resolving the whisper will call the ResolveActionableReportMentionWhisper command with a reportActionID and a resolution, which can be yes or no. The reportActionID is the one of the whisper.

If the whisper is resolved it should not be displayed to the user.

The whisper message will be:

• For a single room: "Heads up, reportNames[0] doesn't exist yet. Do you want to create it?"
• For two rooms: "Heads up, reportNames[0] and reportNames[1] don't exist yet. Do you want to create them?"
• For three or more: "Heads up, reportNames[0], reportNames[1] and reportNames[2] don't exist yet. Do you want to create them?"

Details can be found here in the Mentions V2 design doc.

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01e95bf52a9e340f42
• Upwork Job ID: 1789790273655398400
• Last Price Increase: 2024-05-12

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @kadiealexander

[robertKozik]

@rlinoz Do we have any specific ETA which we are aiming for with this one?

[rlinoz]

I didn't start the backend changes for this one yet, but ideally we would get this done before May 1st.

[robertKozik]

Great, ping me when backend would be ready - I'll then start this task

[rlinoz]

Hey @robertKozik do you think you can start on this? I started the backend already and as we were talking here this is the order we want to get this deployed to avoid any trouble:

1. Deploy the front-end to support showing the whisper
2. Deploy the front-end to support resolving the whisper
3. Deploy the back-end to support sending the whisper and handling its resolution

It will be a little harder to test, but I think we can manage.

[rlinoz]

Also updated the action to be ACTIONABLEREPORTMENTIONWHISPER

[melvin-bot]

Triggered auto assignment to @kadiealexander (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]

⚠️ 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 ⚠️

[melvin-bot]

Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (NewFeature)

[dubielzyk-expensify]

Looks like there's mocks in the doc, but happy to help. Is there anything needed from a design side on this? 😄

[rlinoz]

Oh I don't think so, it is just the new feature label I guess

[rlinoz]

Hey @kadiealexander this is in prod already, but I don't know how we create the Upwork job in new feature issues, can you help please?

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01e95bf52a9e340f42

[melvin-bot]

Current assignees @fedirjh and @ishpaul777 are eligible for the External assigner, not assigning anyone new.

[kadiealexander]

Payouts due:

• Contributor: $250 @fedirjh
• Contributor+: $250 @ishpaul777

Upwork job is here.

[ishpaul777]

hey! @kadiealexander this issue might be eligible for previous $500 bounty since this was created before April 5 https://expensify.slack.com/archives/C02NK2DQWUX/p1715196549664219?thread_ts=1715190852.677769&cid=C02NK2DQWUX