This is the first step of cross tracker search. It's almost not functional at all but set the bases for future work.

We get:

• Step A - A new widget
  • For user and project dashboards
  • An angular 1.6 application
  • With an empty state as nothing was selected
• Step B - The widget allows to select a limited number of trackers in several projects
  • The limit is set to 10 trackers
  • The selector is made of 2 simple select boxes
    • They use the /projects/ REST route that need to be modified to allow to search on project that I'm member of. Both query and representation must be adapted to add this information
  • The selection is saved via REST calls attached to cross tracker feature (it's not widget preference). Needed routes
    • OPTION|POST /xtracker_reports/
    • OPTION|GET|PUT /xtracker_reports/:id
  • Edit of the query is done inline
  • On save the trackers and projects that are no longer visible are removed
  • When a project or a tracker is deleted, the widgets are cleaned
  • On widget delete, remove the report
• Step C - Run the query and display results
  • Query done via REST
    • OPTION|GET /xtracker_reports/:id/content
  • Result presented as a tlp table with fixed columns (like artifact folder) and only the first 30 results
• Step D - Widget inheritnace
  • On project clone (template) widget is inherited with its configuration