|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-14546) Regular users (othe... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)
- [JIRA] (JENKINS-14546) Regular users ... [email protected] (JIRA)

We are facing the same problem (Jenkins LTS 1.466.2 & Nested View 1.9)
Even if View.READ permission is granted, nested views are not visible to regular (non-admin) users;
As a workaround, we have emailed the affected users the URL to the view (eg: http://jenkins_server/view/VIEWNAME)