Webservice Jira 给出:错误:没有这样的操作“getIssuesFromJqlSearch”从吉拉 4.01 开始

发布于 2024-08-21 06:22:07 字数 356 浏览 13 评论 0原文

当我使用Jira的Web服务时,我需要使用getIssuesFromJqlSearch方法来描述某个(JQL)查询。但它返回我“没有这样的操作'getIssuesFromJqlSearch'”。 Jira 4.01中这个方法还没有实现吗?

顺便说一句:我需要一种方法来获取一个特定项目的所有问题,而无需先创建过滤器。这是我找到解决方法的第一个方法,因为没有函数 getIssuesFromProject。

如果无法使用 JQL 方法解决问题,我会尝试使用 URL jql 语句(如 SearchRequest.xml?jqlQuery=project+%3D+Testproject&tempMax=1000)获取 RSS XML 视图。但这不是我最喜欢的。

When I use the Webservice of Jira, I need to use the method getIssuesFromJqlSearch to describe a certain (JQL) Query. But it returns me "No such operation 'getIssuesFromJqlSearch'". Is this method in Jira 4.01 not implemented yet?

BTW: I need a method to get all Issues from one specific project, without creating filters first. This was my first way to find a workaround, because there is no function getIssuesFromProject.

If there is no way to fix the problem with the JQL method, I try to take RSS XML View with the URL jql statement like SearchRequest.xml?jqlQuery=project+%3D+Testproject&tempMax=1000. But this is not my favorite.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

抹茶夏天i‖ 2024-08-28 06:22:07

我刚刚使用soapUI 调用jira.atlassian.com 上的getIssuesFromJqlSearch,效果很好。你安装的是同一个版本吗?不管怎样,您可以使用soapUI 来分析WSDL 并测试所有方法:然后您将隔离问题是否出在您的JIRA 上或是否出在调用该方法的代码上。

顺便说一句,在 JIRA 客户端中,我们确实使用 RSS XML 来下载大部分信息,而且还不错。如果您对此方法有任何疑问,请告诉我。

I just used soapUI to call getIssuesFromJqlSearch on jira.atlassian.com, and it worked fine. Do you have the same version installed? Anyway, you can use soapUI to analyze WSDL and test all the methods: you'll then isolate if the problem is with your JIRA or with the code that calls the method.

By the way, in JIRA Client we do use RSS XML to download most of the information, and it's not that bad. Let me know if you have any questions with this method.

浪漫之都 2024-08-28 06:22:07

当前版本的 jira4r 确实很旧。 实际源代码已更新,但 gem 尚未更新,因此我已克隆github 存储库 并发布了我自己的 gem jira4r-jh 适用于最新的 jira api 版本。

the current version of jira4r is really old. The actual source code has been updated but not the gem so I have cloned the repository to github and released my own gem jira4r-jh which works with the latest jira api version.

小…红帽 2024-08-28 06:22:07

你安装了哪个版本的 Jira???...如果是 3.1x,那么它将无法工作。 getIssuesFromJqlSearch 方法仅支持 jira 版本 4.X。

问候

Which version of Jira you have installed???... if its 3.1x, then it will not work. getIssuesFromJqlSearch method is only supported for jira version 4.X.

Regards

世态炎凉 2024-08-28 06:22:07

这适用于使用 soapUI 的我,但不适用于运行 4.01 的 jira4r。问题在于jira4r(我运行的是v0.3.0)。看来 wsdl 和关联的驱动程序代码是硬连线的,并且这不包括“getIssuesFromJqlSearch”调用。在 ruby/gems/1.8/gems/jira4r-0.3.0 中进行搜索以了解我的意思。搜索“getVersions”揭示了这一点:

./lib/jira4r/v2/jira_soap_service_driver.rb
./wsdl/jirasoapservice-v2.wsdl

搜索“getIssuesFromJqlSearch”时没有显示任何内容。

我通过将 ./wsdl/jirasoapservice-v2.wsdl 替换为我的 Jira 实例中的版本(位于 http://your-jira- instance/rpc/soap/jirasoapservice-v2?wsdl),然后通过修补 ./lib/jira4r/v2/jira_soap_service_driver.rb (看起来它是从 WSDL 自动生成的)适当地,通过添加以下内容:

[ XSD::QName.new(NsSoapRpcJiraAtlassianCom, "getIssuesFromJqlSearch"),
  "",
  "getIssuesFromJqlSearch",
  [ ["in", "in0", ["::SOAP::SOAPString"]],
    ["in", "in1", ["::SOAP::SOAPString"]],
    ["in", "in2", ["::SOAP::SOAPInt"]],
    ["retval", "getIssuesFromJqlSearchReturn", ["Jira4R::V2::ArrayOf_tns1_RemoteIssue", "http://jira.atlassian.com/rpc/soap/jirasoapservice-v2", "ArrayOf_tns1_RemoteIssue"]] ],
  { :request_style =>  :rpc, :request_use =>  :encoded,
    :response_style => :rpc, :response_use => :encoded,
    :faults => {"Jira4R::V2::RemoteException_"=>{:use=>"encoded", :name=>"RemoteException", :ns=>"http://jira.atlassian.com/rpc/soap/jirasoapservice-v2", :namespace=>"http://jira.atlassian.com/rpc/soap/jirasoapservice-v2", :encodingstyle=>"http://schemas.xmlsoap.org/soap/encoding/"}} }
],

显然,如果jira4r从您的实例下载了正确的WSDL,以避免此类版本不兼容,那就太好了:)

This works for me using soapUI, but not from jira4r, running 4.01. The problem is with jira4r (I'm running v0.3.0). It seems that the wsdl and the associated driver code is hard-wired, and this does not include the 'getIssuesFromJqlSearch' call. Do a search in ruby/gems/1.8/gems/jira4r-0.3.0 to see what I mean. Searching for 'getVersions' reveals this:

./lib/jira4r/v2/jira_soap_service_driver.rb
./wsdl/jirasoapservice-v2.wsdl

While searching for 'getIssuesFromJqlSearch' shows nothing.

I fixed the issue by replacing ./wsdl/jirasoapservice-v2.wsdl with the version from my Jira instance (it's at http://your-jira-instance/rpc/soap/jirasoapservice-v2?wsdl) and then by patching ./lib/jira4r/v2/jira_soap_service_driver.rb (which looks like it's been automatically generated from the WSDL) appropriately, by adding this:

[ XSD::QName.new(NsSoapRpcJiraAtlassianCom, "getIssuesFromJqlSearch"),
  "",
  "getIssuesFromJqlSearch",
  [ ["in", "in0", ["::SOAP::SOAPString"]],
    ["in", "in1", ["::SOAP::SOAPString"]],
    ["in", "in2", ["::SOAP::SOAPInt"]],
    ["retval", "getIssuesFromJqlSearchReturn", ["Jira4R::V2::ArrayOf_tns1_RemoteIssue", "http://jira.atlassian.com/rpc/soap/jirasoapservice-v2", "ArrayOf_tns1_RemoteIssue"]] ],
  { :request_style =>  :rpc, :request_use =>  :encoded,
    :response_style => :rpc, :response_use => :encoded,
    :faults => {"Jira4R::V2::RemoteException_"=>{:use=>"encoded", :name=>"RemoteException", :ns=>"http://jira.atlassian.com/rpc/soap/jirasoapservice-v2", :namespace=>"http://jira.atlassian.com/rpc/soap/jirasoapservice-v2", :encodingstyle=>"http://schemas.xmlsoap.org/soap/encoding/"}} }
],

Obviously, it would be nice if jira4r downloaded the correct WSDL from your instance, to avoid these kinds of version incompatibilities :)

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文