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.

Sign up for GitHub

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

Jump to bottom

We should document troubleshooting steps for when Element is broken #8998

Open
turt2live opened this issue Feb 28, 2019 · 2 comments
Open

We should document troubleshooting steps for when Element is broken #8998

turt2live opened this issue Feb 28, 2019 · 2 comments
Labels
A-Developer-Experience A-Documentation T-Task Tasks for the team like planning

Comments

@turt2live
Copy link
Member

turt2live commented Feb 28, 2019 •
edited
Loading

More for the support people trying to get logs out of people. Things like mxReactSdkConfig.bug_report_endpoint_url = 'https://riot.im/bugreports/submit'; mxSendRageshake('It dun broke'); change the bug report URL and send a rageshake, for instance
@turt2live turt2live mentioned this issue Feb 28, 2019
Closed
@lampholder lampholder added T-Task Tasks for the team like planning P1 A-Documentation labels Mar 4, 2019
@lampholder
Copy link
Member

Where's a good place to put this sort of documentation?

@turt2live
Copy link
Member Author

A TROUBLESHOOTING.md doesn't sound like the worst idea

@grimhilt grimhilt mentioned this issue Jul 6, 2022
Merged
@MadLittleMods MadLittleMods changed the title We should document troubleshooting steps for when Riot is broken We should document troubleshooting steps for when Element is broken Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Developer-Experience A-Documentation T-Task Tasks for the team like planning
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@MadLittleMods @turt2live @lampholder