|
||||||||
|
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)

Problem still remains with Jenkins-1.483, Nested View Plugin 1.8, role-strategy 1.1.2.
Without View.READ permissions, nested views are not shown as tabs, but can be accessed if the URL's guessed correctly.