-
Improvement
-
Resolution: Unresolved
-
Major
Within "Manage Roles" there is both the "Global roles" and "Project roles" .... Global roles has columns for Views, but Project roles does not.
Would be nice to assign a subset of regex Pattern projects to a Role to edit View.
May be partially linked to https://issues.jenkins-ci.org/browse/JENKINS-14546
- is duplicated by
-
-
- Resolved
-
[JENKINS-28975] Support Views for "Project roles" section
Brantone
created issue -
Hi,
Sorry, missed the ticket. There is a ticket for views support. I have not completely got the workaround, but it's great that you're unblocked at least. From what I see there is also a need to handle folders better on the project (item) level
| Workflow | Original: JNJira [ 163839 ] | New: JNJira + In-Review [ 181398 ] |
Do you have an ETA on when "View" permissions will be available in the project roles?
bassam_khouri No ETA. Here is a pending pull request, but it is not ready: https://github.com/jenkinsci/role-strategy-plugin/pull/21 . Feel free to take it an finalize
| Link |
New:
This issue is duplicated by |
| Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
| Labels | New: gsoc-2019-project-idea user-experience |
Hi,
just a question to clarify the current status of this issue and what is supported or no.
In current versions, I can see that the "View" permissions (read, delete, create, configure) are already available at "Item" (formerly "Project") level.
But it seems that they only work globally and for "Folders", but not for "Views". Is that correct? Or is there any way to create an item role only granting access to configure this or that view?
I've tried here by creating roles which pattern matches the view name, but it doesn't work. And in the documentation I only have found references to job and folders matching, not to view matching.
Can you clarify if, those item-level ("View") perms are only useful for Folders and not for Views?
TIA and ciao 
Eloy Lafuente
added a comment - - edited Hi,
just a question to clarify the current status of this issue and what is supported or no.
In current versions, I can see that the "View" permissions (read, delete, create, configure) are already available at "Item" (formerly "Project") level.
But it seems that they only work globally and for "Folders", but not for "Views". Is that correct? Or is there any way to create an item role only granting access to configure this or that view?
I've tried here by creating roles which pattern matches the view name, but it doesn't work. And in the documentation I only have found references to job and folders matching, not to view matching.
Can you clarify if, those item-level ("View") perms are only useful for Folders and not for Views?
TIA and ciao
Have devised a work-around whereby our projects are grouped using Folders plugin ... so provide the ability to edit Views via Global roles, but then restricted to the folders and what they can view via appropriate regex in Project roles