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
HOLD #39508When 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
ResolveActionableReportMentionWhispercommand with areportActionIDand aresolution, which can beyesorno. ThereportActionIDis the one of the whisper.If the whisper is resolved it should not be displayed to the user.
The whisper message will be:
reportNames[0]doesn't exist yet. Do you want to create it?"reportNames[0]andreportNames[1]don't exist yet. Do you want to create them?"reportNames[0],reportNames[1]andreportNames[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
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @kadiealexander