Asking to Edit a Workspace: "Null" Displays in Prompt Instead of User's Name

When a user who has a viewer or commenter role in a particular workspace requests to edit that workspace, editors will receive an in-workspace prompt that displays “null” instead of the user’s name.

This happens when a user requests edit access for a workspace through a meeting and if a team member requests edit access for a Team’s shared workspace.

Steps to reproduce

Scenario 1:

  1. User A: Starts a personal room meeting with a blank workspace
  2. User B: As a team member, joins the meeting and accesses the workspace
  3. User B: Requests edit access by selecting ‘Ask to edit’

Scenario 2:

  1. User A: Creates a workspace and shares with members with a viewer role
  2. User B: As a team member with viewer access, requests edit access for the workspace
  3. User A: As workspace owner, access the workspace

Expected result

Scenario 1:

  • The following ‘Ask to edit’ dialog box should display for requestor:

    Ask to edit content:
    Your request can immediately be granted by any Editor in the workspace. The owner will also receive an email. Once granted, you will become an Editor”**

  • Requestor’s name should be displayed in the the in-workspace message.

Scenario 2:

  • Requestor’s name should be displayed in the in-workspace message.

Observed result

Scenario 1:

  • The requestor is presented the wrong dialog prompt when asking to edit. The following dialog displays:

    Ask to edit content:
    Your request can be granted by the workspace owner and any editors present in the workspace.
    Once approved, you will be able temporarily edit content in the workspace for 24 hours.

  • Requestors name displays as “null”, instead of user name on the in-workspace request message.

Scenario 2:

  • Requestors name displays as “null”, instead of user name on the in-workspace request message.
     

Note: these issues will be fixed in an upcoming hotfix tentatively scheduled for Thursday, Aug. 17th.


If you are experiencing this issue, please react to this topic and help our product team understand the scope of impact on our members. Plus 1

This issue is resolved in Bluescape version 23.08.2.