[JIRA] (JENKINS-60109) After 5.0.0 trending graph is no longer intractable

5 views
Skip to first unread message

steve.springett@owasp.org (JIRA)

unread,
Nov 12, 2019, 8:44:03 PM11/12/19
to jenkinsc...@googlegroups.com
Steve Springett updated an issue
 
Jenkins / Bug JENKINS-60109
After 5.0.0 trending graph is no longer intractable
Change By: Steve Springett
Summary: After 2 5 .0.0 trending graph is no longer  intractable
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

steve.springett@owasp.org (JIRA)

unread,
Nov 12, 2019, 8:44:03 PM11/12/19
to jenkinsc...@googlegroups.com
Steve Springett updated an issue
Before version 2 5 .0.0 user could interact with the  plugin's vulnerability trending graph, .
I could click on any build number in the graph, and browser would be redirected to appropriate build in history.



This seems to be no longer possible after 2.0.0.

Currently the only action I'm able to do, is to toggle visibility one of horizontal lines by clicking on the labels below.

!image-2019-11-08-15-39-41-805.png!

steve.springett@owasp.org (JIRA)

unread,
Nov 12, 2019, 8:44:04 PM11/12/19
to jenkinsc...@googlegroups.com
Steve Springett updated an issue
Before version 5.0.0 user could interact with the  plugin's vulnerability trending graph, .
I could click on any build number in the graph, and browser would be redirected to appropriate build in history.

This seems to be no longer possible after 2 5 .0.0.


Currently the only action I'm able to do, is to toggle visibility one of horizontal lines by clicking on the labels below.

!image-2019-11-08-15-39-41-805.png!

steve.springett@owasp.org (JIRA)

unread,
Nov 12, 2019, 8:45:02 PM11/12/19
to jenkinsc...@googlegroups.com

steve.springett@owasp.org (JIRA)

unread,
Nov 12, 2019, 8:45:03 PM11/12/19
to jenkinsc...@googlegroups.com
Steve Springett commented on Bug JENKINS-60109
 
Re: After 5.0.0 trending graph is no longer intractable

Current version is 5.x not 2.0.0. I update those references. If you'd like that feature back, pull requests are encouraged.

Reply all
Reply to author
Forward
0 new messages