-
Story
-
Resolution: Duplicate
-
Major
-
-
1.0-m1
jQuery was added as a stopgap measure for getting the ExtensionPoint metadata. Easiest thing to do is probably to embed this data in the original page (index.jelly) and so remove the need to make any call. Otherwise we need to find http client replacement for jquery.
[JENKINS-35848] Embed the extension point data in the original page load
Epic Link | New: UX-34 [ 24724 ] |
Sprint | New: 1.0-m1 [ 21 ] |
Priority | Original: Medium [ 3 ] | New: Low [ 4 ] |
Epic Link | Original: UX-34 [ 24724 ] |
Epic Link | New: UX-35 [ 24725 ] |
Priority | Original: Low [ 4 ] | New: Lowest [ 5 ] |
Priority | Original: Lowest [ 5 ] | New: Medium [ 3 ] |
Summary | Original: Get rid of jquery in blueocean-web | New: Embed the extension point data in the original page load |
Description | Original: I was only added a stopgap measure for getting the ExtensionPoint metadata. Easiest thing to do is probably to embed this data in the original page (index.jelly) and so remove the need to make any call. Otherwise we need to find http client replacement for jquery. | New: jQuery was added as a stopgap measure for getting the ExtensionPoint metadata. Easiest thing to do is probably to embed this data in the original page (index.jelly) and so remove the need to make any call. Otherwise we need to find http client replacement for jquery. |
Workflow | Original: CloudBees Default Workflow [ 41642 ] | New: Product Backlog April 2016 v2 [ 43445 ] |
Status | Original: New [ 10200 ] | New: To Do [ 10003 ] |