Jenkins Security Advisories - UX Improvement Suggestions

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Jenkins Security Advisories - UX Improvement Suggestions

FredG
Hi,

Thanks for the very thorough Jenkins security advisories.
Unfortunately, I find myself scrolling up and down a lot, when trying to find out the severity of an issue while reading it's description. That the order of the issues differs between the description section and the severity section does not help either. ;)

I'd suggest to add the severity to each issue's description to avoid the scrolling. If there is no added value in the separate severity section, than maybe getting rid of it entirely makes sense as well.

Regards,

Fred

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7ec18933-2407-46b8-b812-84618d46a17fn%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins Security Advisories - UX Improvement Suggestions

Daniel Beck


> On 14. Jan 2021, at 17:58, 'FredG' via Jenkins Developers <[hidden email]> wrote:
>
> I'd suggest to add the severity to each issue's description to avoid the scrolling. If there is no added value in the separate severity section, than maybe getting rid of it entirely makes sense as well.

Thanks for the feedback, I'll do that. I'm pretty sure I even have some work in progress for this somewhere, and then I wanted to move affected/fixed components too, but that ended up being more difficult, and I didn't do either in the end... Time to restart this!

(Meanwhile, as a workaround, you could view the page source. Unlike most jenkins.io stuff, the page is basically generated from front matter (metadata) using the page template. So if you can read YAML somewhat well, that is already grouped like you expect.)

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/11FADEB2-4BCA-40EC-8692-972AE609F0B3%40beckweb.net.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins Security Advisories - UX Improvement Suggestions

FredG
Thanks Daniel!

I think I'll wait for the human-readable version. :D

On Thursday, January 14, 2021 at 7:55:55 PM UTC+1 Daniel Beck wrote:


> On 14. Jan 2021, at 17:58, 'FredG' via Jenkins Developers <[hidden email]> wrote:
>
> I'd suggest to add the severity to each issue's description to avoid the scrolling. If there is no added value in the separate severity section, than maybe getting rid of it entirely makes sense as well.

Thanks for the feedback, I'll do that. I'm pretty sure I even have some work in progress for this somewhere, and then I wanted to move affected/fixed components too, but that ended up being more difficult, and I didn't do either in the end... Time to restart this!

(Meanwhile, as a workaround, you could view the page source. Unlike most jenkins.io stuff, the page is basically generated from front matter (metadata) using the page template. So if you can read YAML somewhat well, that is already grouped like you expect.)

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8ef6a049-c342-4148-9d94-66032e36be8dn%40googlegroups.com.