SSWConsulting / SSWConsulting/SSW.Tiger

✨ Teams Bot - Post an "SSW.Tiger is active" card into the meeting at start (needs custom bot)

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

Nobody has claimed this yet.

Needs Refinement Type: Feature
Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
2d 12h
Merged PRs (30d)
2

Description

Pain

The cleanest fix for end-of-meeting trigger confusion (#119) is a clear message shown inside the meeting the moment it starts, telling people Tiger is active and what to do at the end. Tiger's current pipeline has no meeting-start event, so this cannot be built today. It becomes possible once the custom Teams bot exists (the notification rework / custom Teams bot migration).

Split out from #119. The docs-and-notifications half ships in #127.

Blocked by

Custom Teams bot migration (the notification rework epic). This issue stays parked until that bot is registered and installed.

Feasibility (confirmed)

A custom Teams bot installed in a meeting receives a genuine meeting-start event via the Bot Framework SDK (OnTeamsMeetingStartAsync), provided its manifest carries the RSC permissions OnlineMeeting.ReadBasic.Chat (scheduled meetings) and ChannelMeeting.ReadBasic.Group (channel meetings). With the channel permission, the bot automatically receives start/end events for every channel meeting in teams where it is installed (exactly our sprint-review setup), so it does not need adding to each meeting individually. On that event the bot can post an Adaptive Card straight into the meeting chat.

Acceptance Criteria
  1. When a monitored meeting starts, the bot posts a clear card into the meeting chat indicating SSW.Tiger is active.
  2. The card explains the action required at the end to trigger the summary (stop recording or end the meeting).
  3. The card states participants do NOT need to leave the meeting.
  4. The card correctly states who receives the summary (consistent with the decision made in #127).
  5. The card links to the Tiger documentation page (created in #127).
  6. Wording is short, unambiguous, and suitable for non-technical users.
Notes

The docs page and recipient-behaviour decision both come from #127, so this issue reuses them rather than redefining them.

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 with the custom Teams bot migration and the Bot Framework OnTeamsMeetingStartAsync event, then read #127 for the documentation link and recipient decision. Done means a monitored meeting receives a short Adaptive Card stating Tiger is active, explaining the end action and that participants need not leave, with the correct recipient wording and documentation link.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.