Filter issue scope with a custom User field

[Patrick Doyle]

I have an insight object with an 'Owner' User attribute and a custom User select field 'Current Owner'.  I am trying to filter an Insight object field so that only objects where the Owner and Current Owner match are listed.

This works: Owner=${reporter}

But these don't:

Owner=${customfield_123}

Owner=${Current Owner}

Owner=${currentOwner}

Owner.User=${customfield_123}

Owner.User=${customfield_123.User}

and various other combinations.

What is the correct way to do this?

[Santiago Estel]

Just to let you know that this issue was resolved on Jira Core 9.12.15, and now we can use this as Filter Issue Scope (AQL):

Employee = ${Customer}

Having Employee being the attribute on the Object Type, and Customer a user-picker custom field on the Jira ticket.

[Santiago Estel]

This a bug (yes a bug) that was introduced in Jira version 8.4.

This article explains the issue

https://confluence.atlassian.com/jirakb/setting-a-user-picker-jira-custom-field-as-source-in-an-insight-custom-field-won-t-work-1077910546.html

Based on the above article, now, it's not possible (as it's used to be) just to have one user picker custom field and use it on "Filter Issue Scope (IQL)" in this way:

"Custodian" = ${customfield_908342}

Now, it seems that you need to create two Insight Objects, one for your catalog of users, and the other the working object, then, create an Insight Custom field to read from the catalog of users, and then use that Insight Custom field on the "Filter Issue Scope (IQL)" of the Insight custom field that will retrieve the objects from the actual working object.

This is not good at all...

[Mark Segall]

Hi @Patrick Doyle - Is this something you're trying to present on the portal as the user is requesting the issue or something you're presenting to the agents after the issue is already created? I ask because this will have impacts on how you need to set up the object schema.

[Patrick Doyle]

In this case it's actually just for the agents, I was hoping to give them a way update the owner or other attributes of an Insight object using an Automation rule.  I guess it should only be needed on the agent's create issue screen.  

[Mark Segall]

That makes it easier.  Perhaps try this...

Owner=${customfield_123.displayName}

[Patrick Doyle]

Hmm that didn't work...

[Mark Segall]

I was afraid of that because it worked ok with Owner = ${Reporter} which would mean that Owner is captured as a Jira ID.  So, technically your first example should work. Perhaps try:

Owner = ${customfield_123.name}

or 

Owner = ${customfield_123.label}

Apologies for having you try a bunch of different options.  I don't have Insight available to me in my test environment. 

[Patrick Doyle]

No dice.

[Mark Segall]

Maybe try mapping against name?

(Assuming the Object Name is the Owner's name)

Owner.Name = {customfield_123.displayName}

Owner.Name = {customfield_123.label}

Owner.Name = {customfield_123.name}

[Steve Schepens]

Did you managed to solve this? I'm having the same issue...