I need to be able to restrict the approvals field in the portal to only show authorized people who can approve tickets.
Currently a user could raise a ticket and select anyone for authorization rather than their line manager.
I can see how to filter the list when it's hidden but this doesn't help as we have regional managers who look after their areas.
@James Godbold - I have setup the approvals as you have specified creating a Project Role and then assigning users to that role.
My problem is stemming from the approvers list not creating a drop down user selection in the Customer Portal. Also I was hoping the user picker would provide a preset list of users rather than an email only search confirmation. Is there a better way to do this now?
I am hoping to have a preset dropdown list of managers w/ name and email so the portal only user can select which one to submit the approval to.
One problem with this scheme is that it appears the built-in notification for approval will only send notification to people in the Approvers field. We tried exactly what you have with a project and found that the approver was not receiving an approval email. Opened a case with Atlassian and the rep said "The only supported notification for Approvers is using the supplied Approvers field."
Using this knowledge I tried to switch back to the multi-user-picker Approvers field, but realized you cannot set a filter on that. Instead, I'm going to keep my single user approvers field and copy the value in it to the hidden Approvers field in a post function. Not certain that will work to trigger the notification, but I'll report back if it does.
@Bruce Reed - We have not run into any issues when using the "single user picker" configured for "user filtering" + a Project Role (this bit was in the comments). All licensed, unlicensed, and portal only approvers receive their email notifications when they are selected both from our Portal Submission form and from within the Jira program.
I do not know when you spoke to Atlassian but the response sounds like an "out of demarcation" line customer service agents are trained to use when the problem doesnt fit into a tidy documented box.
** NOTE ** Atlassian does not have a method of using your "filtered" list of approvers to populate as a drop down to your users.
-- If you have issues with the "single user picker" not working correctly for portal only accounts check the following setting: Project > Settings > Customer Permissions > Who can customers share requests with?
The "Any customer or organization, by searching this project. choose this option to allow customers to search their organization for approvers" must be selected. If it is not the user picker for portal only accounts will require the exact email address for the user to be entered with out any auto complete or confirmation that the address is correct.
Agree, and to date Atlassian has still not been able to figure out what's going on. We seem to be in circular information gathering mode, which will of course lead to nowhere. Doesn't seem to matter whether "Approvers" or our custom field is used -- it never sends notification.
I worked it out myself.
Tested and works as expected
Do not use Groups as 'Portal Only' Users are not allowed to be added to Group.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs