Assign a value to an Insight Custom Field

[Eugen G.]

Hello community,

On our Jira Service Management with started configuring (the integrated) Insight module. The Object Schema and first Object Type with some Objects inside have been created.

Now, we would like to utilise the contents of these Objects in Jira SM tickets.

A custom field for an insight object has been created (let's call it "InsightCF"). The Field Scope looks as follows:

If we add the InsightCF to a screen, we are able to start searching and select a value. So far so good.

Next (the challenge), we want to display only values, which match the following criteria:

Email (Insight Attribute) = Reporter (from Ticket)

We have tried the following - none worked.

• Email like ${reporter}
• Email = ${reporter}
• Email = ${reporter.emailAddress}

As said, if we clear the "Filter issue scope (IQL)", we see all values from the objectType "Users" again.

Thoughts, what I am missing?

[Gaurav]

Hello @Eugen G. 

Welcome to the community!!

Based on my understanding, you wish the 'InsightCF' to reflect the Email address and Location of the issue Reporter, on the issue view screen.

In this case, I would suggest you leverage automation rules and set the fields post-issue creation.

Please let me know if this helps.

[Eugen G.]

Hi Gaurav,

That's correct, however, your suggestion was intended to be our step 2.

As we were not able to get the field show what we wanted, our plan was to clarify, whether we are doing something incorrectly.

Will try it though

Best,
Eugen

[Eugen G.]

Hi @Gaurav ,

So, I implemented the automation. It works without any issues using

Email = {{reporter.emailAddress}}

That still leaves the question what to enter into the "Filter issue scope (IQL)" to prefilter the list.

[Gaurav]

@Eugen G. As we are using the Automation rule, to populate the field, is there still a need to prefilter the list?

[Eugen G.]

Hi @Gaurav ,

For this particular scenario not. It would be still interesting to know, why it's not working. This is the reason me asking. So far I got a workaround, but not a solution ;)