subject:"\[jira\] \(MCHANGES\-351\) No paging when maxEntries is reached"

[jira] (MCHANGES-351) No paging when maxEntries is reached

2015-01-26 Thread Bernd Eckenfels (JIRA)


[ 
https://jira.codehaus.org/browse/MCHANGES-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361840#comment-361840
 ] 

Bernd Eckenfels commented on MCHANGES-351:
--

The ASF INFRA team does not want to raise that limit on their Jira instance: 
https://issues.apache.org/jira/browse/INFRA-9059

 No paging when maxEntries is reached
 

 Key: MCHANGES-351
 URL: https://jira.codehaus.org/browse/MCHANGES-351
 Project: Maven Changes Plugin
  Issue Type: Wish
  Components: jira
Affects Versions: 2.11
 Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels

 I try to generate a JIRA changes report for apache commons VFS. If I set the 
 maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
 to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
 case there are 141 bugs in the current fixversion and the query finds 295).
 According to the JIRA docu you can query with different offsets, so would it 
 be possible to query startAt=0-99,100-199,... and so on?
 Here is the request and the response:
 {code}
 Address: https://issues.apache.org/jira/rest/api/2/search
 Http-Method: POST
 Content-Type: application/json
 Headers: {Accept=[application/json], Content-Type=[application/json],
 Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
 (1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
 key DESC,maxResults:600,fields:[*all]...
 Response-Code: 200
 Encoding: UTF-8
 Content-Type: application/json;charset=UTF-8
 Headers: \{Cache-Control=[no-cache, no-store, no-transform],
 connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
 Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
 Server=[Apache-Coyote/1.1], 
 Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
 HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
 X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], 
 X-Content-Type-Options=[nosniff]}
 Messages:
 Message (saved to tmp file):
 Filename:
 C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
 (message truncated to 102400 bytes)
 Payload:
 {expand:schema,names,startAt:0,maxResults:100,total:295, ...
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHANGES-351) No paging when maxEntries is reached

2015-01-23 Thread SebbASF (JIRA)


[ 
https://jira.codehaus.org/browse/MCHANGES-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361713#comment-361713
 ] 

SebbASF commented on MCHANGES-351:
--

There are two aspects to this:

* output pagination support so output pages don't become too large
* retrieval pagination so the plugin is able to retrieve more than the API 
limit (this issue)

These should be treated as independent; it may well be that the JIRA instance 
has a lower maxEntries setting than would fit reasonably on an web page.

 No paging when maxEntries is reached
 

 Key: MCHANGES-351
 URL: https://jira.codehaus.org/browse/MCHANGES-351
 Project: Maven Changes Plugin
  Issue Type: Wish
  Components: jira
Affects Versions: 2.11
 Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels

 I try to generate a JIRA changes report for apache commons VFS. If I set the 
 maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
 to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
 case there are 141 bugs in the current fixversion and the query finds 295).
 According to the JIRA docu you can query with different offsets, so would it 
 be possible to query startAt=0-99,100-199,... and so on?
 Here is the request and the response:
 {code}
 Address: https://issues.apache.org/jira/rest/api/2/search
 Http-Method: POST
 Content-Type: application/json
 Headers: {Accept=[application/json], Content-Type=[application/json],
 Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
 (1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
 key DESC,maxResults:600,fields:[*all]...
 Response-Code: 200
 Encoding: UTF-8
 Content-Type: application/json;charset=UTF-8
 Headers: \{Cache-Control=[no-cache, no-store, no-transform],
 connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
 Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
 Server=[Apache-Coyote/1.1], 
 Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
 HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
 X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], 
 X-Content-Type-Options=[nosniff]}
 Messages:
 Message (saved to tmp file):
 Filename:
 C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
 (message truncated to 102400 bytes)
 Payload:
 {expand:schema,names,startAt:0,maxResults:100,total:295, ...
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHANGES-351) No paging when maxEntries is reached

2015-01-19 Thread Michael Osipov (JIRA)


[ 
https://jira.codehaus.org/browse/MCHANGES-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361387#comment-361387
 ] 

Michael Osipov edited comment on MCHANGES-351 at 1/19/15 7:08 AM:
--

Bernd, this isn't a bug because the changes plugin does not have paging support 
at all. See: MCHANGES-98


was (Author: michael-o):
Bernd, this isn't a bug because the changes plugin does not hat paging support 
at all. See: MCHANGES-98

 No paging when maxEntries is reached
 

 Key: MCHANGES-351
 URL: https://jira.codehaus.org/browse/MCHANGES-351
 Project: Maven Changes Plugin
  Issue Type: Bug
  Components: jira
Affects Versions: 2.11
 Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels

 I try to generate a JIRA changes report for apache commons VFS. If I set the 
 maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
 to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
 case there are 141 bugs in the current fixversion and the query finds 295).
 According to the JIRA docu you can query with different offsets, so would it 
 be possible to query startAt=0-99,100-199,... and so on?
 Here is the request and the response:
 {code}
 Address: https://issues.apache.org/jira/rest/api/2/search
 Http-Method: POST
 Content-Type: application/json
 Headers: {Accept=[application/json], Content-Type=[application/json],
 Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
 (1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
 key DESC,maxResults:600,fields:[*all]...
 Response-Code: 200
 Encoding: UTF-8
 Content-Type: application/json;charset=UTF-8
 Headers: \{Cache-Control=[no-cache, no-store, no-transform],
 connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
 Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
 Server=[Apache-Coyote/1.1], 
 Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
 HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
 X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], 
 X-Content-Type-Options=[nosniff]}
 Messages:
 Message (saved to tmp file):
 Filename:
 C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
 (message truncated to 102400 bytes)
 Payload:
 {expand:schema,names,startAt:0,maxResults:100,total:295, ...
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHANGES-351) No paging when maxEntries is reached

2015-01-19 Thread Michael Osipov (JIRA)


[ 
https://jira.codehaus.org/browse/MCHANGES-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361387#comment-361387
 ] 

Michael Osipov commented on MCHANGES-351:
-

Bernd, this isn't a bug because the changes plugin does not hat paging support 
at all. See: MCHANGES-98

 No paging when maxEntries is reached
 

 Key: MCHANGES-351
 URL: https://jira.codehaus.org/browse/MCHANGES-351
 Project: Maven Changes Plugin
  Issue Type: Bug
  Components: jira
Affects Versions: 2.11
 Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels

 I try to generate a JIRA changes report for apache commons VFS. If I set the 
 maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
 to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
 case there are 141 bugs in the current fixversion and the query finds 295).
 According to the JIRA docu you can query with different offsets, so would it 
 be possible to query startAt=0-99,100-199,... and so on?
 Here is the request and the response:
 {code}
 Address: https://issues.apache.org/jira/rest/api/2/search
 Http-Method: POST
 Content-Type: application/json
 Headers: {Accept=[application/json], Content-Type=[application/json],
 Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
 (1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
 key DESC,maxResults:600,fields:[*all]...
 Response-Code: 200
 Encoding: UTF-8
 Content-Type: application/json;charset=UTF-8
 Headers: \{Cache-Control=[no-cache, no-store, no-transform],
 connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
 Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
 Server=[Apache-Coyote/1.1], 
 Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
 HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
 X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], 
 X-Content-Type-Options=[nosniff]}
 Messages:
 Message (saved to tmp file):
 Filename:
 C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
 (message truncated to 102400 bytes)
 Payload:
 {expand:schema,names,startAt:0,maxResults:100,total:295, ...
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHANGES-351) No paging when maxEntries is reached

2015-01-19 Thread Bernd Eckenfels (JIRA)


 [ 
https://jira.codehaus.org/browse/MCHANGES-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Eckenfels updated MCHANGES-351:
-

Issue Type: Wish  (was: Bug)

 No paging when maxEntries is reached
 

 Key: MCHANGES-351
 URL: https://jira.codehaus.org/browse/MCHANGES-351
 Project: Maven Changes Plugin
  Issue Type: Wish
  Components: jira
Affects Versions: 2.11
 Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels

 I try to generate a JIRA changes report for apache commons VFS. If I set the 
 maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
 to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
 case there are 141 bugs in the current fixversion and the query finds 295).
 According to the JIRA docu you can query with different offsets, so would it 
 be possible to query startAt=0-99,100-199,... and so on?
 Here is the request and the response:
 {code}
 Address: https://issues.apache.org/jira/rest/api/2/search
 Http-Method: POST
 Content-Type: application/json
 Headers: {Accept=[application/json], Content-Type=[application/json],
 Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
 (1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
 key DESC,maxResults:600,fields:[*all]...
 Response-Code: 200
 Encoding: UTF-8
 Content-Type: application/json;charset=UTF-8
 Headers: \{Cache-Control=[no-cache, no-store, no-transform],
 connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
 Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
 Server=[Apache-Coyote/1.1], 
 Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
 HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
 X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], 
 X-Content-Type-Options=[nosniff]}
 Messages:
 Message (saved to tmp file):
 Filename:
 C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
 (message truncated to 102400 bytes)
 Payload:
 {expand:schema,names,startAt:0,maxResults:100,total:295, ...
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHANGES-351) No paging when maxEntries is reached

2015-01-19 Thread Bernd Eckenfels (JIRA)


[ 
https://jira.codehaus.org/browse/MCHANGES-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361397#comment-361397
 ] 

Bernd Eckenfels commented on MCHANGES-351:
--

I think MCHANGES-98 is about missing output paging / better representation. 
This Bug is about the input (RESAT query) paging.

But I agree you can also call this a missing feature not a bug (in any case its 
not useable for my project).

 No paging when maxEntries is reached
 

 Key: MCHANGES-351
 URL: https://jira.codehaus.org/browse/MCHANGES-351
 Project: Maven Changes Plugin
  Issue Type: Wish
  Components: jira
Affects Versions: 2.11
 Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels

 I try to generate a JIRA changes report for apache commons VFS. If I set the 
 maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
 to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
 case there are 141 bugs in the current fixversion and the query finds 295).
 According to the JIRA docu you can query with different offsets, so would it 
 be possible to query startAt=0-99,100-199,... and so on?
 Here is the request and the response:
 {code}
 Address: https://issues.apache.org/jira/rest/api/2/search
 Http-Method: POST
 Content-Type: application/json
 Headers: {Accept=[application/json], Content-Type=[application/json],
 Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
 (1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
 key DESC,maxResults:600,fields:[*all]...
 Response-Code: 200
 Encoding: UTF-8
 Content-Type: application/json;charset=UTF-8
 Headers: \{Cache-Control=[no-cache, no-store, no-transform],
 connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
 Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
 Server=[Apache-Coyote/1.1], 
 Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
 HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
 X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], 
 X-Content-Type-Options=[nosniff]}
 Messages:
 Message (saved to tmp file):
 Filename:
 C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
 (message truncated to 102400 bytes)
 Payload:
 {expand:schema,names,startAt:0,maxResults:100,total:295, ...
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHANGES-351) No paging when maxEntries is reached

2015-01-19 Thread Bernd Eckenfels (JIRA)


[ 
https://jira.codehaus.org/browse/MCHANGES-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361397#comment-361397
 ] 

Bernd Eckenfels edited comment on MCHANGES-351 at 1/19/15 8:54 AM:
---

I think MCHANGES-98 is about missing output paging / better representation. 
This Bug is about the input (REST query) paging.

But I agree you can also call this a missing feature not a bug (in any case its 
not useable for my project).


was (Author: eckes):
I think MCHANGES-98 is about missing output paging / better representation. 
This Bug is about the input (RESAT query) paging.

But I agree you can also call this a missing feature not a bug (in any case its 
not useable for my project).

 No paging when maxEntries is reached
 

 Key: MCHANGES-351
 URL: https://jira.codehaus.org/browse/MCHANGES-351
 Project: Maven Changes Plugin
  Issue Type: Wish
  Components: jira
Affects Versions: 2.11
 Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels

 I try to generate a JIRA changes report for apache commons VFS. If I set the 
 maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
 to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
 case there are 141 bugs in the current fixversion and the query finds 295).
 According to the JIRA docu you can query with different offsets, so would it 
 be possible to query startAt=0-99,100-199,... and so on?
 Here is the request and the response:
 {code}
 Address: https://issues.apache.org/jira/rest/api/2/search
 Http-Method: POST
 Content-Type: application/json
 Headers: {Accept=[application/json], Content-Type=[application/json],
 Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
 (1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
 key DESC,maxResults:600,fields:[*all]...
 Response-Code: 200
 Encoding: UTF-8
 Content-Type: application/json;charset=UTF-8
 Headers: \{Cache-Control=[no-cache, no-store, no-transform],
 connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
 Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
 Server=[Apache-Coyote/1.1], 
 Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
 HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
 X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], 
 X-Content-Type-Options=[nosniff]}
 Messages:
 Message (saved to tmp file):
 Filename:
 C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
 (message truncated to 102400 bytes)
 Payload:
 {expand:schema,names,startAt:0,maxResults:100,total:295, ...
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHANGES-351) No paging when maxEntries is reached

2015-01-19 Thread Michael Osipov (JIRA)


[ 
https://jira.codehaus.org/browse/MCHANGES-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361415#comment-361415
 ] 

Michael Osipov commented on MCHANGES-351:
-

I think MCHANGES-98 can handle both with a config parameter.

 No paging when maxEntries is reached
 

 Key: MCHANGES-351
 URL: https://jira.codehaus.org/browse/MCHANGES-351
 Project: Maven Changes Plugin
  Issue Type: Wish
  Components: jira
Affects Versions: 2.11
 Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels

 I try to generate a JIRA changes report for apache commons VFS. If I set the 
 maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
 to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
 case there are 141 bugs in the current fixversion and the query finds 295).
 According to the JIRA docu you can query with different offsets, so would it 
 be possible to query startAt=0-99,100-199,... and so on?
 Here is the request and the response:
 {code}
 Address: https://issues.apache.org/jira/rest/api/2/search
 Http-Method: POST
 Content-Type: application/json
 Headers: {Accept=[application/json], Content-Type=[application/json],
 Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
 (1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
 key DESC,maxResults:600,fields:[*all]...
 Response-Code: 200
 Encoding: UTF-8
 Content-Type: application/json;charset=UTF-8
 Headers: \{Cache-Control=[no-cache, no-store, no-transform],
 connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
 Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
 Server=[Apache-Coyote/1.1], 
 Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
 HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
 X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], 
 X-Content-Type-Options=[nosniff]}
 Messages:
 Message (saved to tmp file):
 Filename:
 C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
 (message truncated to 102400 bytes)
 Payload:
 {expand:schema,names,startAt:0,maxResults:100,total:295, ...
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHANGES-351) No paging when maxEntries is reached

2015-01-18 Thread Bernd Eckenfels (JIRA)

Bernd Eckenfels created MCHANGES-351:


 Summary: No paging when maxEntries is reached
 Key: MCHANGES-351
 URL: https://jira.codehaus.org/browse/MCHANGES-351
 Project: Maven Changes Plugin
  Issue Type: Bug
  Components: jira
Affects Versions: 2.11
 Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels


I try to generate a JIRA changes report for apache commons VFS. If I set the 
maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
case there are 141 bugs in the current fixversion and the query finds 295).

According to the JIRA docu you can query with different offsets, so would it be 
possible to query startAt=0-99,100-199,... and so on?

Here is the request and the response:

{quote}
Address: https://issues.apache.org/jira/rest/api/2/search
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[application/json], Content-Type=[application/json],
Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
(1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
key DESC,maxResults:600,fields:[*all]}

Response-Code: 200
Encoding: UTF-8
Content-Type: application/json;charset=UTF-8
Headers: {Cache-Control=[no-cache, no-store, no-transform],
connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
Server=[Apache-Coyote/1.1], 
Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], X-Content-Type-Options=[nosniff]}
Messages:
Message (saved to tmp file):
Filename:
C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
(message truncated to 102400 bytes)

Payload:
{expand:schema,names,startAt:0,maxResults:100,total:295, ...
{quote}




--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCHANGES-351) No paging when maxEntries is reached

2015-01-18 Thread Bernd Eckenfels (JIRA)


 [ 
https://jira.codehaus.org/browse/MCHANGES-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bernd Eckenfels updated MCHANGES-351:
-

Description: 
I try to generate a JIRA changes report for apache commons VFS. If I set the 
maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
case there are 141 bugs in the current fixversion and the query finds 295).

According to the JIRA docu you can query with different offsets, so would it be 
possible to query startAt=0-99,100-199,... and so on?

Here is the request and the response:

{code}
Address: https://issues.apache.org/jira/rest/api/2/search
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[application/json], Content-Type=[application/json],
Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
(1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
key DESC,maxResults:600,fields:[*all]...

Response-Code: 200
Encoding: UTF-8
Content-Type: application/json;charset=UTF-8
Headers: \{Cache-Control=[no-cache, no-store, no-transform],
connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
Server=[Apache-Coyote/1.1], 
Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], X-Content-Type-Options=[nosniff]}
Messages:
Message (saved to tmp file):
Filename:
C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
(message truncated to 102400 bytes)

Payload:
{expand:schema,names,startAt:0,maxResults:100,total:295, ...
{code}


  was:
I try to generate a JIRA changes report for apache commons VFS. If I set the 
maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
case there are 141 bugs in the current fixversion and the query finds 295).

According to the JIRA docu you can query with different offsets, so would it be 
possible to query startAt=0-99,100-199,... and so on?

Here is the request and the response:

{quote}
Address: https://issues.apache.org/jira/rest/api/2/search
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[application/json], Content-Type=[application/json],
Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
(1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
key DESC,maxResults:600,fields:[*all]}

Response-Code: 200
Encoding: UTF-8
Content-Type: application/json;charset=UTF-8
Headers: {Cache-Control=[no-cache, no-store, no-transform],
connection=[Keep-Alive], content-type=[application/json;charset=UTF-8], 
Date=[Mon, 19 Jan 2015 01:50:37 GMT], Keep-Alive=[timeout=5, max=96], 
Server=[Apache-Coyote/1.1], 
Set-Cookie=[JSESSIONID=4871902251E72BC474B2D32941521F9A; Path=/jira/; Secure; 
HttpOnly], transfer-encoding=[chunked], X-AREQUESTID=[110x29767730x2], 
X-ASEN=[SEN-2062203], X-AUSERNAME=[anonymous], X-Content-Type-Options=[nosniff]}
Messages:
Message (saved to tmp file):
Filename:
C:\Users\eckenfel\AppData\Local\Temp\cxf-tmp-435678\cos4903552076318255093tmp
(message truncated to 102400 bytes)

Payload:
{expand:schema,names,startAt:0,maxResults:100,total:295, ...
{quote}



 No paging when maxEntries is reached
 

 Key: MCHANGES-351
 URL: https://jira.codehaus.org/browse/MCHANGES-351
 Project: Maven Changes Plugin
  Issue Type: Bug
  Components: jira
Affects Versions: 2.11
 Environment: Maven 3.2.5; Java 1.7.0_72 x64 on win7, german
Reporter: Bernd Eckenfels

 I try to generate a JIRA changes report for apache commons VFS. If I set the 
 maxEntries to 600 it wont work. It looks like the Apache Instance only allows 
 to search for 100 entries (JIRA On Demand seems to be limited to 1000). In my 
 case there are 141 bugs in the current fixversion and the query finds 295).
 According to the JIRA docu you can query with different offsets, so would it 
 be possible to query startAt=0-99,100-199,... and so on?
 Here is the request and the response:
 {code}
 Address: https://issues.apache.org/jira/rest/api/2/search
 Http-Method: POST
 Content-Type: application/json
 Headers: {Accept=[application/json], Content-Type=[application/json],
 Payload: {jql:project = VFS AND status in (5, 6) AND resolution in
 (1) AND type in (1, 2, 3, 4, 5, 6) ORDER BY fixversion DESC, type ASC,
 key DESC,maxResults:600,fields:[*all]...
 Response-Code: 200
 Encoding: UTF-8
 Content-Type: application/json;charset=UTF-8
 Headers: \{Cache-Control=[no-cache, no-store, no-transform],
 connection=[Keep-Alive],

[jira] (MCHANGES-351) No paging when maxEntries is reached

[jira] (MCHANGES-351) No paging when maxEntries is reached

[jira] (MCHANGES-351) No paging when maxEntries is reached

[jira] (MCHANGES-351) No paging when maxEntries is reached

[jira] (MCHANGES-351) No paging when maxEntries is reached

[jira] (MCHANGES-351) No paging when maxEntries is reached

[jira] (MCHANGES-351) No paging when maxEntries is reached

[jira] (MCHANGES-351) No paging when maxEntries is reached

[jira] (MCHANGES-351) No paging when maxEntries is reached

[jira] (MCHANGES-351) No paging when maxEntries is reached

10 matches

Site Navigation

Mail list logo

Footer information