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] Reporting info panel touch ups #120617

Merged
merged 22 commits into from
Dec 15, 2021

Conversation

jloleysens
Copy link
Contributor

@jloleysens jloleysens commented Dec 7, 2021

Summary

Closes #118247

Addresses the points raised the issue and introduces new structure to the flyout. Notable changes:

  • Added subsections for the details to live inside of helping the reader scan and find the exact info they are looking for
  • Moved warnings and errors to a callout at the top of the flyout. It's important that this information be highlighted here as it is one the main reasons a user might to the flyout.
  • Move the report title to the title of the flyout, was "Report info"
  • Removed some fields: Export type, Layout, Dimensions (now to separate fields with units denoted),

How to test

  1. Start Kibana & ES on basic
  2. Go to License management and start a trial license
  3. Generate a PNG/PDF report in dashboard
  4. Go the reporting management UI in Stack Management and view the report flyout by clicking on the name of a report

Release note

We introduced a new structure to the report details flyout to help readers get to the information they want faster.

Screenshots

Screenshots

{D578EF52-04B0-49AE-8610-F30BDDEC6219}

With warnings

Screenshot 2021-12-07 at 14 44 17

With errors

Screenshot 2021-12-14 at 11 04 29

With errors and warnings

Screenshot 2021-12-07 at 14 39 54

@jloleysens jloleysens added release_note:enhancement (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:Reporting Services v8.1.0 labels Dec 7, 2021
@jloleysens jloleysens requested a review from tsullivan December 7, 2021 14:18
@jloleysens
Copy link
Contributor Author

@elasticmachine merge upstream

@jloleysens jloleysens marked this pull request as ready for review December 8, 2021 15:16
@jloleysens jloleysens requested review from a team as code owners December 8, 2021 15:16
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@jloleysens
Copy link
Contributor Author

@elasticmachine merge upstream

Copy link
Member

@tsullivan tsullivan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a few minor suggestions

Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>
Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>
@jloleysens
Copy link
Contributor Author

@elasticmachine merge upstream

Copy link
Member

@tsullivan tsullivan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@gchaps gchaps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to add more spacing between the title "Timestamps" and "Time zone"? It seems a little tight.

}}
>
{i18n.translate('xpack.reporting.reportInfoFlyout.openInKibanaAppButtonLabel', {
defaultMessage: 'Open in Kibana App',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really have the context for this text, but can it be: Open in Kibana

If you do include app, it should be lower case.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Open in Kibana" sounds good!


hasScreenshot && {
title: i18n.translate('xpack.reporting.listing.infoPanel.dimensionsInfoHeight', {
defaultMessage: 'Height (in pixels)',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are the parens needed? "Size in bytes" does not contain parens.

},
hasScreenshot && {
title: i18n.translate('xpack.reporting.listing.infoPanel.dimensionsInfoWidth', {
defaultMessage: 'Width (in pixels)',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment about the parens. Does this work:

Width in pixels

@@ -431,10 +429,7 @@ class ReportListingUi extends Component<Props, State> {
defaultMessage: 'Open the Kibana App where this report was generated.',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
defaultMessage: 'Open the Kibana App where this report was generated.',
defaultMessage: 'Open the Kibana app where this report was generated.',

@jloleysens
Copy link
Contributor Author

Thanks for the review @gchaps ! I think I've addressed your points.

Is it possible to add more spacing between the title "Timestamps" and "Time zone"? It seems a little tight.

Great idea, updated, see the screenshot.

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
reporting 56.3KB 58.0KB +1.7KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
reporting 41.8KB 42.1KB +260.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

Copy link
Contributor

@gchaps gchaps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jloleysens jloleysens merged commit d213263 into elastic:main Dec 15, 2021
@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label Dec 15, 2021
@jloleysens jloleysens deleted the reporting/info-panel-touch-ups branch December 15, 2021 09:20
TinLe pushed a commit to TinLe/kibana that referenced this pull request Dec 22, 2021
* changed info -> summary and combined maximum attempts and attempts field

* added spaceId if it is there to job info

* moved space id to job details section

* moved processing and job info into a single array

* wip, introduced a new structure to the flyout for easier visual parsing. still need to re-introduce errors and deprecated report types in the new structure

* remove unnecessary div

* added warnings and errors to callout and cleaned up comments

* remove unused functionality and introduce date formatting per advanced settings format

* remove unused import

* remove unused i18n

* refactor check for info.max_attempts in flyout content

Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>

* update info.lyout.dimensions.height to be Math.ceiled

Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>

* update info.lyout.dimensions.width to be Math.ceiled

Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>

* lint and remove bad suggestion commit

* added actions button to flyout, in flyout footer

* create a little bit more breathing room for the section titles

* added logic to disable the action buttons in the flyout when the actions are not ready

* update copy per feedback

* added basic tests for the actions menu in the flyout

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>
jloleysens added a commit to jloleysens/kibana that referenced this pull request Apr 28, 2022
* changed info -> summary and combined maximum attempts and attempts field

* added spaceId if it is there to job info

* moved space id to job details section

* moved processing and job info into a single array

* wip, introduced a new structure to the flyout for easier visual parsing. still need to re-introduce errors and deprecated report types in the new structure

* remove unnecessary div

* added warnings and errors to callout and cleaned up comments

* remove unused functionality and introduce date formatting per advanced settings format

* remove unused import

* remove unused i18n

* refactor check for info.max_attempts in flyout content

Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>

* update info.lyout.dimensions.height to be Math.ceiled

Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>

* update info.lyout.dimensions.width to be Math.ceiled

Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>

* lint and remove bad suggestion commit

* added actions button to flyout, in flyout footer

* create a little bit more breathing room for the section titles

* added logic to disable the action buttons in the flyout when the actions are not ready

* update copy per feedback

* added basic tests for the actions menu in the flyout

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>
(cherry picked from commit d213263)

# Conflicts:
#	x-pack/plugins/reporting/public/lib/job.tsx
#	x-pack/plugins/reporting/public/management/components/report_info_flyout_content.tsx
#	x-pack/plugins/translations/translations/ja-JP.json
#	x-pack/plugins/translations/translations/zh-CN.json
jloleysens added a commit that referenced this pull request Apr 29, 2022
* [Reporting] Reporting info panel touch ups (#120617)

* changed info -> summary and combined maximum attempts and attempts field

* added spaceId if it is there to job info

* moved space id to job details section

* moved processing and job info into a single array

* wip, introduced a new structure to the flyout for easier visual parsing. still need to re-introduce errors and deprecated report types in the new structure

* remove unnecessary div

* added warnings and errors to callout and cleaned up comments

* remove unused functionality and introduce date formatting per advanced settings format

* remove unused import

* remove unused i18n

* refactor check for info.max_attempts in flyout content

Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>

* update info.lyout.dimensions.height to be Math.ceiled

Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>

* update info.lyout.dimensions.width to be Math.ceiled

Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>

* lint and remove bad suggestion commit

* added actions button to flyout, in flyout footer

* create a little bit more breathing room for the section titles

* added logic to disable the action buttons in the flyout when the actions are not ready

* update copy per feedback

* added basic tests for the actions menu in the flyout

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tim Sullivan <tsullivan@users.noreply.github.com>
(cherry picked from commit d213263)

# Conflicts:
#	x-pack/plugins/reporting/public/lib/job.tsx
#	x-pack/plugins/reporting/public/management/components/report_info_flyout_content.tsx
#	x-pack/plugins/translations/translations/ja-JP.json
#	x-pack/plugins/translations/translations/zh-CN.json

* resolved merge conflicts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead release_note:enhancement v8.1.0 v8.2.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Reporting] Touch up content in the report job info side panel should have more content
6 participants