Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Reporting/Design] Add a new Export menu item & update Reporting table #39620

Closed
7 tasks
ryankeairns opened this issue Jun 25, 2019 · 8 comments · Fixed by #111412
Closed
7 tasks

[Reporting/Design] Add a new Export menu item & update Reporting table #39620

ryankeairns opened this issue Jun 25, 2019 · 8 comments · Fixed by #111412
Labels
enhancement New value added to drive a business result Feature:Reporting:Framework Reporting issues pertaining to the overall framework impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:x-large Extra Large Level of Effort needs-team Issues missing a team label

Comments

@ryankeairns
Copy link
Contributor

Describe the feature:
In an effort to raise awareness of Reporting capabilities, we discussed a couple of changes that better align with user expectations:

Add 'Export' menu item

Split out export-related actions from the Share menu and place then in a new top-level 'Export' menu item. This would contain links like 'Export to CSV', 'Export to PNG', 'Export to PDF', etc., while the Share menu would retain links for 'Get embed code' and 'Get permalink'.

  • Add 'Export' menu item to Discover
  • Add 'Export' menu item to Dashboard

Marvel prototype

👉 https://marvelapp.com/8g51848/screen/58300225

Preview snapshots from Marvel prototype 👆

Screenshot 2019-06-25 15 07 21

Screenshot 2019-06-25 15 07 27

Screenshot 2019-06-25 15 07 33

Improve the Reporting table

Update the Management > Reporting table view to more clearly present information about completed reports. Changes include:

  • Use application icon (instead of text) to identify source and save horizontal space
  • Make the report title/name clickable
  • Use an icon to convey status and place it next to the related datetime value
  • Display the report format (CSV, PNG, PDF), and make it clickable
  • Make the column headers sortable

Marvel prototype

👉 https://marvelapp.com/8g51848/screen/58293451

Preview snapshots from Marvel prototype 👆

Screenshot 2019-06-25 15 04 15

@ryankeairns ryankeairns added the (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead label Jun 25, 2019
@tsullivan
Copy link
Member

I love all the Reporting table improvements!

@tsullivan
Copy link
Member

The UI changes proposed here would solve the related issue: #45053

@joelgriffith
Copy link
Contributor

I'm definitely excited to get this in

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@tsullivan
Copy link
Member

NOTE: The changes to the Export menus are under the ownership of the apps that want to integrate with Reporting. On the UI side, the Reporting devs manage just the job listing of the reports.

@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@bmcconaghy bmcconaghy added Team:Reporting Services and removed Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Dec 20, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@tsullivan
Copy link
Member

Hi, quick update: we will have the ability to delete reports before we are taking on this issue: #60077

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@tsullivan tsullivan removed Team:Reporting Services Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Dec 17, 2020
@tsullivan tsullivan added Team:Reporting Services enhancement New value added to drive a business result labels Feb 25, 2021
@exalate-issue-sync exalate-issue-sync bot added the impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. label May 13, 2021
@exalate-issue-sync exalate-issue-sync bot added the loe:small Small Level of Effort label May 13, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Jun 1, 2021
@exalate-issue-sync exalate-issue-sync bot changed the title [Reporting] Add a new Export menu item & update Reporting table [Reporting/Design] Add a new Export menu item & update Reporting table Jun 1, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:weeks and removed loe:medium Medium Level of Effort labels Sep 3, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Oct 21, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:x-large Extra Large Level of Effort and removed loe:weeks labels Nov 24, 2021
@sophiec20 sophiec20 added Feature:Reporting:Framework Reporting issues pertaining to the overall framework and removed (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead (Deprecated) Team:Reporting Services labels Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Reporting:Framework Reporting issues pertaining to the overall framework impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:x-large Extra Large Level of Effort needs-team Issues missing a team label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants