Rest endpoint to get connected Jira tickets for an Insight object does not filter unresolved tickets before subset is created

Issue Summary

The rest endpoint /objectconnectedtickets/[OBJECT_ID]/tickets to get connected Jira tickets for an Insight object, does by default exclude resolved tickets. However, these are filtered after the subset for the pagination is done – which could result in unresolved tickets being not included. Max limit is 50. 

Steps to Reproduce

1. Go to a Jira instance with JSM Premium and Insight enabled
2. Create a test object in Insight
3. Setup an Insight custom field and configure it to make the test object available for selection
4. Create 51 tickets where that Insight object is selected in the custom field
5. Go to the test object and click Show all filtered issues
6. You should see ticket 1-50, which is correct behaviour so far since the limit is 50 and all tickets are unresolved.
7. Go and resolve ticket 3 and 4 – then repeat step 5
8. You will now only see 48 tickets, and ticket 51  is not included

Expected Results

Given a list with tickets like below, and we want the first 5 unresolved tickets – we are supposed to get TICKET-1, TICKET-2, TICKET-5, TICKET-6, and TICKET-7.

* TICKET-1 (unresolved)
* TICKET-2 (unresolved)
* TICKET-3 (resolved)
* TICKET-4 (resolved)
* TICKET-5 (unresolved)
* TICKET-6 (unresolved)
* TICKET-7 (unresolved)
* TICKET-8 (unresolved)
* TICKET-9 (unresolved)
* TICKET-10 (unresolved)

Actual Results

Given a list with tickets like below, and we want the first 5 unresolved tickets – we are currently getting only 3 tickets back that are TICKET-1, TICKET-2, and TICKET-5. 

* TICKET-1 (unresolved)
* TICKET-2 (unresolved)
* TICKET-3 (resolved)
* TICKET-4 (resolved)
* TICKET-5 (unresolved)
* TICKET-6 (unresolved)
* TICKET-7 (unresolved)
* TICKET-8 (unresolved)
* TICKET-9 (unresolved)
* TICKET-10 (unresolved)

Workaround

The workaround today is to use the iqlFunction in JQL to get the correct result of connected Jira tickets.