google / google/site-kit-wp

Messaging on key metrics panel

Open
#12,709 0 comments 0 reactions 0 assignees View on GitHub
Type: Bug
Dominant language
JavaScript
Stars
1.4k
Forks
384
Avg merge
4d 14h
Merged PRs (30d)
77

Description

## Bug Description

I noticed on edge case. That said, it might not be relevant in the future with the SFR rollout but it could impact existing sites.
But here's the deal:
- On a site without SFR, I connect analytics and the Key metric tiles
- The key metric section appears in settings
- I disconnect the analytics module
- On the dashboard, the key metrics section will have the 'change metrics' CTA which will state that user can change their personalised goals or deactivate widget in settings.
- Clicking on the 'Settings' hyperlink leads to settings but there is no Key metrics section there
By right it should be there if we are directing user there. Unless we'd need to hide the 'Change metrics' CTA then.

Video is attached for reference.

https://github.com/user-attachments/assets/448348e4-d5ef-4c70-9168-59e1ead32430

## Steps to reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

## Screenshots

## Additional Context

- PHP Version:
- OS: [e.g. iOS]
- Browser: [e.g. chrome, safari]
- Plugin Version: [e.g. 22]
- Device: [e.g. iPhone6]

---------------

_Do not alter or remove anything below. The following sections will be managed by moderators only._

## Acceptance criteria

*

## Implementation Brief

* [ ]

### Test Coverage

*

## QA Brief

*

## Changelog entry

*

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the dashboard and settings sequence described: connect analytics, configure Key metrics, disconnect analytics, then follow the “change metrics” CTA’s Settings link. Inspect the Key metrics panel and settings entry points to determine whether the link should expose the section or the CTA should be hidden; done means the resulting navigation and available controls are consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
analytics, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.