-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
1.26 on Jenkins 1.509
Renaming a job caused the attached stacktrace.
- is blocking
-
JENKINS-13222 Allow job selection with fixed job names to contain variables without requiring job permissions for authenticated users
-
- Closed
-
- is duplicated by
-
JENKINS-17524 NPE when renaming job in My Views
-
- Resolved
-
-
JENKINS-17705 NullPointerException when rename a job (Status Code: 500)
-
- Resolved
-
-
JENKINS-17596 NullPointerException on project rename
-
- Closed
-
-
JENKINS-17613 NullPointerException when renaming build plan
-
- Closed
-
[JENKINS-17447] NPE when renaming job
Link |
New:
This issue is blocking |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is duplicated by |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Assignee | New: Jesse Glick [ jglick ] |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is duplicated by |
Workflow | Original: JNJira [ 148622 ] | New: JNJira + In-Review [ 192803 ] |
Was fixed in 4203fe7c16fe4bbe4efbc9bae87a329dfc1ec393.