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.

Sign up for GitHub

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

[Reporting] Back off on the approach to remove support for the roles.enabled setting. #113014

Closed
tsullivan opened this issue Sep 23, 2021 · 2 comments
Closed

[Reporting] Back off on the approach to remove support for the roles.enabled setting. #113014

tsullivan opened this issue Sep 23, 2021 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead 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:medium Medium Level of Effort needs-team Issues missing a team label

Comments

@tsullivan
Copy link
Member

Kibana version: 8.0 and the latest 7.x

Removal of supporting roles.enabled is too big of a change to force into 8.0. The removal should be phased more gradually, using telemetry data for acceptance criteria.

Steps to reproduce:

  1. Start Kibana with reporting config at the defaults
  2. View a warning that roles.enabled support is going away in 8.0: https://github.com/elastic/kibana/pull/100427/files#r714993527

Expected behavior:

Granting reporting privilege through a "reporting_user" role will not be supported starting in 8.0 in a future version.
@tsullivan tsullivan added the bug Fixes for quality problems that affect the customer experience label Sep 23, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 23, 2021
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 23, 2021
@tsullivan tsullivan mentioned this issue Sep 23, 2021
Merged
3 tasks
@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 Oct 27, 2021
@tsullivan
Copy link
Member Author

Closed via #114950

@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Oct 27, 2021
@sophiec20 sophiec20 added (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Feature:Reporting:Framework Reporting issues pertaining to the overall framework and removed (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
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead 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:medium Medium Level of Effort needs-team Issues missing a team label
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tsullivan @sophiec20 @elasticmachine