-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[ILM] Copy update #91100
[ILM] Copy update #91100
Conversation
… primary buttons back to correct order
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes look good @yuliacech ! I did not test locally, happy when CI is passing. Would you mind adding a screenshot of the buttons that have swapped position?
Thanks a lot for your review, @jloleysens! I updated the screenshot with a full form version :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for raising this @yuliacech.
While most of the changes look good, I have some major concerns regarding how the current UI uses "data" in place of "index." In ES, "data" could mean document or index.
The UI should be clear that the policy affects indices, not documents. For example:
Users could interpret this copy as:
"The policy moves documents that are N days old."
OR
"The policy moves documents with a timestamp that is N days old."
But neither is the case. Phase migration is triggered by index age or rollover date.
I'd also like to get feedback from @debadair, who has worked closely on ILM in the past.
..._management/public/application/sections/edit_policy/components/phase_footer/phase_footer.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/i18n_texts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/i18n_texts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/i18n_texts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/i18n_texts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/i18n_texts.ts
Outdated
Show resolved
Hide resolved
..._management/public/application/sections/edit_policy/components/phase_footer/phase_footer.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some alternate suggestions that are more from the viewpoint of moving data between the data tiers than the underlying mechanics. I think it would be good to get @gchaps to weigh in on the terminology.
..._management/public/application/sections/edit_policy/components/phase_footer/phase_footer.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/i18n_texts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/i18n_texts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/i18n_texts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/i18n_texts.ts
Outdated
Show resolved
Hide resolved
..._management/public/application/sections/edit_policy/components/phase_footer/phase_footer.tsx
Outdated
Show resolved
Hide resolved
@elasticmachine merge upstream |
Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> Co-authored-by: debadair <debadair@elastic.co>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks @yuliacech.
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
* Added copy adjustments, fixed wrong capitalization of titles and swap primary buttons back to correct order * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> Co-authored-by: debadair <debadair@elastic.co> * Fixed eslint issues and added labels for buttons Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> Co-authored-by: debadair <debadair@elastic.co>
* Added copy adjustments, fixed wrong capitalization of titles and swap primary buttons back to correct order * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> Co-authored-by: debadair <debadair@elastic.co> * Fixed eslint issues and added labels for buttons Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> Co-authored-by: debadair <debadair@elastic.co> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> Co-authored-by: debadair <debadair@elastic.co>
Summary
This PR continues work done in 88024, 88671, 90291.
Previous work concentrated on aligning ILM design with data tiers concept and this PR contains a copy update concerning:
Screenshot
Checklist