Provide an intuitive way to clear cookies and cache, and reload a website
Status
| Provide an intuitive way to clear cookies and cache, and reload a website | |
| Stage | Shelved |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | Splitting this into different features. |
{{#set:Feature name=Provide an intuitive way to clear cookies and cache, and reload a website
|Feature stage=Shelved |Feature status=` |Feature version=` |Feature health=OK |Feature status note=Splitting this into different features. }}
Team
| Product manager | ` |
| Directly Responsible Individual | Michael Verdi |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
{{#set:Feature product manager=`
|Feature feature manager=Michael Verdi |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
Approximately 20% of SUMO questions are about websites not working or loading and can be fixed by clearing cookies and cache and then reloading the website. In order to do this, you have to use the "Clear Recent History" feature, configure it to clear only cookies and cache, select a time range and, once that's done, reload the website.
People often don't discover this feature and don't know how to use it because:
- The feature isn't presented when and where the problem is
- The feature's name doesn't indicate that it will help with website connection issues
- The feature has to be configured properly to work in this instance
- After clearing cookies and cache, the additional step of reloading the website has to be performed.
What this feature would do:
- Change the Shift-Reload functionality to include clearing cookies and cache - a sort of "super-reload".
- Change the look of the reload button when shift in held down.
- Do this "super-reload" automatically when a user clicks reload 3 times in a short time span.
2. Users & use cases
- Cookies and/or website cache preventing page from loading or updating.
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
`
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=Approximately 20% of SUMO questions are about websites not working or loading and can be fixed by clearing cookies and cache and then reloading the website. In order to do this, you have to use the "Clear Recent History" feature, configure it to clear only cookies and cache, select a time range and, once that's done, reload the website.
People often don't discover this feature and don't know how to use it because:
- The feature isn't presented when and where the problem is
- The feature's name doesn't indicate that it will help with website connection issues
- The feature has to be configured properly to work in this instance
- After clearing cookies and cache, the additional step of reloading the website has to be performed.
What this feature would do:
- Change the Shift-Reload functionality to include clearing cookies and cache - a sort of "super-reload".
- Change the look of the reload button when shift in held down.
- Do this "super-reload" automatically when a user clicks reload 3 times in a short time span.
|Feature users and use cases=*Cookies and/or website cache preventing page from loading or updating. |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | Unprioritized |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | ` |
| Secondary roadmap | ` |
| Feature list | ` |
| Project | ` |
| Engineering team | ` |
{{#set:Feature priority=Unprioritized
|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=` }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}