-
Notifications
You must be signed in to change notification settings - Fork 1.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
Che administrators can specify a header message on User Dashboard visible to every user #20724
Labels
area/dashboard
kind/task
Internal things, technical debt, and to-do tasks to be performed.
new¬eworthy
For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
severity/P1
Has a major impact to usage or development of the system.
sprint/current
Milestone
Comments
ibuziuk
added
the
kind/task
Internal things, technical debt, and to-do tasks to be performed.
label
Nov 3, 2021
che-bot
added
the
status/need-triage
An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
label
Nov 3, 2021
ibuziuk
added
area/dashboard
sprint/next
and removed
status/need-triage
An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
labels
Nov 3, 2021
l0rd
added
the
severity/P1
Has a major impact to usage or development of the system.
label
Nov 4, 2021
Hi, a question to the assignee of this issue: Will the outcome require any changes to the relevant content of the Installation Guide or Administration Guide or End-user Guide? Yes/No? |
@max-cx if the question is still relevant: yes |
11 tasks
Fixed in the eclipse-che/che-operator#1330 |
l0rd
added
new¬eworthy
For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
status/release-notes-review-needed
Issues that needs to be reviewed by the doc team for the Release Notes wording
labels
Mar 10, 2022
l0rd
changed the title
As an admin, I would like to have a possibility to add information / warning header to the User Dasboard by configuring the CheCluster CR
Che administrators can specify a header message on User Dasboard visible to every user
Mar 10, 2022
To be backported to 7.42.x / CRW 2.15.3 |
This was referenced Mar 14, 2022
Closed
ibuziuk
changed the title
Che administrators can specify a header message on User Dasboard visible to every user
Che administrators can specify a header message on User Dashboard visible to every user
Mar 15, 2022
max-cx
removed
the
status/release-notes-review-needed
Issues that needs to be reviewed by the doc team for the Release Notes wording
label
Jan 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/dashboard
kind/task
Internal things, technical debt, and to-do tasks to be performed.
new¬eworthy
For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
severity/P1
Has a major impact to usage or development of the system.
sprint/current
Is your task related to a problem? Please describe
From time to time, Admin needs to communicate some information with the users e.g.:
Admin should have a possibility to configure the header that will be applied to the UD layout.
from the UX perspective It could look similar to the warning we are having for workspace format were not only the text, but also links are supported in the message body:
Describe the solution you'd like
It should be possible to configure the warning for UD on the CheCluster CR level e.g.
Describe alternatives you've considered
Currently, it is possible to configure the warning on the product.json level but this requires rebuilding the whole project which does not look like an option - #18769
It should be possible to configure the banner in runtime
Release Notes Text
It's now possible to customize Che User Dashboard, Che users landing page, to show a message that has been setup by the administrator. The message will be visible to every user that will have access to Che User Dashboard.
The text was updated successfully, but these errors were encountered: