I am creating this post to track some inconsistent behaviour regarding pasting spreadsheet cells on to a Miro board.
The expected result is that the cells appear as Sticky Notes on the board. However, there have been some reports that Text objects are being created instead.
My test data as two cells in Excel, Excel web app, and Google Sheets:
I then pasted a single cell (the one with “one” in it) and then both cells at the same time.
I did this in both the latest 64-bit stable Chrome and Miro desktop app from Windows 11.
From my tests, I consistently got plan text when pasting a single cell from Google Sheets.
Results:
Chrome
Desktop app
Tagging @Kerrin and @JonoB here as they had reported the issue in an older post.
Alyona9 months ago
Hi @Robert Johnson,
I finally have some updates regarding this issue: what you suspected got confirmed by the team; there are differences in how the platform of origin implemented their copy functionality. Excel puts a single cell as a table, and thus we paste it as a sticky, while with Google Sheets, just the text is added to the clipboard. There's no way for Miro to know if that text used to be a cell in this case.
The team plans to work on fixing this inconsistency, but this would be out of our focus in nearest future. Taking into account the cause of this issue, I'm going to remove the [KNOWN BUG] marking from this topic.
Thanks for creating this ticket and reporting the behavior.
We have been able to reproduce the issue on our end, which enabled us to escalate the case along to our tech team. They will now be sure to investigate this case further, and we will get back to you once there are any updates to share.
Thank you all for your patience with us! Our team just released a fix for the issue with the sticky notes conversion. To make sure you're on the latest application's version, please log out and sign back in. If you still experience any issues after that, please let us know!
@Alyona - I reset my Miro app data, signed out in Chrome (and cleared my cache) and the issue is still happening for me (Windows 11, 64-bit). Specifically, if I open a Google Sheet in Chrome, enter some text in one cell, e.g., “test”, and then copy-paste that cell into a Miro board, it appears as Text.
But if I take that same cell with the word “test” in it, copy-paste that into another cell, and copy-paste those two cells into a Miro board, I end up with two sticky notes.
I compared Excel online to Google Sheets and this appears to be a Google issue(?) that Miro may or may not make an exception for.
When only one cell is copied in a Google Sheet, it is not being saved to the clipboard as a table td (“<td>”) element. Instead, it is wrapped in a <span>:
Thank you all for your patience with us! Our team just released a fix for the issue with the sticky notes conversion. To make sure you're on the latest application's version, please log out and sign back in. If you still experience any issues after that, please let us know!
I finally have an update for you! So the issue that our team fixed last week was a different one, and it looks like I might have misinformed you here. The team was working on ensuring that copied cells get pasted into the table in Miro and do not cause stickies or text boxes to appear instead.
On the other hand, the issue where one cell copied from Google Sheets and pasted to the board doesn't become a sticky note despite a cell copied from Excel becoming one is an inconsistency our team is aware of. I don't yet have any information on whether or not they'll be working on it any time soon (if ever). If I have any other updates, I'll let you know in this thread!
I finally have some updates regarding this issue: what you suspected got confirmed by the team; there are differences in how the platform of origin implemented their copy functionality. Excel puts a single cell as a table, and thus we paste it as a sticky, while with Google Sheets, just the text is added to the clipboard. There's no way for Miro to know if that text used to be a cell in this case.
The team plans to work on fixing this inconsistency, but this would be out of our focus in nearest future. Taking into account the cause of this issue, I'm going to remove the [KNOWN BUG] marking from this topic.
