You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
According to this documentation: https://docs.thinktilt.com/proforma/ProForma-User-Lookup-Fields.1571291698.html
There are only two options to configure the user picker.
Default Jira user search (Restricted)
Only users with permission to access Jira can lookup other Jira users.
This search will NOT work for customers and anonymous users in the Jira Service Desk portal.
Users with Browse Project permission
Both Jira and Portal users can lookup Jira users who have the Browse project permission for this project. This means that any user who has permission to see the project’s issues will be returned as an option in the user-lookup field.
I would like to know if there's a way to configure a proforma user picker such that using the 2nd option, and granting Browse Project to Service Desk Customers - Portal access will allows service desk customers with portal access to search for users.
This is because I have user pickers in conditional sections, so I can't use the JSM user picker. Some of my users have a JSM license, some don't have any license at all.
I would like to avoid granting everyone browse project permissions, because this would mean that those users with JSM licenses can look at internal comments.
TLDR: how to allow users to use proforma user picker from the customer portal and search for any user that has a Jira Account (might not have license)?
Hi @koh 👋
At this point I don't believe it's possible to allow use ProForma user pickers to show all Jira accounts. I do understand the complication using the conditional sections brings up. I wish I could solve that for you. I will share this post with the product team -- it's good feedback and nice to see these different use cases.