-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Allow users to manage reports #17878
Comments
Original comment by @tbragin: I think that in addition to deletion, we should consider other report management tasks, such as searching, sorting, and filtering. Making the title more general to reflect that. |
Original comment by @tbragin: via @bohyun-e from LINK REDACTED
|
Original comment by @tbragin: One thing I noticed playing with managing report history via Sense is that right now the way the reporting index is organized, one has to either delete the whole weekly index or delete individual reports by its Elasticsearch document id ( From a workflow perspective, it seems natural to want to filter a long report history by report title before determining which reports to delete, but for that we'll have to index the right fields with correct mappings. Note: If we don't make the data-level changes to enable this for 4.6, and decide to do this in 5.0, we'll may have to ask users to delete their report history on migration or think through report index versioning. Representative report document for reference:
mapping for payload:
|
Requested in #19752 is ability to rename the file in management. |
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
Any news on that? Would it be possible to release at least the delete report button? UPDATE: Sorry, now I saw that I can select the report and remove it. Thanks. |
Pinging @elastic/kibana-app-services (Team:AppServices) |
Closing for #81544 |
Original comment by @w33ble:
The async queue UI brought in LINK REDACTED could use a lot more controls. For example:
The text was updated successfully, but these errors were encountered: