nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Insight custom field picker only retrieves first 50 results

t_s_llc

I am testing out Insight as a CMDB for our tickets' linked assets. I set up a custom field on our tickets for my Insight schema that includes all of our assets, but when I click the dropdown it only returns the first 50 objects I've created. If I search, it only searches based on those 50 results, too. Am I doing something wrong, or is this a limitation?

Accepted answers

All comments

Gonchik Tsymzhitov

Hi!

Please, visit to configuration in admin, then you can find 50 results in dropdown,

you can adjust.

But what is the purpose of that? I am asking it will reflect to performance and UX.

i.e. io Google search suggested 10 hot results

Hakan Bahadir_l20svj

Hello,

A quick question, are you using the Insight Marketplace Application or the new Insight feature which comes with JSM Premium?

Thanks.

Hakan Bahadir

Solution Architect

Eric Littler

I actually don't mind that it limits the drop down to 50 results.

But the real problem for me is, when I start searching, it only returns results from within those 50 results. So if I'm searching an asset starting with a Z, it returns nothing. Seems like a bug.

Eric Littler

I'm using the new Insight feature with JSM Premium. I'm on a trial right now, if that matters.

Rafael Tejero Palma

Hi Eric,

Have you found a solution to this behavior?

One of my customers has the same problem, but I can't find a way to solve it.

Many thanks.

Eric Littler

Hello, Rafael.

Not exactly. To recap, I only got the first 50 results and when I searched it was only from those 50 results.

What I noticed is it was happening in a pop up screen (like when I transitioned a workflow), but not on the regular issue page. So I took the asset field out of the Resolve Issue screen and only add them from the main ticket now. I haven't tested in a while if the issue has gone away on its own.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management