Insight - Object picker

[Sergei Miroshnikov]

Hello! 

In our organization we use Jira Service Management (4.14.1) for IT support issues and Insight as CMDB. Both - Server versions. 

In Insight our testing schema:

• object type: organization1 with sub-types pc, printers, users etc.
• object type: organization2 with sub-types pc, printers, users etc.
• ...
• infrastructure object types: - pc models, printer models etc.

the meaning of this 'organizations' is to give some users permissions to pick or view their asset in the future (of course, later there will be a rethinking and rework).

In our test project we use just one custom field to pick something related to issue - user, printer or software. This custom field insight configuration contains only object schema pointing without any filter scope.

So, when we creating an issue and want to pick some objects from, for example, 'organization8 ---> printers' we should scroll down all expanded organizations with all expanded object types. 

How can I change this behavior to see all object types (folders) folded in object picker? 

[Sergei Miroshnikov · Accepted solution]

I found workaround that is good for us for now, maybe later there will be better solution.

Maybe someone will find this helpful.

• in 'organisations' object type I added organisation objects 
• in every object type inside every subfolder added attribute 'organisation' with link to main 'organisation' object type 
• filled all needed fields with organisations (it is convenient to bulk editing if you have many objects)
• put 2 custom fields on issue screens - one with 'insight objects' type with objecttype=organisations and one 'Insight Referenced Objects' type with reference to previous field 
• next time on issue screen you can choose an organisation in first custom field and see everything (or maybe something like PC or printer if you tune it in custom field IQL query ) related to this organisation in other field.

[David Sumlin]

I'm confused as to what your object schema looks like.

It sounds like it is: (but this doesn't make sense since you can't have two object types named the same in the same schema)

Org1

• PC
• Printer
• User

Org2

• PC
• Printer
• User

[Sergei Miroshnikov]

Yes, like that on screenshot (not real one)

You can`t have two object types with same name in the same object type but in the same schema it`s ok

And you can fill one type with sub types and then copy it, so you have same object type with subfolders but without objects.