Dear all,
we agree that current solution may not be suitable for all cases as well as user experience may not be very smooth. This ticket reports only a break in A4J and Insight apps and that was recovered hence the status of the issue set to Done.
For any changes in the behaviour of the integration we need a separate Feature Request ticket(s) with the description what behaviour is requested.

Daniel Ramotowski

Atlassian introduced a new problem since I last investigated this. The iql query sent by A4J assumes that "Name" is always the label attribute of Insight object types. It fails to account for the changing of an object type's label to any other text attribute or the renaming of the default "Name" attribute. Any object type which does not use "Name" as the label will be excluded from A4J results.

I agree this is NOT resolved.

As Matthew already stated, this issue is definitely not resolved!
I already pointed out the exact same thing to the Atlassian/A4J support back in November 2020 (JSP-413692).

Besides a possibility to search for an insight object key would also be helpful in this regard.

edit (as I took too long to send the comment...):

Altough the fix certainly made the selection of objects somewhat possible again, this is far from a real solution or good user experience and there are still many cases where it remains impossible to select certain objects.

Just to somewhat showcase our usecase the excerpt of my ticket with the Atlassian support:

Imagine an object schema that contains 30 objects with the exact same name "Atlassian Support", trying to search for that term in A4J results in only 25 objects, therefore making the other five impossible to select.

Although that example might look stupid at first, imagine a sizable instance of Insight with thousands and thousands of objects (over 50.000 in our case), many coming from external datasources where I have no control over.
With that in mind it is easily possible to have multiple objects with similar or even the same name within Insight.

Hi matthew.r.dell, 

concern for this ticket was to re-enable A4J and Insight integration with new API. Pagination was not supported in previous A4J versions.

A4J version 7.2.3 introduced 'query as you type ' in insight object dropdown, so lack of pagination was mitigated by narrowing the results.

If pagination is still expected, feature request could be opened.

Cheers

Daniel Ramotowski

This should be reopened. The fix in 7.2.2 and improvement in 7.2.3 checks which version of Insight is installed then uses the appropriate API endpoint for the Insight version. The problem is it does not account for the paginated results returned by 8.4 endpoint:
/rest/insight/1.0/iql/objects?iql=objectTypeId={id}
 

So A4J only returns results from the 1st page of responses for each object type. The default return is 25 objects per page. This leaves many objects unsearchable.

They'd need to use the "resultPerPage" parameter to include more objects or paginate through results using the "page" parameter.

Opinion: A better solution is to retrieve the object schema and IQL query of the selected Insight custom field context configuration for the project scope of the rule and return only applicable results. Right now, A4J searches every single object type, even those outside of the CF's context; that seems inefficient.

I have tested it. Still does not work.

Hi dave.bosman, fe9534534cb0

fix You are looking for was provided in A4J 7.2.2 and improved in 7.2.3.

I'd suggest upgrade to 7.2.3.

Regards

Daniel Ramotowski

Why is this not done yet? 

Automation for Jira was one of the best selling plugins before Atlassian bought it. Bugs where fixed in 1 or 2 days when reported. 

Since Atlassian bought the plugin this level of customer support vanished as this is already reported over a year ago and is still not fixed. 

The workaround is good for IT people, but a lot of project leads/admins are non technical so this is not a viable workaround.  

Same.