-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Hudson ver. 1.340
I run into the following:
When an user creates a new job he get a "Status Code: 404" error-page, right after he submitted the jobname and type. This does not happen when the Job - Read permission in the Project-based Matrix Authorization Strategy is switched on (by the admin). But when the Job - Read permission is switched on, the user also can see all other jobs from other projects, violating our visibility requirement (project members may only see and have access to their own jobs).
Maybe it is a solution to move the Project-based security matrix to the same page where you register the jobname and type.
Then the user have the possibility to set the Job-Read permission for a specific group or user.
Regards,
Johan.
- is duplicated by
-
JENKINS-18493 Users unable to copy jobs without global read permissions
- Resolved
-
JENKINS-5278 Newly created jobs can get 'lost'
- Resolved
- links to