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

Allow configuring the link to "Report Error" #17287

Closed
rijkvanzanten opened this issue Jan 24, 2023 Discussed in #17259 · 1 comment · Fixed by #21174
Closed

Allow configuring the link to "Report Error" #17287

rijkvanzanten opened this issue Jan 24, 2023 Discussed in #17259 · 1 comment · Fixed by #21174
Assignees

Comments

@rijkvanzanten
Copy link
Member

There's two main places in the app where the user is prompted to report an error: In unexpected error dialogs and in the Settings sidebar. For these two locations, we should allow the system admin to configure what this link does. This allows the admin to have the user notify them through email (or elsewhere) instead of having them be sent over to GitHub (where they might not have an account / aren't familiar).

The configuration should be done in Project Settings. The entered string will be used in the href for the report error buttons. This allows mailto: and other app links to be used as well. The field should accept a template string that's rendered with micromustache. The variables that should be available in the context of the template are:

  • error: The Error object that caused the error dialog
  • route: The current vue-router context
  • user: Current user (from the userStore)
  • role: Current role (from the roleStore)
  • navigator: Browser's navigator object

This would allow the template to be something like https://example.com/report?ua={{navigator.userAgent}}&page={{route.fullPath}}&error={{error}}

Discussed in #17259

Originally posted by u12206050 January 21, 2023
Screenshot 2023-01-21 at 10 53 07

Currently this "Report Error" button opens up an issue on the Directus repo.

Could it rather be configurable such that it opens an issue on the project's repo first, such that it could first be debugged there before involving and burdening the Directus Team with all such (possibly minor) issues?

@github-actions
Copy link

Linear: ENG-571

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants