-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
Separate severity for pinned issues or annountment #283
Comments
I think in the case of severities it's pretty easy to understand what the logical structure should be (down at the top; maintenance at the bottom), but I'm not so sure about informational posts which are intentionally pinned; are they above maintenance, are they at the same level as a partial outage, etc? thanks for the suggestion! |
@mistermantas Pinned maintenance is showing at the bottom of outages but it does looks like in the same box as major issue and red in colour. Please see attached screenshot. It would be good to show as a separate box than the outages as different colour. (blue/green?) Also even with outages, they can be structured with different severity for e.g. all major outages in its own box with red colour, all disrupted outages in a separate box in amber colour to avoid misleading signal. :) |
Is your feature request related to a problem? Please describe.
I'm always frustrated when all issues and/or announcement are pinned together even though they have different level of severity. E.g. A maintenance announcement is not a major issue.
Describe the solution you'd like
Pinned issue should be separated with different severity with the highest severity shown at the top of the page with order.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: