[ 
https://issues.jenkins-ci.org/browse/JENKINS-13429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163630#comment-163630
 ] 
dogfood commented on JENKINS-13429:
-----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[jenkins_ui-changes_branch 
#30|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/30/]
     [FIXED JENKINS-13429] (Revision d1b2ba7e4988d26fbb815b8912efb16273c407d4)

     Result = SUCCESS
Kohsuke Kawaguchi : 
[d1b2ba7e4988d26fbb815b8912efb16273c407d4|https://github.com/jenkinsci/jenkins/commit/d1b2ba7e4988d26fbb815b8912efb16273c407d4]
Files : 
* core/src/main/java/hudson/security/AuthorizationStrategy.java
* changelog.html

                
> Nested views not showing up with just read perms for View
> ---------------------------------------------------------
>
>                 Key: JENKINS-13429
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13429
>             Project: Jenkins
>          Issue Type: Bug
>          Components: nested-view
>    Affects Versions: current
>            Reporter: M S
>            Assignee: Kohsuke Kawaguchi
>              Labels: jenkins, plugin, views
>
> Jenkins 1.459 + Nested View Plugin 1.8 + Role-based Authorization Strategy 
> 1.1.2
> User has read permissions for "View" but Jenkins main page is missing Nested 
> views (even if they have sub views with jobs).
> Adding "configure" perms for "View" results in Nested views showing up 
> correctly.
> It looks like it's connected with:
> "Added the View.READ permission to control visibility of views, and updated 
> the default implementation to hide empty views. (issue 3681)"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to