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

          [JENKINS-28975] Support Views for "Project roles" section

          Brantone added a comment -

          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

          Brantone added a comment - 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

          Oleg Nenashev added a comment -

          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

          Oleg Nenashev added a comment - 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

          Bassam Khouri added a comment -

          Do you have an ETA on when "View" permissions will be available in the project roles?

          Bassam Khouri added a comment - Do you have an ETA on when "View" permissions will be available in the project roles?

          Oleg Nenashev added a comment -

          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

          Oleg Nenashev added a comment - 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

          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

          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

          Markus Winter added a comment -

          stronk7 Indeed the view permissions on Items only apply to folders basically. Views are not Items in Jenkins that is why they don't work. While it might be possible to add a filter for views, this will not restrict people from accessing the jobs if an item rule allows them to access the job. With the ContainedInView macro that is available now, having that possibility might be something to think of. There is a PR open for this feature. The tricky part is determining the view name when you're in a folder of e.g. when using nested-view plugin.

          Limiting the names of views that can be created might not be possible though as there is most likely no feature in core to limit view names as it is possible for item names.

          Markus Winter added a comment - stronk7 Indeed the view permissions on Items only apply to folders basically. Views are not Items in Jenkins that is why they don't work. While it might be possible to add a filter for views, this will not restrict people from accessing the jobs if an item rule allows them to access the job. With the ContainedInView macro that is available now, having that possibility might be something to think of. There is a PR open for this feature. The tricky part is determining the view name when you're in a folder of e.g. when using nested-view plugin. Limiting the names of views that can be created might not be possible though as there is most likely no feature in core to limit view names as it is possible for item names.

            Unassigned Unassigned
            brantone Brantone
            Votes:
            5 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: