Improve the experience of GH issue creation across the app.

[ccanash]

Define how to improve the experience of GH issue creation across the app. Some examples of improvement can include:

1. Add the possibility to create a GH issue from additional pages in the app. For example: about a report, about 1 test, about a test plan as a whole,  about a specific command within a test)
2. Improve how to display existing issues. It currently it mixes open and closed issues.
3. Explore having existing issues appear elsewhere than → in the same places where we are adding the possibility to submit an issue for example in candidate review (have a link so that user know that there are existing issues and can check what they are) 

[howard-e]

1. Add the possibility to create a GH issue from additional pages in the app. For example: about a report, about 1 test, about a test plan as a whole,  about a specific command within a test)

We can re-use the “Raise an Issue” button to instead present a secondary set of radio options in a dialog (or similar) depending on the context:

• On Test Run:

  1. Raise an Issue -> Select “… about the test” (current default)
  2. Raise an Issue -> Select “… about a specific command” (selecting this now shows another list for which command (or commands) are problematic
  3. Raise an Issue -> Select “… about the test plan”
  4. In addition to no.3, the Test Plan info shown at the top of the Test Run should also show and link to the correct test plan version’s review page and there should also be a “Raise an Issue” button on that page

• On Test Review Page:

  1. Include “Raise an Issue” button under GitHub Issues table and given the context, that covers the entire Test Plan (this will require a template addition/change to highlight this is for the entire test plan)

• On Test Plan’s Report Page:

  1. Include “Raise an Issue” button under the Metadata section. We can allow the user to select a specific combination of the listed AT + Browser reports that are present, otherwise we can assume it covers the entire report (this will require a template addition/change to highlight the issue is for a published report)

• On Test Plan’s AT + Browser Report Page:

  1. We can re-use the existing “Raise an Issue” buttons here in the same way they are being used on the Test Run page (this will require a template addition/change to highlight the issue is for a published report)

2. Improve how to display existing issues. It currently it mixes open and closed issues.

This would have been recently covered by #1266 and #1269.

3. Explore having existing issues appear elsewhere than → in the same places where we are adding the possibility to submit an issue for example in candidate review (have a link so that user know that there are existing issues and can check what they are)

Can do!