microsoft / microsoft/AdaptiveCards
[Rendering] Mentions in Teams Message Extension do not work
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Target Platforms
Other
SDK Version
Cards: 3.1.0, Templating: 1.5.0, Expressions: 4.22.7
Application Name
Microsoft Teams
Problem Description
When viewing Mentions via an adaptive card in a message extension, the mentions do not render correctly. Instead the render with Name. This only appears to happen in the web/desktop version of Teams, as mobile still works correctly.
Screenshots
Card JSON
{
"$schema": "https://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.5",
"type": "AdaptiveCard",
"body": [
{
"type": "TextBlock",
"text": "<at>Adele Vance</at>, <at>Isaiah Langer</at>, <at>Kallen (Stadtfeld) Kozuki</at>"
}
],
"msteams": {
"entities": [
{
"type": "mention",
"text": "<at>Adele Vance</at>",
"mentioned": {
"id": "<entraId>",
"name": "Adele Vance"
}
},
{
"type": "mention",
"text": "<at>Isaiah Langer</at>",
"mentioned": {
"id": "<entraId>",
"name": "Isaiah Langer"
}
},
{
"type": "mention",
"text": "<at>Kallen (Stadtfeld) Kozuki</at>",
"mentioned": {
"id": "<entraId>",
"name": "Kallen (Stadtfeld) Kozuki"
}
}
]
}
}
Sample Code Language
No response
Sample Code
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the supplied Adaptive Card JSON to reproduce the mention rendering in Microsoft Teams message extensions, comparing web/desktop behavior with mobile. Done means the named mentions render correctly instead of showing the ... markup; the issue does not mention a source file or test to start from.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100