|
[
Permlink
| « Hide
]
Derek MacKie added a comment - 23/Feb/06 07:23 PM
We are trying to streamline some of our business processes through a simple soap client on top of Jira - however we absolutely need to have the ability to create sub tasks via the soap interface for this to work. Has this been implemented yet?
I would really like this feature as well.
Sebastian,
We have not got around to this yet, due to the large number of feature request. As I am sure you are aware the source of the RPC plugin is avaialble so you can extend the plugin if needed. We are hoping to address this in teh future. Anton I've attached the patch that I used to add a createSubtask() method to the jira-development-kit--3.8/examples/rpc-jira-plugin files. The work by Andrey Polyakov for the Jimex plugin was very helpful, though this patch takes a different approach and doesn't modify the RemoteIssue class.
Hey, Atlassian, did you ever fill that open position for someone to work on the SOAP API? Another SOAP problem: please extend SOAP so issue creation supports also sub-issues. We need this while importing a lot of issues from current tracking systems.
Hello,
yes, I try to import issues from our current tracking system via SOAP. Unfortunately there is no other way since Jelly also does not support all features we need. I too would like to be able to create subtasks via SOAP.
When you want to integrate with JIRA there a few key things you immediately need to be able to do:- 1) Create an issue Currently can only do 1). Please please please make this more useful We REALLY need this feature in our environment, where we are attempting to import 20,000+ issues from an existing infrastructure. When might this feature be added, either via SOAP or the Jelly script capability?
I attach an updated diff for Jira 3.10 and a precompiled plugin with subtask support. Instructions for installing the plugin:
1) Copy atlassian-jira-rpc-plugin-3.10.2-1-subtask.jar to WEB-INF/lib This plugin seems to automatically replace the standard "RPC Jira Plugin", at least it did for me. To create subtasks, see the attached Python script "subtask.py" for an example. Note that there is a new SOAP method createSubtask which accepts a third parameter which is the parent issue key. You cannot pass this information using the second parameter as you might think. If you use this to bulk import issues, I suggest you remove this plugin atter the import and use the default RPC Jira Plugin supplied by Atlassian. Atlassian folk - please add this patch into the official plugin
 Interesting, that 3.8 patch appears to be based on a patch that I emailed someone else on Oct 30th! Anyway, I've attached my original patch for 3.8, which also includes a check that you don't create subtasks of subtasks accidentally. I would also like to see this functionality make it into JIRA, but I'm aware that Atlassian have been trying to hire someone to own the API code for a while now.
Has anyone updated this patch for 3.11 ?
I took the 3.10 diff and applied it to the 3.12 code and it worked. Thanks for the patch!
If work is to be performed on that level it would be interesting to also augment the SOAP API in order to allow it to return which task is the parent of a sub-task.
If the information I have is still valid this is not possible in 3.7.2 and in 3.11. Also for me, sub-task and link support using XMLRPC is the most important for me. My automation tool uses XMLRPC for some tasks, but then has to switch to using the REST (wget) interface for others. Both work well, but having to switch to the REST interface in the same tool is painful, including the REST discovery phase. My initial import from another tracking tool also was not smooth because of this. It was a combination of about 6 manual steps, some with XMLRPC, generating temporary files and some with Jelly, etc. I had to do this about 8 times before I got it 100% correct. We used "atlassian-jira-rpc-plugin-3.10.2-1-subtask.jar" in a way that Peter told .And using this we
are able to insert the subtask. But while we are using this patch, the following method is not working : "getIssueTypesForProject" . Do anybody have any idea regarding this ? My vote is in.
This would be an important improvement for us. We use Jira in combination with an automated testtool. At the moment we put the results back in a comment but we would really like to add subtasks (e.g. testresults from a specific automated run) to the parent issue. And when JRA-4446 would be resolved....  Please fix this. We need the ability to 1) determine an existing tasks parent task and 2) create a sub-task.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Add ability to create sub-task via soap
