Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "Copy story data" button to error boundary screen #11394

Closed
adamdunnage opened this issue Apr 29, 2022 · 4 comments · Fixed by #12554
Closed

Add "Copy story data" button to error boundary screen #11394

adamdunnage opened this issue Apr 29, 2022 · 4 comments · Fixed by #12554
Assignees
Labels
Group: Settings P2 Should do soon Type: Enhancement New feature or improvement of an existing feature Type: Support Questions & Feedback from support escalation.

Comments

@adamdunnage
Copy link

Feature Description

It would be useful to add an option for web stories users to export a story as a JSON file to provide to support for debugging.

This would simply be an export function and would not allow users to export/import story data. This would allow us in the support forums to request this data from the user to help with our troubleshooting of their story issues.

The feature would work much like other plugins with an export settings feature.

Alternatives Considered

  1. This could be included in the Site Health Information rather than adding an option for the user to download a JSON file.

  2. An alternative to this would be to continue using the process we have in place which is less efficient but does work. This improvement would eliminate many steps in the process making everything much more efficient.

Additional Context

N/A

@adamdunnage adamdunnage added Type: Enhancement New feature or improvement of an existing feature Group: Settings Type: Support Questions & Feedback from support escalation. labels Apr 29, 2022
@swissspidy
Copy link
Collaborator

Related: #4357

The feature would work much like other plugins with an export settings feature.
This could be included in the Site Health Information rather than adding an option for the user to download a JSON file.

Just noting that the difference there is that these are for site-wide debugging information, not for exporting a single piece of content.

@swissspidy
Copy link
Collaborator

I was just thinking, would a small Chrome extension perhaps help with this too? Then the user can share their story URL, you open the story and the Chrome extension would allow you to download the story data for it.

@adamdunnage
Copy link
Author

I was just thinking, would a small Chrome extension perhaps help with this too? Then the user can share their story URL, you open the story and the Chrome extension would allow you to download the story data for it.

That could certainly help in this process and I guess takes away the reliance on the user having to get that information to pass on to us.

@swissspidy swissspidy added the P3 Nice to have label Sep 16, 2022
@swissspidy
Copy link
Collaborator

This functionality is especially useful when there's an editor crash, so we could add this as a button below the error crash message.

@swissspidy swissspidy added Pod: WP P2 Should do soon and removed P3 Nice to have labels Oct 2, 2022
@swissspidy swissspidy removed their assignment Oct 17, 2022
@swissspidy swissspidy changed the title Export story as JSON setting for users to provide for support troubleshooting Add "Copy story data" button to error boundary screen Oct 26, 2022
@timarney timarney self-assigned this Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Group: Settings P2 Should do soon Type: Enhancement New feature or improvement of an existing feature Type: Support Questions & Feedback from support escalation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants