This issue is to track low-priority work that could be time consuming but still needs to be done at some point.

• Angular router is used in the public management view
• Integration concerns of Kibana App features, especially Discover / Saved Search CSV, need to be moved to Kibana App ownership.
• Logic to flatten hits from saved search into CSV (server-side only) needs to be unified with Discover (front-end-only)
• Immediate generation of CSV is not a Reporting feature. Reporting export types should always be async/queued.
• Make print_layout an abstraction of the Dashboard PDF integration. It's just a different mode of screenshot, and the layout changes needed are specific to Dashboard.
• Translations for all log messages
• Smaller and more isolated functional tests for each visualization type.
  • Remove expectation of parallelized job running from functional tests: Reporting jobs can stack up, but don't execute in parallel.
• Automated tests on the generation APIs should validate the jobs they are queuing get completed successfully.
• Move reporting/export_types to reporting/server/export_types to follow ESLint import rule: https://github.com/elastic/kibana/blob/01dd08e/x-pack/legacy/plugins/reporting/export_types/csv_from_savedobject/server/lib/generate_csv_search.ts#L29
• Organize types in to server public common and move them to NP as much as possible
• PDF creation leads to inconsistent data model of pending jobs. PDF jobs have an internal objects structure for storing the multiple relative URLs and doing so makes the flow inconsistent with PNG, where there is a better working data model. [Reporting/Legacy] Remove reporting legacy job params compatibility shim #52539
• More unit testing and functional testing needed for PNG creation Getting flaky tests back in shape for reporting #46076