1009313: Resolved Operations not applied to user issue.

[mohammedaffanc]

Bug description

1009313: Resolved the Operations are not applied correctly to a newly joined user after the document is auto‑saved.

Root cause

In ImportFile API we are calling the GetPendingOperations using the FileName which returns 0 actions causing the issue.

Solution description

Need to use the roomName as we are using roomName to update actions to Redis cache.

Task and Ticket ID

• Task ID - https://dev.azure.com/EssentialStudio/Ej2-Web/_workitems/edit/1009313
• Ticket ID - https://support.bolddesk.com/agent/tickets/810652

Reason for not identifying earlier

• Guidelines not followed. If yes, provide which guideline is not followed.

• Guidelines not given. If yes, provide which/who need to address.
  Tag label update-guideline-coreteam or update-guideline-productteam.

• It was missed earlier

Areas tested against this fix

Provide details about the areas or combinations that have been tested against this code changes.

• Tested against feature matrix. Feature matrix link
• NA

Is it a breaking issue?

• Yes, Tag breaking-issue.
• NO

If yes, provide the breaking commit details / MR here.

Action taken

What action did you take to avoid this in future?

Feature matrix document updated

• Yes
• NO
• NA

Automation details - Mark Is Automated field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the bug is automated.

• Pagination
• E2E or Manual Automation using tester - Make sure all items are automated with priority before release which can be tracked in automation dashboard.

If the same issue is reproduced in ej2, what will you do?

• Resolved. Provide MR link.
• NO. Created task to track it. Share task link.
• NA

Is this common issue need to be addressed in the same component or on other components in our platform?

• Yes - Need to check in other components, tag needs-attention-coreteam
• No

Output screenshots

Post the output screenshots if an UI is affected or added due to this bug.

Blazor Checklist

Confirm whether this feature is ensured in both Blazor Server and WASM

• NA
• Yes
• NO

Is there any new API or existing API name change?

• Yes. If yes, Provide API Review task link.
• NO

Is there any existing behavior change due to this code change?

• Yes. Add breaking-change label.
• NO

Do the code changes cause any memory leak and performance issue? (Test only if you suspect that your code may cause problem)

• Yes
• NO

Reviewer Checklist

• All provided information are reviewed and ensured.

[Thamizhselvanv]

Approved this pull request.