Konrad Garus added a comment - 19/Sep/2018 3:29 PM I found the issue in JSD codebase. Using sources decompiled by Intellij IDEA, but it gives you the idea. Let's say there are 70 requests for the user, and I'm running a query with start=50. That means there should be 20 requests on the page. Now, see comments in code below. ServiceDeskCustomerRequestServiceImpl : public Either<AnError, PagedResponse<CustomerRequest>> getCustomerRequests(@Nullable ApplicationUser user, @Nonnull CustomerRequestQuery customerRequestQuery) { Assertions.notNull( "customerRequestQuery" , customerRequestQuery); return Steps.begin( this .userFactory.wrap(user)).then((cu) -> { return this .dispatchCustomerRequestQuery(cu.forJIRA(), customerRequestQuery); }).yield((cu, customerRequests) -> { return customerRequests; }).map((input) -> { // At this point input is a list of 20 CustomRequests return PagedResponseImpl.toPagedResponse(customerRequestQuery.pagedRequest(), input); }); } PagedResponseImpl : public static <T> PagedResponse<T> toPagedResponse(LimitedPagedRequest limitedPagedRequest, List<T> items) { // items has 20 entries, limitedPageRequest.start=50 return filteredPageResponse(limitedPagedRequest, items, Predicates.alwaysTrue()); } public static <T> PagedResponse<T> filteredPageResponse(LimitedPagedRequest limitedPagedRequest, List<T> items, Predicate<? super T> predicate) { if (predicate == null ) { predicate = Predicates.alwaysTrue(); } boolean hasMore = items.size() > limitedPagedRequest.getStart() + limitedPagedRequest.getLimit(); // This takes the iterable of 20 items and skips 50, so the result is empty. BAM! List<T> filteredItems = FluentIterable.from(items).skip(limitedPagedRequest.getStart()) .limit(limitedPagedRequest.getLimit()).filter(predicate).toList(); return from(filteredItems, hasMore).pageRequest(limitedPagedRequest).build(); } One way to fix this to replace the call in getCustomerRequests : // From: return PagedResponseImpl.toPagedResponse(customerRequestQuery.pagedRequest(), input); // To: LimitedPagedRequest pagedRequest = customerRequestQuery.pagedRequest(); boolean hasMore = input.size() > pagedRequest.getStart() + pagedRequest.getLimit(); return PagedResponseImpl.from(input, hasMore).pageRequest(pagedRequest).build();

Konrad Garus added a comment - 19/Sep/2018 12:07 PM This is a disastrous show-stopper, not a low-priority bug that deserves no attentions for years. Since the assignee is showing as inactive, does it mean it will take 2 more years for someon to notice it again?