Automation for Jira - Insight

[gwn]

Using Automation for Jira for editing some created issues, but when choosing the customfield from Insight I only get "No options ".

I can select from the custom field elsewhere in jira when creating or editing a issue, but not 

through Automtion for Jira, any hints on what I am doing wrong?

[Matthew Dell]

I think this affects anyone who has upgraded Insight >= 8.4 and uses Automation for Jira's "Edit" action to search for objects to set values on Insight CFs.

I've found that Automation for Jira is using a replaced Insight API endpoint in Insight versions >= 8.4

https://documentation.mindville.com/insight/latest/preparing-for-insight-version-8-4-36953678.html#PreparingforInsightVersion8.4-ObjectsYellowchanged

Automation for Jira is using:

/rest/insight/1.0/objecttype/{id}/objects

which was REPLACED by:

/rest/insight/1.0/iql/objects?iql=objectTypeId={id}

So it returns "no objects" when you search for values to set, but you could set the value using the "additional fields" section. Rules that set Insight CF values continue to work because you aren't searching for values.

[Andrew Laden]

Since Atlassian now owns Insight and Automation, are they fixing this? Is the a jira issue to track?

[Matthew Dell]

Atlassian owns Automation for Jira, not Insight. They responded to my support ticket this morning that they expect to release a fix in v7.1.18 of Automation for Jira.

Here's the bug in the public tracker: https://jira.atlassian.com/browse/JIRAAUTOSERVER-34

[Sandra _Mindville_]

Atlassian actually owns both now, Automation for Jira and Insight :) 

https://www.atlassian.com/blog/announcements/atlassian-acquires-mindville

[Matthew Dell]

Whoa! I hadn't heard. Thanks for the correction.

[Phil Evans]

This bug is fixed i think (although no update on tracker)

There were updates and you can use Insight fields in AFJ and kind of choose objects, but when i try to choose object i need - its not there! There are some, a bunch of objects from different objects types, but what i want to choose is like not available.

So what i think is that AFJ doesn't take into account that theres IQL filter on custom field.

Do you guys have the same?

Please tell me how is it going for you now?

[Matthew Dell]

I've been in contact with Atlassian support about this. They fixed the bug to use the appropriate Insight REST endpoint per Insight version.
Unfortunately, they haven't accounted for pagination or number of objects returned by the >= Insight 8.4.x API endpoint.
At default, it will return only the 1st 25 objects from each object type. They've told me it will be addressed in another version of Automation for Jira.
I've also expressed that their goal should be to use the custom field's configuration to return objects.

[Phil Evans]

Some proper news here! Thank you, Matthew.

[Matthew Dell]

I've run into this issue as well. Existing rule Edit actions which set values for Insight CFs continue to work, but I cannot change the Insight CF field values in the rule actions or add new actions to the rule chain that set Insight CFs. "No Options" is always the result, even if entering or copy/pasting exact object label with object key. I ended up opening a request with Atlassian support. No solution has been offered yet.

[Andrew Laden]

Take a look at https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Insight-Asset-Management-and-Automation-for-JIRA-Missing-fields/qaq-p/853694 and see if that is similar to what you are trying to do.

In particular how you may have to use more options to specify in JSON what you are trying to do.

[gwn]

I got it working earlier, but something happend. The ones I made before are still working but I cant edit then, and I can't create new ones.