addon-org.everit.jira.worklog.query.plugin.cor

[Andre Janssen]

Problem with worklogsByIssues.

If I try command https://s2a900en.be.srv.dev.sys:6080/jira/rest/jira-worklog-query/1/find/worklogsByIssues?startDate=2016-01-03&endDate=2016-10-09&user=U33925 in Internet explorer I get message "The webpage cannot be found" but when I execute it in Chrome I get a blank screen as result. Both are incorrect results.

I see following messages in the JIRA access log :

for Internet explorer : 10.222.75.210 864x24663x1 u33925 [12/Oct/2016:14:24:22 +0200] "GET /jira/rest/jira-worklog-query/1/find/worklogsByIssues?startDate=2016-01-03&endDate=2016-10-09&user=U81775 HTTP/1.1" 400 - 2954 "-" "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/7.0)" "1xwxeb3"

For Chrome : 10.222.75.210 870x24733x1 u33925 [12/Oct/2016:14:30:50 +0200] "GET /jira/rest/jira-worklog-query/1/find/worklogsByIssues?startDate=2016-01-03&endDate=2016-10-09&user=U81775 HTTP/1.1" 400 - 3095 "-" "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36" "1x6svj5"

Can you tell me what's wrong?

[Andre Janssen]

We just want to summarize the worked time out of our JIRA issues. And I just performed what is written in the documentation of this plug to understand how it works.

Refer to http://myjira/rest/jira-worklog-query/REST-API-VERSION/find/worklogsByIssues in the "Summarize worked time by issues" topic of the plugin documentation. 

So I first logged on to our JIRA instance and executed the command (URL) afterwards.

Though command https://s2a900en.be.srv.dev.sys:6080/jira/rest/jira-worklog-query/1/find/worklogs?startDate=2016-01-03&endDate=2016-10-09&user=U81775 based on documentation topic "Querying worklogs modified during an interval" (http://myjira/rest/jira-worklog-query/REST-API-VERSION/find/updatedWorklogs) returns output as described in the documenation. 

[Jonas Andersson]

A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn't follow the rules.

In the case of a REST API with a JSON payload, 400's are typically, and correctly I would say, used to indicate that the JSON is invalid in some way according to the API specification for the service.

What exactly are you trying to do? the "command" you enter is actually a URL, and the url might not want to be called with a GET request, but maybe with a POST.. If you tell us a bit more of what you are trying to accomplish with this URL, we might be able to guide you better.