Open grietine opened 1 year ago
Hi grietine! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.
Best regards, Teams Platform
Thank you for reporting this issue, we will check this and respond back to you. Would it be possible for you to share the JSON with us?
Sure!
@grietine - Thank you for sharing the JSON, we are also able to repro this issue with new channel experience in Teams. We will check this internally and get back to you. Thank you.
@grietine - We have shared the feedback with engineering team and raised a workitem to track this. We will keep you posted. Thank you.
@Meghana-MSFT Also want to say this "bug" is causing major frustrations for us as well. thnx
@CDSFounder - Apologies for the inconvenience caused. We have shared this feedback with team. We will keep you posted. Thank you.
@CDSFounder - Apologies for the inconvenience caused. We have shared this feedback with team. We will keep you posted. Thank you.
What is the status / response from your team?
Unfortunately, we do not have any update to share. Thank you for your understanding.
Can we vote anywhere to make this issue a priority? This is a major concern for us as well
Unfortunately, there is no such option. We are following up with the team internally. We will keep you posted. Thank you.
Update : A feature request has been raised to address this issue, team is working on the feature request.
More then 2 months passed since the last status update. What is the current situation?
Fix has been made to this issue. But it hasn't reached the public rings yet. We will keep you posted.
@Meghana-MSFT my company is suffering from this affliction as well. Is there any kind of timeline for a fix?
@Meghana-MSFT This is affecting us and our customers as well. Any updates on this?
@Meghana-MSFT Any update on publishing the fix? This is very disappointing to our users. I read above that the fix was made but not published yet.
@Meghana-MSFT our company is also affected by this, would be nice to have this fix ASAP, since it is disrupting our workflow a lot.
Apologies for the inconvenience caused to you. Fix is going to rollout in few weeks, but we don't have any exact ETA to share.
Hey @Meghana-MSFT do you have any update for us?
Apologies for the inconvenience caused to you. Fix is going to rollout in few weeks, but we don't have any exact ETA to share.
Any updates on when Microsoft will rollout the fix?
Same issue here, very frustrating. Any ETA for the fix?
This issue is fixed in new Teams T2.1. As you can see in below screenshot, see more/less button is removed.
@Meghana-MSFT What is T2.1 and how does it correlate to this?
Teams T2.1 is the new version of Teams. We tested in below version of Teams.
@Meghana-MSFT What about the teams web app? As a linux user i only use Teams in the Browser and i don't see the issue fixed there.
@co-sic - This issue is fixed in web client as well in the new version of Teams. Please find the version details in below screenshot.
Version details:
No see more/less button:
@Meghana-MSFT I am still seeing the issue in the version screenshotted below.
@jay-staffingengine - Are you on MAC machine?
I’m on a PC
@Meghana-MSFT I am still seeing the issue in the version screenshotted below.
Same problem here. Same version of Teams. Also web version still exhibits the problem. macOS Sonoma 14.1.2
We will check internally and get back to you.
Still not working. Not on the desktop client - latest version. Not on the web client. And you never got back to us.
Please note that the fix was done for adaptive cards and the original issue in this thread is also reported for adaptive cards. If you are still facing the issue with adaptive cards, then please share the card payload using the fiddler trace so that we can confirm that the Teams client is indeed getting the 'Adaptive card' type and then we can proceed from there.
Please follow these steps -
This is a response going through the steps above from a card from our Azure DevOps integration that is still showing "see more":
{"sequenceId":29913,"conversationid":"19:de8dda2a58934e37ba460187e9abed3a@thread.tacv2","conversationLink":"https://amer.ng.msg.teams.microsoft.com/v1/users/ME/conversations/19:de8dda2a58934e37ba460187e9abed3a@thread.tacv2","contenttype":"text","type":"Message","s2spartnername":"SMBA","annotationsSummary":{},"hasAnnotated":true,"id":"1707935024139","clientmessageid":"1707935024003","version":"1707935414485","messagetype":"RichText/Media_Card","content":"<URIObject type=\"SWIFT.1\" url_thumbnail=\"https://urlp.asm.skype.com/v1/url/content?url=https://neu1-urlp.secure.skypeassets.com/static/card-128x128.png\">Build 20240214.6 - succeeded
And decoding the Base64 data:
{"type":"message","summary":"Build 20240214.6 - succeeded","textFormat":"markdown","attachments":[{"content":{"summary":"Build 20240214.6 - succeeded","themeColor":"#107c10","sections":[{"text":"
Build for <img src=\"https://us-prod.asyncgw.teams.microsoft.com/urlp/v1/url/content?url=https%3a%2f%2fcdn.vsassets.io%2fcontent%2fnotifications%2fteams-pushrepo.png\" alt=\"Repo Icon\"> <img src=\"https://us-prod.asyncgw.teams.microsoft.com/urlp/v1/url/content?url=https%3a%2f%2fcdn.vsassets.io%2fcontent%2fnotifications%2fteams-branch.png\" alt=\"Branch Icon\"> <a href=\"/#version=GBmain\">main, finished 02/14/2024 18:23:30 UTC
","activityTitle":"<a href=\"https://dev.azure.com/itap-informatics-azure/609a9576-db36-42fe-b2fa-61b68a8087e0/_build/results?buildId=13677\">DEV Release / 20240214.6 (Succeeded)
","activitySubtitle":"Trigger: manual for Will Grauvogel
","activityImage":"https://us-prod.asyncgw.teams.microsoft.com/urlp/v1/url/content?url=https%3a%2f%2fcdn.vsassets.io%2fcontent%2fnotifications%2fteams-build-succeeded.png","activityImageType":"article","markdown":true,"startGroup":false}],"potentialAction":[]},"contentType":"application/vnd.microsoft.teams.card.o365connector"}]}%As we can see from the payload (see the contentType value at the end) it's a o365connector card as suspected and not an Adaptive card which is why you're seeing the 'see more'. Anyway, even for O365 connector cards, compared to Teams classic, the card was being truncated at much shorter height in latest Teams so, engineering team has pushed a change to bring parity with classic Teams and based on Teams releases, looks like that change will take some time to reach the general ring.
We are no longer able to avoid leaving Teams Classic and now are gravely afflicted by this for many integrations. It's near crippling with respect to something that used to be so seamless and useful
Version 24004.1304.2655.7488 (24004.1304.2655.7488)
When we set up our Integrations we started trying to use Adaptive Cards, but were unable and had to use https://learn.microsoft.com/en-us/outlook/actionable-messages/message-card-reference for Jira -> Teams Connector Webhooks Cards and for Webhooks sent directly from CI/CD Code
Please do one or all of the following:
It so discouraging having something so useful working and an escape like this ruin it
The initial comment on this thread highlights a broader concern.
Rather than imposing clutter and making unilateral decisions on behalf of users, could you instead implement configuration options to customize the display size and behavior of the 'see more/less' feature?
This has crippled our integrations and general experience with Teams.
@Meghana-MSFT
Please provide an update on when this issue might be solved in all the venues it remains broken. I was able to review to Teams Classic for awhile but now that option has been taken from me.
This is so painful for something that worked so seemlessly.
Same issue. You just broke an app that we took months to build. You seriously degraded the user experience for us. New ms teams is not fixed....
After upgrade to the latest version, I've noticed a change on how AdaptiveCards are displayed.
Currently, we have implemented a custom AdaptiveCard with all the necessary info, but in order to fully view it you have to click "see more" button. It's a small, but impactful change to our workflow. As everything in that post is important and especially that all the action buttons are on the bottom of the AdaptiveCard.
Can you implement a setting for channel or user to set a view size behavior of "see more / less"? Instead of forcefully deciding what's cluttering and best for the user, let the user to decide what he wants in this case.
Screenshots:
See more:
See less:
Thank you for your time!
Microsoft Teams Version: 1.6.00.12455 (64-bit)