Need help with Jira SOAP API for sub-task creation
I’m using Jira version 4.2.1-b588 and working with the JiraSoapService class. I’ve been looking for a way to create sub-tasks or link issues, but I can’t seem to find the right method.
Has anyone successfully created sub-tasks or linked issues using the SOAP API? I’d really appreciate some guidance on this. Maybe there’s a specific method I’m overlooking or a different approach I should take?
If you’ve dealt with this before, please share your experience. Thanks in advance for any help!
I’ve had a fair share of troubles with Jira’s SOAP API, particularly in older versions like 4.2.1. The workaround that has worked for me involved first creating a regular issue and then updating it by setting the ‘parent’ field via the updateIssue() method. Although it’s not the most elegant solution, it’s functional. For linking issues, I recall that methods like linkIssues() could be useful, but the overall SOAP approach remains less straightforward. If feasible, migrating to the REST API might prove worthwhile given its improved handling of sub-tasks and links.
ugh, jira 4.2.1 soap api is ancient. have u tried using createIssue() to make a regular issue then updateIssue() to set the parent field? not ideal but it worked 4 me. might wanna look into createRemoteLink() for linking. honestly tho, soap api is a pain - switch to REST if u can, its way better for this stuff.
I’ve worked with Jira’s SOAP API extensively, and creating sub-tasks can be tricky. For version 4.2.1, there’s no direct method to create sub-tasks via SOAP. However, you can achieve this by creating a regular issue and then updating its parent field.
First, use createIssue() to make a new issue. Then, call updateIssue() to set the ‘parent’ field to the key of the parent issue. It’s not elegant, but it works. For linking issues, look into the createRemoteLink() method.
Remember, Jira’s SOAP API is deprecated. If possible, consider migrating to the REST API for better support and more straightforward methods for these operations.