Report Error should first be reported at project level

[u12206050]

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?

[rijkvanzanten]

Good one! What would be a good way to configure the report error interaction? Maybe a field in project-settings? If we leave it as just a link, you could also do a mailto: address I suppose, which would be a nice way to support both email and other things 🤔

[paescuj]

Good question! I think it would indeed require a dedicated field to customize this link.
In order to be really useful, it would also require a mapping of error / context data to params, for example by allowing a templated link like https://my-custom-report-link.com/issue?error={{error}}&version={{directusVersion}} (would also work for mailto:).

[u12206050]

That sounds good. Either in env or in project settings.

Shall I make a PR or is it pretty easy for core team to do?

[rijkvanzanten]

Is that an exhaustive list? Anything else we should spec out? I'm wondering if there's a more "standard" set that we could rely on so we don't have to document / come up with yet another object structure that's vaguely similar 🤔

Maybe we could say:

• Context
  • Browser UA
  • Current Page
• Error
• User
  • (Anything from the user object / user store)
• Role
  • (Anything from the role object / role store)

I think Role might be an important one here, as it's not unlikely that errors are thrown due to a specific permissions set that the admin needs to reproduce

[u12206050]

Correct, role is also very good to have.
Datetime is also very good to have I guess and timezone since the user using it might be in different timezone.

[u12206050]

I wonder how much data we can actually send especially if it is being injected into href of mailto:

[rijkvanzanten]

Good thinking! Seeing that we're rendering this template out client side, maybe instead of "context" with predefined keys we should "just" make navigator available? That way you could set things like {{ navigator.userAgent }} 🤔

I wonder how much data we can actually send especially if it is being injected into href of mailto:

What do you mean? It might get a little finicky in configuration, but you can pre-fill a whole email body in a mailto: link with query params, so in theory you should be able to send whatever you want? 🤔

[u12206050]

Ok, yeh sure. Think mailto is safest, since the user could be offline actually.

[rijkvanzanten]

This feature request has been accepted and is queued to be implemented! You can follow along with the progress here: #17287