Best Of

Wonderful that a fix was put in place for what was clearly a bug.

If any folks from the Smartsheet side of things are reading this thread, what is nature of the disconnect between Support stating that this was design intent when it's actually a bug that requires fixing? It seems as though the response of "this is the current expected behavior of the Widget in the dashboard" puts the responsibility back on the user to submit through these forums, which offer limited visibility on traction and progress, as opposed to offering solutions and coordination internally across teams.

To ask this more directly, is there internal communication from what Support is seeing in their cases and what Product / Engineering can resolve as bug fixes?

Would love a feature to preview all documents regardless of format (pdf, excel, etc.). This would be very useful and time saver. Current process downloads excel sheets and have to open each document individually to look at one point of information.

Please prioritize working on this!!!

Thanks!

Can you please add the opportunity when creating a form, to enter an image into a specific cell when the user adds an image? Right now, they only load as attachments.

Thank you for the clarification, Genevieve. I appreciate you taking the time to provide a thoughtful response.

I'm drawing primarily on my experience working with other platforms and tools; when a bug is submitted through the ticketing system of these other platforms, Support engages directly with Engineering, the submitter is notified, and the bug is resolved in direct response to the initial ticket. The added requirement to post a bug to "Ideas and Feature Requests" to increase visibility, with multiple folks receiving the same "this is how the tool is designed to function" response, feels a bit roundabout, particularly for an example as straightforward as this. It also feels like bug reports muddy up the water of feature requests, though I understand if this portal is your primary point of community escalation and internal prioritization.

I realize that I'm flagging a challenge without offering up a solution, and without fully understanding your teams' internal structures and channels of communication. Just taking a moment to recognize the groundswell required to escalate a bug from support submission (possibly extending across multiple levels of support), through community posting, through upvote, through monthly Product Team review, and then eventually to resolution. It all feels pretty daunting and offers up multiple points of failure or abandonment.

Let me know if I'm reading any of this the wrong way - just reflecting on my experience elsewhere. Also, always happy to discuss further. Best everyone's way.