Skip to main content

Hello, dear Community.

As this is the only way to reach any support from Miro, i reach out again, after having this issue reported last year in autumn, soon after the layers function had been introduced.
There was no response.
In other cases, Miro support did acknowledge my messages and in two cases the team fixed the bugs that i reported. So i really hope that this message gets through, because this bug is really a dealbreaker for what i am doing with Miro.

 

Here is the message again:

i started to notices strange behaviour from the Layers function under certain conditions:

Here i do have a Layer called “Canvas”. It contains the following build up: 

  • a transparent frame, having the name on it. This frame is important to be able to export the whole canvas including content as an image or pdf.
  • a colored shape, just to give the coloured and visible frame
  • the canvas as an image

then there are several other layers. Relevant for this part of the board is the “Examples” layer which contains pre-existing sticky notes, those that you can see in the screenshot here.

The “default” layer should then contain all the additional sticky notes that users are adding. There: the “examples” layer can be hidden, and then users can add their own sticky notes, within the default layer. That is the plan at least.

 

 

What happens instead is the following: Whenever i create a new sticky note, while the “default” layer is selected, and the sticky note is created ON the canvas, then this sticly note gets automatically and inmediatly “pulled” into the canvas layer. Its suddenly in the canvas layer, and the canvas layer is also the selected layer, but without explicitly selecting it.

 

This only changes, when i delete the transparent frame in the background of the “canvas sandwich” within the canvas layer.
Then, sticky notes that are created inside the default or any other layer, stay in that layer and do not get “pulled” into the canvas layer.

Its most defenitly a series of bugs that show up here, also because, when i save the template and then insert it, the behaviour of the layers start to change, also somehow randomly. 

Sometimes it works, sometimes not.
 

Of course i could also give the Miro support team access to the board of even a live tour of the bugs.

Best regards,
Benjamin

Hi ​@DataDriverOlav,

 

Thank you for sharing the detailed explanation of the issue you're encountering with the Layers feature. I understand how critical this functionality is for your workflows!

 

While the Miro Community is a great space for discussions and sharing ideas, technical issues like this are best addressed by the Miro Support team directly. I’ve gone ahead and converted your post into a support ticket to ensure the team investigates this thoroughly.

 

If you have additional insights or updates in the meantime, feel free to share them here.

Thank you ​@Eca 

 

yeah there are comming up many more issues with the Layers function like:

-- Elements “jumping” from one Layer to another. Even parts of grouped elements jump randomly back to the default layer, after they have been moved or placed into a certain layer.

-- Elements “flicker” and keep standing there, visible, even after a certain layer was selected to be hidden. This also seems to happen randomly. When i then make the layer visible again and then hide it again, then usually the visible element goes back into normal behaviour. This also seems to happen randomly, after hovering over hidden layers in the layers selection menu (but not clicking it).

-- Still, elements change their placement within the layers, and mostly jump back to the default layer, after a template has been created and saved that includes layers. Of course every layer has different elements. But they should of course stay in the layer the supposed to stay in, especially for a template. This also seems to happen at random (of elements jump back to the default layer).
-- Sometimes elements just jump to a completly different layer.
-- When using layers, the “send to back” or “sent to front” function does not to work properly anymore, or in other words, does not actually send items to the back or front. Not even within their own layer structure. For example: 

 - I have Layer 1 with 10 Elements, all stacked. I have Layer 2 with 10 Elements, stacked. I have Layer 3 with 2 Elements, stacked.

-→ Now want to sent Element 7 from Layer 1 to the global back. It does sometimes work, and sometimes not. My conclusion: the function is only referencing to its own Layer 1 environment. Nope, unfortunately, even when i expect Element 7 to become Element 1 (the most in the back), within the stacked structure of Layer 1´s 10 Elements, i would expect this to work locally within the Layer. But it does also many many times not work as expected. Rather, it seems to happen randomly.

 

It really looks like you guys fundamentally have some issues with how the data is stored in the background, maybe there is a logic conflict? I think it really would make sense to look at it, because unfortunaletly this behaviour is really much like a beta-beta-beta.

 

Thank you a lot anyways for taking the time and i am happy to show more to the support team and really give them a tour, because if those Bugs could be fixed soon, it would improve our days a lot and Miros usefullness.

​​​​​​​Best,
Benjamin

Reply


Terms & Conditions