-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
If I run the following code:
try : jiraissue = s.jira1.getIssue(auth,issue) # look up the issue except : print "Bad Issue skipping", issue #not a valid jira issue raise
On an issue that has since been moved, the following exception is raised:
Bad Issue skipping SYS-48 Traceback (most recent call last): File "./makeReleaseNotes.py", line 68, in ? jiraissue = s.jira1.getIssue(auth,issue) # look up the issue File "/usr/lib/python2.4/xmlrpclib.py", line 1096, in __call__ return self.__send(self.__name, args) File "/usr/lib/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/usr/lib/python2.4/xmlrpclib.py", line 1147, in request return self._parse_response(h.getfile(), sock) File "/usr/lib/python2.4/xmlrpclib.py", line 1286, in _parse_response return u.close() File "/usr/lib/python2.4/xmlrpclib.py", line 744, in close raise Fault(**self._stack[0]) xmlrpclib.Fault: <Fault 0: 'java.lang.Exception: java.lang.NullPointerException'
It would be nice if the Remote API could support moved issues
- is related to
-
JRASERVER-17316 Add a method to remote API (SOAP) that looks up an issue by its key even if the issue has been moved
- Closed
- relates to
-
JRACLOUD-10502 XML RPC Python client unable to retrieve an issue that has been moved
- Closed