SSWConsulting / SSWConsulting/SSW.Tiger

✨ Alternate Access Point for Recording - Tiger can’t access Teams meeting recording when original organizer has left the company

Open
#61 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Bug YakShaver
Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
2d 12h
Merged PRs (30d)
2

Description

Cc: @yaqi-lyu @calumjs @joshbermanssw @suiyangqiu
Hi Team

▶️ Watch the video (01:09)

Describe the Bug

Tiger fails to process/access the recording for a recurring sprint review meeting (TinaCMS / Tina Cloud) when the original Teams meeting organizer has left the company.

Current behavior appears to be that Tiger tries to access the meeting recording via the original organizer’s account, which is no longer possible after the organizer’s account is removed/disabled.

To Reproduce

Steps to reproduce the behavior:

  1. Have a Teams meeting series created by an organizer who later leaves the company (account removed/disabled).
  2. Run Tiger against the sprint review meeting (e.g., TinaCMS / Tina Cloud) and attempt to locate/access the meeting recording.
  3. Observe Tiger failing when attempting to access the recording through the original organizer’s account.
  4. See error
Expected Behavior

Tiger can access the Teams meeting recording via an account/path that remains valid even if the original organizer leaves (e.g., via the recording owner/uploader, the actual recorder, or another stable resource such as the meeting/chat/channel files location).

Tasks
  • Investigate how Tiger currently resolves and authenticates access to Teams meeting recordings
  • Identify Microsoft Graph / Teams APIs that can retrieve a recording without needing the original organizer’s account
  • Implement an alternative recording lookup strategy based on recording owner/uploader (or equivalent permanent source)
  • Add automated test coverage for the “organizer left the company” scenario
  • Fix
More Information

Current workaround is to send a new meeting invite from someone still in the company, which is undesirable.

Environment
  • Device: N/A
  • Browser: N/A
  • OS: N/A
Screenshots

Tiger bug context screenshot

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how Tiger currently resolves and authenticates access to Teams meeting recordings, then review the Microsoft Graph and Teams API calls involved. Reproduce the case where the organizer’s account is removed and identify a stable recording owner or storage path. Done means an alternative lookup works in that scenario and automated test coverage is added.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.