Skip to content

Make page titles more consistent for Overview, Alerts, Rules, Rule Detail and Cases pages#146150

Merged
CoenWarmer merged 5 commits intoelastic:mainfrom
CoenWarmer:bug/142859-inconsistent-page-title-styling-new
Nov 24, 2022
Merged

Make page titles more consistent for Overview, Alerts, Rules, Rule Detail and Cases pages#146150
CoenWarmer merged 5 commits intoelastic:mainfrom
CoenWarmer:bug/142859-inconsistent-page-title-styling-new

Conversation

@CoenWarmer
Copy link
Copy Markdown
Contributor

@CoenWarmer CoenWarmer commented Nov 23, 2022

Closes #142859.

Summary

This PR updates the Observability Overview, Alerts, Rules, Rule Details and Cases pages so their headers are more consistent with one another.

Previously:

203355680-f6f88a6f-7fe8-4653-aeab-f464e0d90414.mov

With this PR:

Screen.Recording.2022-11-22.at.16.44.38.mov

@CoenWarmer CoenWarmer requested a review from a team as a code owner November 23, 2022 14:00
@CoenWarmer CoenWarmer requested a review from a team November 23, 2022 14:00
@CoenWarmer CoenWarmer requested review from a team as code owners November 23, 2022 14:00
@CoenWarmer CoenWarmer changed the title Fix page title for Overview page Make page titles more consistent for Overview, Alerts, Rules, Rule Detail and Cases pages Nov 23, 2022
@CoenWarmer CoenWarmer added v8.6.0 release_note:skip Skip the PR/issue when compiling release notes labels Nov 23, 2022
Copy link
Copy Markdown
Member

@cnasikas cnasikas left a comment

Choose a reason for hiding this comment

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

Cases changed LTGM!

Copy link
Copy Markdown
Contributor

@formgeist formgeist left a comment

Choose a reason for hiding this comment

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

LGTM 👍 Thanks for fixing these inconsistencies

@kibana-ci
Copy link
Copy Markdown

💚 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
observability 495.9KB 495.9KB -41.0B
Unknown metric groups

ESLint disabled in files

id before after diff
osquery 1 2 +1

ESLint disabled line counts

id before after diff
enterpriseSearch 19 21 +2
fleet 59 65 +6
osquery 109 115 +6
securitySolution 443 449 +6
total +20

Total ESLint disabled count

id before after diff
enterpriseSearch 20 22 +2
fleet 68 74 +6
osquery 110 117 +7
securitySolution 520 526 +6
total +21

History

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

/>
</EuiButton>
),
<EuiButton
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This reduces the 'pop in' effect on this page where buttons suddenly jump to the left

Copy link
Copy Markdown
Member

@maryam-saeidi maryam-saeidi Nov 24, 2022

Choose a reason for hiding this comment

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

I like this improvement, just wondering if you checked with @maciejforcone whether disabling the button is the approach that we use in Kibana or do we need to use a loader for the title instead until we have the authorization information. (For the cases that the user actually doesn't have access)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Well @maciejforcone, what do you think?

Copy link
Copy Markdown

@maciejforcone maciejforcone Nov 24, 2022

Choose a reason for hiding this comment

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

I checked how it works in Rules. So we do show "manage rules" always, but when user gets there and has no permissions to Create rule - then we don't show the button. But for example in Monitor view we show the button, but later in form we show the message "permissions needed".
image
image

For some actions we also show disabled button
image

So looks like we don't have a common pattern for that yet. I'd stick with what we have for now - showing the button, and then in form we show the info of missing permissions. And in case when there is instant action like this toggle:
image
the button can be disabled, with missing permissions info on hover.

Copy link
Copy Markdown
Contributor Author

@CoenWarmer CoenWarmer Nov 24, 2022

Choose a reason for hiding this comment

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

Ok, @maciejforcone agrees that a less jumpy UI is better, so the fix in this PR is good. @maryam-saeidi hope this answers your question.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

And to the question of loader vs element - less jumps is always better, so I like how @CoenWarmer solved that.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@maciejforcone Thanks for the input, the loader option was for the whole page/title (not the button). I think I saw a similar approach on the cases page if I am not mistaken, so it will also not be jumpy. But if we use disable approach, that's also a good option.

Copy link
Copy Markdown
Member

@maryam-saeidi maryam-saeidi left a comment

Choose a reason for hiding this comment

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

Nice job! 💪🏻

It's great to have the same title style for different pages. I've added some clarification questions but overall LGTM

/>
</EuiButton>
),
<EuiButton
Copy link
Copy Markdown
Member

@maryam-saeidi maryam-saeidi Nov 24, 2022

Choose a reason for hiding this comment

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

I like this improvement, just wondering if you checked with @maciejforcone whether disabling the button is the approach that we use in Kibana or do we need to use a loader for the title instead until we have the authorization information. (For the cases that the user actually doesn't have access)


return (
<EuiFlexGroup wrap gutterSize="s" justifyContent="flexEnd">
<EuiFlexItem grow={1}>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

👍🏻

rangeTo={relativeEnd}
refreshInterval={refreshInterval}
refreshPaused={refreshPaused}
width="auto"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

What is this change about?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is this change intentional?

Before After
image image

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think the new Unified Search bar also employs this to make the size of the date picker component dynamic to the displayed value or label. I'm fine with moving in this direction, and we'll probably have to pick this up in other apps later on (if they're not already moving to the new Unified Search bar).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Interesting, may I ask what was the reasoning behind it?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@maryam-saeidi To save space in context of its surrounding elements, for instance the Unified Search bar date picker changes width depending on the value or content within.

image

CleanShot 2022-11-24 at 12 33 49@2x

The previous date picker in the Observability overview page had a fixed size which was the largest width possible (when the date range would be absolute date formats) which is unnecessary for most use-cases.

@CoenWarmer CoenWarmer merged commit b3c022d into elastic:main Nov 24, 2022
@CoenWarmer CoenWarmer deleted the bug/142859-inconsistent-page-title-styling-new branch November 24, 2022 12:11
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Nov 24, 2022
…tail and Cases pages (elastic#146150)

Closes elastic#142859.

## Summary

This PR updates the Observability Overview, Alerts, Rules, Rule Details
and Cases pages so their headers are more consistent with one another.

**Previously:**

https://user-images.githubusercontent.com/535564/203364454-35002377-d23a-4327-91b0-d1f473869f6a.mov

**With this PR:**

https://user-images.githubusercontent.com/535564/203364851-9afd2950-0fba-4f6b-ad52-0b81da77451a.mov
(cherry picked from commit b3c022d)
@kibanamachine
Copy link
Copy Markdown
Contributor

💚 All backports created successfully

Status Branch Result
8.6

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

jloleysens added a commit to jloleysens/kibana that referenced this pull request Nov 24, 2022
* main:
  Make page titles more consistent for Overview, Alerts, Rules, Rule Detail and Cases pages (elastic#146150)
  [Files] Delay `<Image/>` blurhash reveal and handle blurhash errors (elastic#146159)
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Nov 25, 2022
@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

1 similar comment
@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

2 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Copy Markdown
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.

jbudz pushed a commit that referenced this pull request Dec 1, 2022
…ule Detail and Cases pages (#146150) (#146807)

# Backport

This will backport the following commits from `main` to `8.6`:
- [Make page titles more consistent for Overview, Alerts, Rules, Rule
Detail and Cases pages
(#146150)](#146150)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Coen
Warmer","email":"coen.warmer@gmail.com"},"sourceCommit":{"committedDate":"2022-11-24T12:11:28Z","message":"Make
page titles more consistent for Overview, Alerts, Rules, Rule Detail and
Cases pages (#146150)\n\nCloses
https://github.com/elastic/kibana/issues/142859.\r\n\r\n##
Summary\r\n\r\nThis PR updates the Observability Overview, Alerts,
Rules, Rule Details\r\nand Cases pages so their headers are more
consistent with one
another.\r\n\r\n**Previously:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364454-35002377-d23a-4327-91b0-d1f473869f6a.mov\r\n\r\n**With
this
PR:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364851-9afd2950-0fba-4f6b-ad52-0b81da77451a.mov","sha":"b3c022dc05fbe9f941627f526ba301cb1c29eefd","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.6.0","v8.7.0"],"number":146150,"url":"https://github.com/elastic/kibana/pull/146150","mergeCommit":{"message":"Make
page titles more consistent for Overview, Alerts, Rules, Rule Detail and
Cases pages (#146150)\n\nCloses
https://github.com/elastic/kibana/issues/142859.\r\n\r\n##
Summary\r\n\r\nThis PR updates the Observability Overview, Alerts,
Rules, Rule Details\r\nand Cases pages so their headers are more
consistent with one
another.\r\n\r\n**Previously:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364454-35002377-d23a-4327-91b0-d1f473869f6a.mov\r\n\r\n**With
this
PR:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364851-9afd2950-0fba-4f6b-ad52-0b81da77451a.mov","sha":"b3c022dc05fbe9f941627f526ba301cb1c29eefd"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/146150","number":146150,"mergeCommit":{"message":"Make
page titles more consistent for Overview, Alerts, Rules, Rule Detail and
Cases pages (#146150)\n\nCloses
https://github.com/elastic/kibana/issues/142859.\r\n\r\n##
Summary\r\n\r\nThis PR updates the Observability Overview, Alerts,
Rules, Rule Details\r\nand Cases pages so their headers are more
consistent with one
another.\r\n\r\n**Previously:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364454-35002377-d23a-4327-91b0-d1f473869f6a.mov\r\n\r\n**With
this
PR:**\r\n\r\n\r\nhttps://user-images.githubusercontent.com/535564/203364851-9afd2950-0fba-4f6b-ad52-0b81da77451a.mov","sha":"b3c022dc05fbe9f941627f526ba301cb1c29eefd"}}]}]
BACKPORT-->

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release_note:skip Skip the PR/issue when compiling release notes v8.6.0 v8.7.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Page titles are inconsistent on Observability Alerting Pages

8 participants