-
Bug
-
Resolution: Fixed
-
Major
-
Blue Ocean 1.1.4
-
-
Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4
When a custom Blue Ocean Organisation is in use that uses a Folder as its root rather than Jenkins then users can be prevented from creating pipelines that they should be able to create.
- relates to
-
JENKINS-45482 modifying existing github org incorrect behaviour if custom blue ocean org in use
-
- Closed
-
-
JENKINS-45360 creating a pipeline with a duplicate name does not fail gracefully with custom Org
-
- Closed
-
- links to
[JENKINS-45442] When a custom organisation is in use pipeline creation checks permissions on jenkins rather than the organistion root
Description |
Original:
When a customer Blue OCean Organisation is in Use that uses a Folder as its root rather than Jenkins then users can be prevented from creating pipelines that they should be able to create. |
New:
When a customer Blue Ocean Organisation is in Use that uses a Folder as its root rather than Jenkins then users can be prevented from creating pipelines that they should be able to create. |
Labels | New: cloudbees-internal-steel |
Epic Link | New: JENKINS-35759 [ 171771 ] |
Sprint | New: Blue Ocean 1.2-beta3 [ 346 ] |
Assignee | New: Alvaro Lobato [ alobato ] |
Assignee | Original: Alvaro Lobato [ alobato ] | New: James Nord [ teilo ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Link |
New:
This issue relates to |
Link |
New:
This issue relates to |
Description |
Original:
When a customer Blue Ocean Organisation is in Use that uses a Folder as its root rather than Jenkins then users can be prevented from creating pipelines that they should be able to create. |
New:
When a custom Blue Ocean Organisation is in use that uses a Folder as its root rather than Jenkins then users can be prevented from creating pipelines that they should be able to create. |