Mass select for insight objects on object picker while creating issue in Jira Software

[Grzegorz]

Hi,

Is there any option for mass select for insight objects on object picker while creating issue in Jira Software? Something like hold SHIFT + select first object and last object.

Sometimes we need to add many objects in one issue and it will be an improvement.

Other option is to develop button (Select all visible), after using search field.

Anyone know workaround to add 100-200 objects without clicking them?

Thanks

[Hakan Bahadir]

Hello,

I wonder if the following would work for your case:

- Create a custom field (i.e. "Change Scope") for getting a text value and ask the user to specify a filter value at the time of issue creation.

- User enters "dev-app"

- When the issue is created, the Insight post function called "Assign object/s based on an IQL query based on data from an issue" can execute the IQL:

Name like ${Change Scope}

and add matching objects to the insight custom field. You can also review the placeholders page for other useful variable options. This way, the user does not need to select multiple servers manually.

On the other hand, there may be a challenge in this scenario. The user needs to know the keyword to type. Another solution could be grouping the servers for simplicity. i.e. Application, System, Microservice, etc. If the "dev-app" servers are hosting your "Microservice 1". Then you can create another Object Type for Microservices. Then map the servers hosting this microservice. This way, you can let the user select the Microservice name while creating the issue. And again, the insight post function can automatically find the related servers and update the second Insight Custom Field.

I hope that helps.

Cheers, 

Hakan Bahadir

Solutions Engineer 

[Grzegorz]

Thank You for response.
In our case there is not only name based scenarios but we will try with post funcitons.

'Select all visible' button or IQL in search view still will be the best option :)

[David Sumlin]

Unfortunately, I don't believe there's a workaround. :-(

[Grzegorz]

Maybe we could report it as new feature?