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

Move reporting from management application into the user setting #36141

Closed
AlonaNadler opened this issue May 6, 2019 · 13 comments
Closed

Move reporting from management application into the user setting #36141

AlonaNadler opened this issue May 6, 2019 · 13 comments
Labels
enhancement New value added to drive a business result Feature:Reporting:Framework Reporting issues pertaining to the overall framework impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort needs-team Issues missing a team label

Comments

@AlonaNadler
Copy link

Describe the feature:
Currently, the reporting is in the management application, the management application has more and more capabilities to manage the entire stack and becomes a place for admins, where reporting is a per-user page where end user sees their report.
In addition with Feature Control, admins will likely want to hide management application completely to many of the users and having to reporting page there will prevent some of them from doing so.

I suggest we move the reporting into the user setting on the page top right
image

It will be a more accessible location to look for users reports.
Since only security clusters have the user icon, and basic users have CSV reports but not security, I suggest to add the user icon on the top right to for Basic users as well so end users can get to their reports from the same place whether they have security or not.

cc: @joelgriffith @elastic/kibana-design

@AlonaNadler AlonaNadler added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label May 6, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@joelgriffith joelgriffith added the (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead label May 7, 2019
@joelgriffith
Copy link
Contributor

@AlonaNadler do you think this will require changes to the URL structure? Hopefully this will be an easy move, however if we change the structure or our URL's it might be tough to handle with bookmarking and other external tools

@AlonaNadler
Copy link
Author

I'm not sure, I hope it doesn't require to change the URL. In general, I don't think users bookmark the reporting page but there might be other use cases that I haven't considered. How can we check this? can it break some of the reports history?

@cchaos
Copy link
Contributor

cchaos commented May 8, 2019

Can you just make sure the old url's redirect to the "new" page?

@kobelb
Copy link
Contributor

kobelb commented May 10, 2019

Reporting can technically be enabled when Security isn't, so the "user profile" in the top navigation isn't always there. Would it make sense to add a dedicated "Reporting" top nav item in this situation?

@AlonaNadler
Copy link
Author

AlonaNadler commented May 10, 2019

How about adding a user profile for basic when there is no security ?

@kobelb
Copy link
Contributor

kobelb commented May 20, 2019

How about adding a user profile for basic when there is no security ?

That seems somewhat awkward, since there isn't a user logged in. I'm not sure what we'd display here.

@AlonaNadler
Copy link
Author

Since each user sees only their own report, it will say "my reports" in the future I can see other things we can add into it like settings and other preferences

@kobelb
Copy link
Contributor

kobelb commented May 20, 2019

Since each user sees only their own report, it will say "my reports" in the future I can see other things we can add into it like settings and other preferences

When security isn't enabled, all users see the same reports. There is no "my reports" view in this situation, it's just "everyone's reports".

@timroes timroes added Team:Stack Services and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jul 18, 2019
@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)

@elasticmachine
Copy link
Contributor

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

@tsullivan
Copy link
Member

This issue is closely related to #78478 where we talk about moving Reporting to an upcoming "notification service" UI.

@AlonaNadler does reporting truly need to be under the "user setting" or should we keep waiting for the notification center? I prefer the latter.

RFC of Notification Service: #90297

@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels May 13, 2021
@exalate-issue-sync exalate-issue-sync bot removed the loe:small Small Level of Effort label Jun 1, 2021
@exalate-issue-sync exalate-issue-sync bot added the loe:medium Medium Level of Effort label Jun 1, 2021
@tsullivan
Copy link
Member

Closing as duplicate of #78478

@exalate-issue-sync exalate-issue-sync bot added loe:small Small Level of Effort and removed loe:medium Medium Level of Effort labels Dec 9, 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:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort needs-team Issues missing a team label
Projects
None yet
Development

No branches or pull requests

10 participants