You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a public board is copied. Board documents are created on DB for every folder that the Public board contains with the email of the user who is copying.
However, these documents could contain folder tiles that use a "loadBoard" property that should have the value for the ID of the board document that includes the board for this folder.
This property is pointing to the board IDs of the Author of the public board instead.
This causes the copying user not to find the folder because is not of his property. Some folders continue working only if the folder label matches exactly with the name of the board. that is not an expected behavior.
How to test it.
Just exactly after copying a public board. the "loadBoard" for the boards on the local Store is correctly set for that to find this issue using the app:
Copy a public board in a new account.
Sign Out of the account.
Sign In
Change the label of a folder
Click on the folder and the board is lost
The text was updated successfully, but these errors were encountered:
Bug description
When a public board is copied. Board documents are created on DB for every folder that the Public board contains with the email of the user who is copying.
However, these documents could contain folder tiles that use a "loadBoard" property that should have the value for the ID of the board document that includes the board for this folder.
This property is pointing to the board IDs of the Author of the public board instead.
This causes the copying user not to find the folder because is not of his property. Some folders continue working only if the folder label matches exactly with the name of the board. that is not an expected behavior.
How to test it.
Just exactly after copying a public board. the "loadBoard" for the boards on the local Store is correctly set for that to find this issue using the app:
The text was updated successfully, but these errors were encountered: