|
This is a zip file included updated source files a new class to allow some issue linking operations across the SOAP interface. It is based off of XML-RPC 3.3-2 source code.
I would like too created link betwwen issues via Soap.
So I would like to know if modification have been done or will be done soon. Ludovic: looks like this is scheduled to be fixed in JIRA 3.7, which is 3 releases out there. If you want it to happen earlier, why don't you vot e for this issue ...
3.6 was just released. So it should be in the next version.
To be able to create a link remotely, we also will need all available link types:
LinkType[] getLinkTypes(); Suggested methods are not enough. I've taken a look at the attached file. In JiraSoapService, there are the following methods:
================== public RemoteIssue[] getLinkedIssues(String token, String issueKey, String linkName, boolean outward) throws RemotePermissionException, RemoteAuthenticationException, RemoteException; The problem with the first method is that though I get all linked issues, I can't tell through which link are they connected. The problem with the second method is that if I have N link types in the system, I'll have to call this method 2N times to collect all the information about what issues are linked and how. Why don't you create the following method instead? =================== public RemoteLink[] getIssueLinks(String token, String issueKey) throws blablabla; public class RemoteLink { private RemoteLinkType linkType; private int sourceIssueId; private String sourceIssueKey; private int targetIssueId; private String targetIssueKey; .... } ==================== I would be very happy to have read access to the issue links as described by Igor Sereda.
As there is only the possibility to patch the SOAPService myself, thats the way to go. Its sad though that this issue "wont take long" since 2005 now. Atlassians,
are there any updates on this feature implementation? It would be extremely helpful to at least have read access to issue links via SOAP. thanks in advance Denis,
At the moment I have no news. We are desparately trying to hire a Remote API developer for our San Francisco office to help us improve JIRA's remote API. Cheers, How hard would it be to implement? has anyone attempted to do a temporary
fix or some fix that can potentially be included into the trunk of the next release? For everyone requesting a more complete implementation of a SOAP remote API.
We apologize for not keeping you better informed of our thinking on the feature. We will do our best to make sure we do in the future. We do not have the feature scheduled for inclusion at this point however we are, as Anton mentions higher in the thread, currently working on building our API expertise and resources. Once we have them on board we will be able to attack this. For the more technically orientated please note that the RPC plug-in source code Brett I too would benefit from the need to link issues
Has anyone modified the RPC plug-in source code to provide access to the links for 3.12?
Please try to get this into the next release, we need it but don't want to hack in the hotfix. Also it would be nice if you could use Issue links as Query constraints.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Ability to access and create link information via SOAP
Cheers,
Nick