Rest endpoint to get connected Jira tickets for an Insight object does not filter unresolved tickets

Issue Summary

The rest endpoint /objectconnectedtickets/[OBJECT_ID]/tickets to get connected Jira tickets for an Insight object, does by default exclude resolved tickets.

Steps to Reproduce

1. Go to a Jira instance with JSM 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 10 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 10 tickets, which is correct behavior.
7. Go and resolve ticket couple of tickets – then repeat step 5
8. You will now only see 8 tickets, and resolved ticket is not included

Expected Results

All tickets including the resolved tickets should be available

Actual Results

Only the unresolved tickets are visible

Workaround

Create an issue filter in Jira and use the param "filterId" in the HTTP request. This way, you can get whichever connectedTicket within the JQL filter, by calling:

For example:

Save a JQL Filter, showing any Issue of a specific Project, then use it in the REST Call as shown below:

http://<yourJira>/rest/insight/1.0/objectconnectedtickets/6109/tickets?filterId=10400

This will return ALL Jira Issues within my filter, which are connected to the Object's ID indicated, regardless of the Issue's Status.

Note:
The correct API was noted in the Insight 8.4 Changes - but current documentation is missing .../tickets and need updating.
The workaround should also be added to the documentation (was included in older version of the Insight REST APIs documentation).