Good Morning,
Since the latest update, trello has now re added the card cover margin boarders around the edges of all card covers as a default (whether you use your own image or stock image).
The new card cover margin boarder also try’s to colour code itself, to the colours which are within the images being used, and the majority of the time these margin boarder colours which are being automatically created do not match the image colours, therefore makes the card cover look ridiculously unappealing. I’ve attached an image so you can see
If I select the full size card cover, I do not want trello to add a boarder to any of my selected images, whether it’s my own image or stock image. How can I remove this feature and go back to the previous update where this issue did not exist, and there was no automatic margin boarders being applied to card covers? if someone would like to use and image without a boarder being applied then this should be an option, especially when the full size option has been selected (this should mean full image - no boarder applied)
The automatic colour coded boarders make your entire board look horrendous, especially if you use a substantial amount of cards like I do
Please can someone get back to me on how to resolve this issue? Thank you
Hi, Ev!
Thank you for sharing this issue.
After some testing on our end, we were able to reproduce what you're seeing and have now opened up a new bug report that you can find right here: TRELLO-1343.
I have also added this ticket as an internal comment to this report so that way our engineering team can reference it and also use it to help align priority.
That being said, with the link I sent above, you should be able to watch this issue by clicking on *Start watching this issue*.
For further information about how we track and fix our bugs, you can review the Atlassian Cloud Bug Fix Policy.
If you have any additional questions, things you would like to make known about this bug, other concerns or feedback, please feel free to let me know!
Good Morning Augusto,
I greatly appreciate you taking time to respond, thank you
Thanks again for adding a ticket to this issue
This is actually the second time this has happened on an update, I assume the engineering team updates the web browser version, and doesn’t even bother to check if the mobile version displays any errors before making the update available to users?
I haven’t used the web version for years!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.