Forms: Add Feedback link to admin bar

[enejb]

This PR adds a quick link to the admin bar if the user is visiting a single page or post on the frontend and is someone that should have access to the dashboard.

It only shows up if we are also going to render the form.

On single page with a form on.

On a single page without a form.

To disable the newly added quick_link menu you can
do the following:

function my_plugin_prefix_disable_jetpack_contact_admin_bar( $html ) {
	remove_action( 'admin_bar_menu', array( 'Automattic\Jetpack\Forms\ContactForm\Contact_Form', 'add_quick_link_to_admin_bar' ), 500 );
	return $html;
}
add_filter( 'jetpack_contact_form_html', 'my_plugin_prefix_disable_jetpack_contact_admin_bar' );

Proposed changes:

• Adds the Feedback quick link to the admin bar.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

No

Testing instructions:

• As a logged in editor or admin user visit a single page or post that has a form on. Notice that you see the feeedback link in the Admin bar.
• As a visitor notice that you don't see it.
• Pages without a form shouldn't display the feedback link. The link should take you to your preferred feedback view ( classic or modern)

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the add/form-responses-to-admin-bar branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/form-responses-to-admin-bar

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: April 1, 2025
  • Code freeze: March 30, 2025

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[ilonagl]

Hey @enejb 👋,

This is a great and quick solution! 🙌

I wonder about the naming and whether it's clear enough, maybe something like 'Form Feedback' (adding Form) could help to clarify what this is (especially for new users)? It takes a bit more space tho.

[jp-launch-control]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/packages/forms/src/contact-form/class-contact-form.php	539/788 (68.40%)	-1.24%	14 💔

Full summary · PHP report · JS report

_{If appropriate, add one of these labels to override the failing coverage check: Covered by non-unit tests Use to ignore the Code coverage requirement check when E2Es or other non-unit tests cover the code Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR I don't care about code coverage for this PR Use this label to ignore the check for insufficient code coveage.}

[simison]

@crisbusquets @Copons any needs to coordinate this with anyone from Dotcom? Note that this Only applies to pages with forms on them.

@enejb what happens if form is in footer/sidebar? It would be too much to render on every page.

@ilonagl thoughts on what the link copy should be?

[simison]

@enejb how's the mobile version?

[enejb]

@simison

what happens if form is in footer/sidebar? It would be too much to render on every page.

If we are a single (page or post or any other post type) - we would show the link to the form responses. Even if it is a shortcode or a widget.

In the current version we only link users to the default form responses page. No source attribute. But ideally we would send the user to the correct one.

how's the mobile version?

The mobile version doesn't show the link at all.

See

[crisbusquets]

Oh, hello Zap! ⚡

From what I understand, we want to give site admins a quick link to check replies for a specific form, right?

Not sure how feasible that would be, but could we explore rendering the block differently so the link appears with the form? The Feedback link in its current spot seems easy to miss 🤔

[simison]

Admin area felt more fitting semantically since that's where other admin stuff goes: also where you edit current page, or check stats for the current post.

Also nice not to keep the page as WYSIWYG as possible with editor and no extra things appearing, potentially messing up with page layout.

[aaronrobertshaw]

This is testing as advertised for me 👍

✅ Form responses link shows on individual posts and pages
✅ New link isn't displayed on index pages or mobile

I have a few minor questions and thoughts I've left as inline comments.

Edit: Looking at this screenshot again, the lack of an icon for "Form responses" stuck out. Are there plans for a follow-up addressing this?

[ilonagl]

@ilonagl thoughts on what the link copy should be?

Form responses that is currently used is the most straightforward one, and keeps things consistent with our namings (img reference below). This reduces guesswork and makes label recognition easier for users.

I agree with @aaronrobertshaw that having an icon would help keep the links consistent with the rest. Can we reuse the existing Feedback icon from the sidebar? It’s not ideal, but it maintains consistency for now, and we can update both instances when we have a better one.

[enejb]

The updates admin bar with the icon.

[aaronrobertshaw]

This is getting closer, thanks for the iterations here @enejb 👍

I think we can clean up some of the icon styles, then it should be ready to go.

I've tested the current PR state along with my suggested tweak below and visually they are the same.

[crisbusquets]

Sorry I'm late. Did you implement tracking here? This way we'll be able to know how many people click that option 👀