Allow customizing the feedback form template
complete
A
Ahmed Ramy
I wanted to make our users write their bug report in a helpful fashion like
- What Happend?
- What is expected?
- Customize the email field so it's mandatory.
- Checkbox YES/NO
Log In
Peter Simic
complete
DONE 🤓 100% customizable bug submission form is now available on Flutter and React Native too. Let us know what you think of it in our Slack community.
Peter Simic
Tailor Shake SDK to your own app testing workflow! 🦄 Fully customizable forms are now available on native
iOS
and Android
SDKs v16.0.Shake SDK v16.0 for React Native and Flutter will be available in a few days too.
We'd like to hear what you think of this latest SDK — join other Shake users in our Slack community.
Borna Spanic
Hi everybody,
We changed the status for this ticket to "In progress". Shake created a community where we discuss the design and it's implementation. I will send the invites on our community voter so you can be fully up to date.
Borna Spanic
in progress
Peter Simic
planned
Update: We're now writing a specification for this ✍️ Thanks for the patience, form input field customizations are coming your way!
Petra Gluhak
Merged in a post:
Option to make email field mandatory
P
Peter
Add the option to make the email field mandatory for a user before a bug/feedback ticket can be sent.
A
Admin Tools
This would be great !
I think it could some generic input type like:
-Text
-Select
-Number
-CheckBox
-RadioButton
R
Robin Kunz
I would also like to be able to customize the "Ticket has been submitted" bottomsheet (page) after the user sends a ticket. Right now its quite formal and doesnt trigger nor motivates the user really well (emojis, special text according the specific branding).
So in general I would highly appreciate it if we have more customization in terms of User Interface (design, text) and fields (custom fields, very basic surveys, Links etc.)
R
Robin Kunz
Really like this idea!
Petra Gluhak
Merged in a post:
Multiple input fields
J
Joseph Ross
Testers report better bugs when the bug reporter prompts for specific details. A pattern we've found works well is to prompt for the title (sentence), detailed description (paragraph), and numbered steps to reproduce. Buglife even allowed us to have a multiple-choice frequency field. https://buglife.com/docs/ios/custom-fields.html
With Shake, we occasionally get a devoted tester that crams all of these into the single field Shake offers, but it would be best if we could prompt for this information.
Load More
→