Customize the create post form with more fields | Feature Requests

Customize the create post form with more fields

complete

Suspicious Peafowl

In addition to a title and details field, allow admins to add additional custom fields. In another setting where we use Aha to collect feedback from customer-facing teams, we have custom fields to prompt specific questions like:

how would this help solve a customer's problem? (text area)
what is the relevant product area? (single select)
steps to reproduce the bug?

These Qs might be too much for a customer-facing feedback site, but they're super useful for discussing and sorting through ideas internally.

Ramiro Olivera

marked this post as

complete

We've just introduced the concept of custom post fields
!
Once your team has created post fields, you can add up to three of them to your create post form and optionally make it a required field.
Check out this help article to learn more about post fields.
Custom post fields are only available for teams on a Growth plan or above. Thanks for sharing your thoughts and helping us improve Canny!

Mushy Cephalopod

Ramiro Olivera: Hey Ramiro! I noticed the help doc is going to a 404, and while the UI is available for me to create the new forms, I can't see them in either the app or our Zendesk integration. Am I just a bit early here?

Ramiro Olivera

Mushy Cephalopod: Hey Jessie, thank you for letting me know, the link should be live now! Regarding the fields, they are available only on Canny and the widget for the time being, but the plan is to release them for integrations too.

Remember to add the fields to each individual board for them to show on the "Create post" form. Also, don't doubt to reach for support if something is not working as expected!

Overseas Tahr

Ramiro Olivera: Question, the fields dont show in the front end i.e. already published requests? we see it in the backend as admins but frontend doest see.

Limited Lobster

Ramiro Olivera +1 for what Majid says above me. Also, let me ask: These fields don't apply to alredy-existing posts it seems, is that true? If a user edits an already-existing canny, then this field is not there. why?

Zippy Tuna

It will be cool if also the initial post inputs are bigger or somehow expandable. It looks comically small for our business when we are asking users to post a lot of details and multiple screenshots: https://forum.serpapi.com/bugs

It's the reason we have to switch to a public GitHub issue-only repository for our business for now: https://github.com/serpapi/public-roadmap/

Sarah Hum

marked this post as

in progress

Coming soon, stay tuned! We're going to support up to 3 additional fields on the create post form. Admins will be able to create and fill in additional information beyond those fields.

Fuchsia Dove

Sarah Hum: 👏

Scarlet Carp

Sarah Hum: Can you please confirm what the 3 additional fields will be? Will we be able to add and remove any fields? We were about to cancel our paid subscription here, but we are willing to reconsider if you can show us the designs of the new feature and when it will be live.

Sarah Hum

Hi Scarlet Carp, it'll be pretty flexible. Basically, we're introducing a concept of custom "post fields". You create a new post field (see image for the types we'll support) and then you'll be able to add those to the create form. Those 3 additional fields are completely optional and can be removed. The existing title and details fields cannot be removed. We're estimating this'll be available within the next week.

Fuchsia Dove

Sarah Hum: This is excellent!!

Sarah Hum

marked this post as

planned

We know that this will help your teams add more context to requests. That said, we also want to keep in mind that the more you ask from end-users, the less you might get. We're planning to support up to 3 additional fields on the create post form. Admins will be able to fill in additional information beyond those fields.

Thanks those who gave thoughts already. Feel free to continue sending those our way!

Fuchsia Dove

Sarah Hum: Good points. Excited for this one!

Lime Mosquito

Sarah Hum: Thank you Sarah!

Silver Sawfish

Sarah Hum: We'd like to steer the people posting requests to speak more about their problems/needs/jobs to be done, instead of proposing a solution. That'd really help us get to the bottom of our users' issues quicker, so if there's anything that can be done on the form level, that'd be great!

Sarah Hum

Silver Sawfish: You'll be able to adjust the field name and placeholder text to help guide them!

Private Beaver

Sarah Hum: I hope that these custom fields will be editable by admins, e.g. via API.

Sarah Hum

Merged in a post:

ability to change post forms

Overseas Tahr

Right now, we can not ask stakeholders to have multiple information in different fields. It would be great if,

me as a Canny admin can define the fields that should be filled in addition to title and details like custom fields for ease of management.
Allow different kinds of fields like numeric, yes/no, date. etc.
Also allow labelling of bugs
having filters for these as well.

Sarah Hum

marked this post as

under review

We know this is a popular request and we want to hear more! Give us specific examples of what you would add to your create post form(s). We're also thinking about what types of fields to support (text, dropdown, etc.).

Fuchsia Dove

Sarah Hum: Awesome. The primary problems this feature would solve for us are:

Ensure the necessary information is added to every request so our Product and Engineering teams can properly prioritize it without hunting down this information from our team or customers.
Provide clarity to our team around what information the Product & Engineering teams need on each post to properly prioritize them. This would reduce training time for new employees as well.

Below are the ways we would use it for our two main Canny boards. Note, our internal team will sometimes post to each Canny board, but our users will too sometimes. The fields marked with a * are ones that we only expect our team to fill out, not our users.

For Feature Requests:

Description of what the feature should do (plain text)
Problem the feature will solve for clients (plain text)
What is the current workaround and how bad is it (plain text)

For Bug Reports:

Describe exactly what is happening and steps to reproduce it (plain text)
Link to page where this happened in your (the client’s) account (URL)

The following fields would ideally be in a private comment, entered by our team, so they aren't publicly visible to our users:

Intercom Conversation Link (URL) *
Loom video reproducing the bug (URL) *
Client Name (plain text) *
What is the severity of this request? - Can't use app, Major annoyance, no workaround, A minor annoyance, or workaround (multiple choice) *
Is this a VIP client (yes or no)? *
In your estimation how many clients may be impacted (number) *

Mushy Cephalopod

Sarah Hum: Yes yes yes this would be amazing! We use Canny internally only, and we ask our CS team to fill out the following info: 
What does the merchant want?
Why do they want it?
Link/Resources:
What are the current workarounds?
What platform are they on?
But they don't usually do it because it's not there as a prompt. We would like it either as text that is already in the request, or else as a question-answer form.
So for us the option of pre-loaded text (like you can do in Jira) along with customizable drop down options (like in Slack workflows) that would help enormously. 
Having required fields would be a great bonus as well.

Weekly Worm

Sarah Hum: we're very similar to others in that we want 
What is the Problem?
What is the Proposed Solution?
What is the current workaround?
Without having these as separate fields, we don't usually get the info we are after and end up having to comment to get the info, particularly to the first question....

Agreeable Lobster

Sarah Hum: I think the easiest way to get this to market while satisfying the most customers would be to allow users to add up to five elements with free-text labels. Then they could create whichever title for each field that best suits their use case. Elements could then either be text area or dropdown.

Temporary Crocodile

Agreed! We have similar needs to those posted here but ability to customize fields/field types would be the best. For example, Sarah Hum the ability to add multiple URL fields but only requiring one would be beneficial. And as others have mentioned, the information we need submitted for FR vs. bugs differ.

Worried Landfowl

Sarah Hum: It would be great to be able to have the "stars" field type available so we can specify effort on a per-ticket basis.

Odd Junglefowl

Sarah Hum: I have a similar need in that I'd like to be able to automatically add to the new Create Post form the page URL the user is viewing when they use the Give Feedback link we've put in our application. I think having that available would help me correctly interpret the problem or request the customer is reporting.

Sarah Hum

Merged in a post:

Add more optional fields in form

Gray Scorpion

In addition to using Canny as a feedback form, we also sometimes use it for bug report. I would like to be able to have additional optional text fields (in addition to "description" where I can ask for additional items.

Black Porpoise

Is this coming up in the roadmap soon Sarah Hum? Seems like it's a pretty common feature of other feedback tools: https://webpagefx.mangoapps.com/msc/NzE3Nzc1XzkwMjQxNjE

Sarah Hum

Hi Black Porpoise, no update to share on this yet. The hesitation here is because, the more we ask from end users, the less likely they will actually give feedback. We would much rather you get the feedback first and ask users to elaborate if need be. We will let you know via this post if we change our stance on this.

Artificial Flyingfish

Sarah Hum: I'm not sure how everyone else will leverage this, but the OP talked about needing more information internally from users. This is exactly our use case. We're not only using Canny for external users but also for internal users (such as sales or customer success) that may want to log a feature on a user's behalf.

In this case, we want more information and because it's an internal user, it's acceptable to ask these questions.

Unknown Centipede

Make selecting CATEGORIES MANDATORY too.

I always forgot adding Categories in the Feedback posts I do, that most of the time, they always end up in

"Uncategorized"