Send Bug Report workflow requiring login

[codefarmer]

[Splitting the bug reporting part of the thread from Delete all ancestors and events related to a specific person - #15 by takaji to avoid hijacking that thread]

@sam888
It looks like the Send Bug Report wizard sends users directly to the page that requires a choice to be made between Gramps and Feature Requests. For first-time users this isn’t possible until they log in (and they may not have an account).

We can put a note on the Send Bug Report wizard to say “You will need to log in (or create an account) to submit a bug report”, or change the description for the file bug report button to “Use this button to start a web browser and file a bug report by logging in to the Gramps bug tracking system (you can create an account if you don’t have one).”

In addition to that, is it possible to add a hint on the web page to indicate that login is required in order to choose the project

When a user arrives at that page, it’s likely an exception in Gramps that leads them there, so could the page be automatically be populated with the Gramps project as the choice?

[takaji]

Yes, I think that would be a suitable solution.

However: I understand that it’s important to be able to contact a user to follow-up about a bug report or request more information, but there’s also some significant roadblocks in place to collecting a bug report. Firstly, as a user I need to go through a few pages in the bug report pop-up, and then I need to create an account to report the bug. Would it not be possible to allow bug reporting without creating an account? There could, for instance, be a required field where the submitter enters their email address which could then be used to follow-up.