Extend Make Contact Forms

[mrfoxtalbot]

The information submitted via contact forms on Make sites is stored in a "Feedback" tab on the site itself. This is very handy and gives us a fallback option in case the emails are lost HelpScout but the current functionality is very basic and makes it hard to handle those submissions efficiently.

I would like to extend the current "Feedback" tab to add the following:

• A basic taxonomy ("Status"?) to organise and filter form responses (each time will use different terms on based on their own needs). It should be possible to create new terms for that taxonomy.
• A new editable text field to add notes to each form submission (comments, external links, etc).

The above would be a bare minimum, if at all possible I would also make these two other changes.

• Reduce the height (or the amount info shown) on the listings page on keep each entry to just a few lines. Currently, they are too big and not easy to scroll through.
• Add a "edit" link on each entry to see the full info, edit the terms, and add notes. Alternatively, this could also be done from the list view itself, using something similar to "quick edit".

[mrfoxtalbot]

Current "Responses" listing

[mrfoxtalbot]

Proposed "Responses" listing

[dd32]

This is just the generic Jetpack contact form feedback section, and as such, any enhancements/changes we make here is likely to require ongoing maintenance if Jetpack changes how things are done.

I'm hesitant to make any enhancements here as a result, unless Jetpack natively supports it through a filter or something.

An upstream related issue:

• ​https://github.com/Automattic/jetpack/issues/13001

[mrfoxtalbot]

Thank you for linking to the upstream issue, @dd32. I added a comment there.

As much as I would like to see this implemented quickly, I understand that doing a custom extension of Jetpack is going to make it hard to maintain it and that it makes more sense to try and have this added to Jetpack itself.

Should we close this issue as wontfix then?

[dd32]

Should we close this issue as wontfix then?

Unfortunately, I think that's the best option here.

If a different workflow is wanted here, we'd be better switching away from Jetpack Forms to something else I suspect.