Details
-
Task
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
-
1.0-japan-m9, 1.0-m10
Description
When items are shown on the main dashboard (/pipelines) they may include items that are from nested folders.
When clicking on an item that is in a folder, it needs to be loaded with the URI reflecting what its folder path is.
In Scope
- When UX-276 is completed we need to handle nested folder jobs in the frontend
- Always use the fullName as the display name
- Browsing to a pipeline should work if its in a folder
- Browsing to a folder should 404
Browsing to a folder just show a list of the folder contents as if that folder was the "root" of the dashboard
[1:24 PM] James Dumay: e.g if I browse to /org/my/sub/folder/
[1:24 PM] James Dumay: show everything under /org/my/sub/folder/ as it is "/"
Attachments
Issue Links
- is blocked by
-
-
- Resolved
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | UX-35 [ 24725 ] |
| Rank | Ranked higher |
| Link | This issue is blocked by UX-276 [ UX-276 ] |
| Comment | [ This is unblocked now if anyone is interested in it ] |
| Link | This issue is blocked by UX-196 [ UX-196 ] |
| Link | This issue relates to UX-310 [ UX-310 ] |
So if we look at the REST url:
breaking it down:
http://localhost:62054/jenkins/blue/rest/organizations/$orgname/pipelines/$folderA/pipelines/$folderB/$pipelineName/
so "pipelines" acts as a separator
jdumay this will involve the design as per the mockups in https://cloudbees.atlassian.net/browse/UX-196 right?
mnealeAs mentioned in comment in https://cloudbees.atlassian.net/browse/UX-196, "There is issue of how to detect folder vs pipeline, that gets addressed with data extensibility/capability work.", this is cross cutting concern and going to be addressed in UX-68/UX-350.
vpandey actually can use the numOfFolders etc to know if something is a folder at least (so they can not be shown at top level).
| Link | This issue is blocked by UX-310 [ UX-310 ] |
| Description |
In Scope * When UX-276 is completed we need to handle nested folder jobs in the frontend |
In Scope * When UX-276 is completed we need to handle nested folder jobs in the frontend * [1:22 PM] James Dumay: * Dashboard should NOT display folders * Always use the fullName as the display name * Browsing to a pipeline should work if its in a folder [1:23 PM] James Dumay: * Browsing to a folder should 404 [1:23 PM] James Dumay: * Browsing to a folder just show a list of the folder contents as if that folder was the "root" of the dashboard [1:24 PM] James Dumay: e.g if I browse to /org/my/sub/folder/ [1:24 PM] James Dumay: show everything under /org/my/sub/folder/ as it is "/" |
| Link | This issue is blocked by UX-533 [ UX-533 ] |
| Description |
In Scope * When UX-276 is completed we need to handle nested folder jobs in the frontend * [1:22 PM] James Dumay: * Dashboard should NOT display folders * Always use the fullName as the display name * Browsing to a pipeline should work if its in a folder [1:23 PM] James Dumay: * Browsing to a folder should 404 [1:23 PM] James Dumay: * Browsing to a folder just show a list of the folder contents as if that folder was the "root" of the dashboard [1:24 PM] James Dumay: e.g if I browse to /org/my/sub/folder/ [1:24 PM] James Dumay: show everything under /org/my/sub/folder/ as it is "/" |
In Scope * When UX-276 is completed we need to handle nested folder jobs in the frontend * Always use the fullName as the display name * Browsing to a pipeline should work if its in a folder [1:23 PM] James Dumay: * Browsing to a folder should 404 [1:23 PM] James Dumay: * Browsing to a folder just show a list of the folder contents as if that folder was the "root" of the dashboard [1:24 PM] James Dumay: e.g if I browse to /org/my/sub/folder/ [1:24 PM] James Dumay: show everything under /org/my/sub/folder/ as it is "/" |
| Description |
In Scope * When UX-276 is completed we need to handle nested folder jobs in the frontend * Always use the fullName as the display name * Browsing to a pipeline should work if its in a folder [1:23 PM] James Dumay: * Browsing to a folder should 404 [1:23 PM] James Dumay: * Browsing to a folder just show a list of the folder contents as if that folder was the "root" of the dashboard [1:24 PM] James Dumay: e.g if I browse to /org/my/sub/folder/ [1:24 PM] James Dumay: show everything under /org/my/sub/folder/ as it is "/" |
In Scope * When UX-276 is completed we need to handle nested folder jobs in the frontend * Always use the fullName as the display name * Browsing to a pipeline should work if its in a folder * Browsing to a folder should 404 Browsing to a folder just show a list of the folder contents as if that folder was the "root" of the dashboard [1:24 PM] James Dumay: e.g if I browse to /org/my/sub/folder/ [1:24 PM] James Dumay: show everything under /org/my/sub/folder/ as it is "/" |
| Rank | Ranked higher |
| Description |
In Scope * When UX-276 is completed we need to handle nested folder jobs in the frontend * Always use the fullName as the display name * Browsing to a pipeline should work if its in a folder * Browsing to a folder should 404 Browsing to a folder just show a list of the folder contents as if that folder was the "root" of the dashboard [1:24 PM] James Dumay: e.g if I browse to /org/my/sub/folder/ [1:24 PM] James Dumay: show everything under /org/my/sub/folder/ as it is "/" |
When items are shown on the main dashboard (/pipelines) they may include items that are from nested folders. When clicking on an item that is in a folder, it needs to be loaded with the URI reflecting what its folder path is. In Scope * When UX-276 is completed we need to handle nested folder jobs in the frontend * Always use the fullName as the display name * Browsing to a pipeline should work if its in a folder * Browsing to a folder should 404 Browsing to a folder just show a list of the folder contents as if that folder was the "root" of the dashboard [1:24 PM] James Dumay: e.g if I browse to /org/my/sub/folder/ [1:24 PM] James Dumay: show everything under /org/my/sub/folder/ as it is "/" |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Sprint | 1.0-japan-m9 [ 41 ] |
| Rank | Ranked lower |
| Sprint | 1.0-japan-m9 [ 41 ] | 1.0-m10 [ 56 ] |
cmeyers sorry I may have mislead this morning when talking through URIs.
The aim is that the main dashboard does show (paginated) all pipelines from all folders (but not the folders themselves). This is a big long flat list. When we have that, we will need to be able to let the user click on something that is in a folder (even though it is flattened out on the main dashboard) and have it load, with the correct data URL for rest, and the URI in the browser set correctly - which is what this ticket is about.
V R
made changes -
| Project Import | Tue Jun 14 12:50:41 JST 2016 [ 1465876241198 ] |
| Project Import | Wed Jun 15 02:53:18 UTC 2016 [ 1465959198925 ] |
| Labels | blueocean-imported |
| Component/s | blueocean-plugin [ 21481 ] | |
| Key |
|
|
| Workflow | Product Backlog April 2016 V2 [ 172228 ] | JNJira [ 172486 ] |
| Project | User Experience [ 10600 ] | Jenkins [ 10172 ] |
| Status | To Do [ 10003 ] | Open [ 1 ] |
V R
made changes -
| Priority | Medium [ 3 ] | Major [ 10000 ] |
V R
made changes -
| Reporter | James Dumay [ jdumay ] | James Dumay [ jamesdumay ] |
V R
made changes -
| Reporter | James Dumay [ jdumay ] | James Dumay [ jdumay ] |
| Sprint | 1.0-m10 [ 56 ] |
| Rank | Ranked higher |
| Sprint | 1.0-m10 [ 66 ] |
| Rank | Ranked lower |
| Assignee | Cliff Meyers [ cliffmeyers ] |
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Sprint | 1.0-m10 [ 66 ] | 1.0-m9 [ 46 ] |
| Rank | Ranked lower |
| Sprint | 1.0-japan-m9 [ 46 ] | 1.0-japan-m9, 1.0-m10 [ 46, 66 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Attachment | IMG_7668.JPG [ 33099 ] |
cliffmeyers here is the whiteboard where we talked about where to put the path:
I am not sure if tscherler was also attacking this - I don't think so.
Yes, this is in-progress. I was in training on Wed, but had time to squash a few small bugs during breaks. I plan to focus on this on Thu.
| Priority | Critical [ 2 ] | Blocker [ 1 ] |
| Priority | Blocker [ 1 ] | Major [ 3 ] |
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Workflow | JNJira [ 172486 ] | JNJira + In-Review [ 199236 ] |
vpandey Some clarification: in https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-rest - I can see how folders are navigated, but it isn't clear to me how you know something is a folder to start with - is there something missing?