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

Jump to bottom

Turn current Dashboard into a PDF report #9737

Closed
gaumondp opened this issue Feb 9, 2016 · 3 comments
Closed

Turn current Dashboard into a PDF report #9737

gaumondp opened this issue Feb 9, 2016 · 3 comments
Assignees
@tsteur
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Milestone
2.16.1

Comments

@gaumondp
Copy link

gaumondp commented Feb 9, 2016

Many of my users do custom dashboards but are puzzled to recreate them in Emails/PDF reports.

Would be great to have those 2 new options :

  1. Save current Dashboard as PDF
  2. Add this Dashboard in Email Reports

What is very important is to keep "preferences" from the Dashboard, mainly numbers of rows, Flat or not, etc.
@tsteur
Copy link
Member

tsteur commented Feb 10, 2016

I like this idea a lot. See also #9351 here I also mentioned

Let a user create a custom "dashboard" / "view" in Piwik based on this export. It would be some kind of dashboard but showing it more report like. This would be directly shown in the UI

which is basically the other way around.

Export dashboards is a duplicate of #5101

@tsteur tsteur closed this as completed Feb 10, 2016
@tsteur tsteur added the duplicate For issues that already existed in our issue tracker and were reported previously. label Feb 10, 2016
@tsteur tsteur added this to the 2.16.1 milestone Feb 10, 2016
@tsteur tsteur self-assigned this Feb 10, 2016
@gaumondp
Copy link
Author

Dear @tsteur , I find it strange to see the label/milestone set to 2.16.1, I had the impression that 2.16 was LTS so no new features, only bug/security fixes... and such new features would get the 3.0 milestone.

@tsteur
Copy link
Member

tsteur commented Feb 10, 2016

I set it to 2.16.1 as I closed this issue as a duplicate and left #5101 open. So it won't be developed in 2.16.1 in this case

@labolanimichele labolanimichele mentioned this issue Dec 10, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tsteur tsteur

Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Milestone
2.16.1
Development

No branches or pull requests
2 participants
@tsteur @gaumondp