Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Assets/Insight restrict attributes in portal

Is there a way to restrict the visibility of Insight attributes in the JSM/SD portal when using the object picker.
For reference the object picket is the dialog that appears and allows an advanced search using the magnifying glass next to the insight CF on the portal create request screen.

1 answer

0 votes
Peter-Dave Sheehan
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 02, 2023

Either via the type-ahead or the magnifying glass, the list is subject to whatever IQL filter you've applied in the custom field context.

If you want a different list in the portal vs jira, then you need to have an IQL that will render differently based on default values and IQL placeholders.

If you can have a custom field that has a different value when you're in Jira or when you're in the Portal, then you can use that value as a way to filter the objects.

This works best if you also have scriptrunner so you can hide that field.

Then in your objects, you might need an attribute like "Applicable to" that will contain some values that can be used to match against the various default values in the form. For example, it can contain just "Jira", just "Portal", or "Jira,Portal".

Then the IQL would look something like

"Applicable To" like ${ApplicableToCustomFieldName}

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events