Hi folks, I hope everyone is well.
Further to https://community.atlassian.com/t5/Jira-questions/Add-Organization-to-Security-Level/qaq-p/888928, I'd like to know if it is possible to assign Security Levels to Portal-Only customers (or failing that, Organizations).
Context:
We have a client ("Client X") where several people have Portal-Only accounts and are generating tickets through the portal. These Portal-Only customers are grouped into an Organization ("X-Org" - pardon the pun) so they can view each other's tickets.
We would like to set up their Business Manager ("BMX" - lol) on Jira proper so she can go through tickets and shift their Priorities, as changing Priorities isn't possible from the portal without setting up convoluted transitions and making the portal ticket view unnecessarily complicated...
In order to prevent BMX viewing tickets from our other clients, we need to set all of the client's existing tickets to a security level (i.e. "Sec-ClientX") as well as any new tickets generated from the Client X's other staff.
Unfortunately our testing of this has hit a bottleneck whereby Client X's portal-using staff are unable to see any new tickets they raise, as well as their previously submitted tickets or other tickets in X-Org, because the Security Level is being automatically assigned and therefore preventing any visibility of the tickets or any subsequent updates we provide to them.
I'd like to know if it is at all possible to allow Client X's portal-only customers to view tickets with the Sec-ClientX security level, either by assigning the P-O customer accounts to it or by assigning X-Org to it (and therefore all the P-O customers in the Organization).
Sorry if any of this is unclear, and thanks very much in advance for taking the time to read and consider the issue.
All the best
Joshua
Playing with with the User Management console a bit, I have found a successful workaround whereby I add Portal-Only users to a group with the necessary Security Level access without the need to pay for a license for them. The only thing they'll need to do is set up an Atlassian account.
1) Select Jira Service Desk from the User Management section of the Administration menu.
2) Search / locate the Portal-Only customer you want to assign a security level to / add to a group.
3) Select Migrate to Atlassian Account from the ••• menu on the user's customer's row - this will take a few seconds and send an invitation email to the user's email address.
4) The customer must now set up their Atlassian account, which will be immediately added to your Jira. If the customer already has an account, it will simply be added to your Jira.
5) Now select Users from the Administration menu and click on the same customer.
6) There should be buttons discerning whether the account can access the site as well as what products the account has access to. Disable everything other than "Has access on site".
7) The step above should remove the user from any groups they had been added to - if this is not the case, hit Remove user from group from each group's ••• menu in the Groups section.
8) Finally select Add to group and select the group(s) with the security level you want to assign the customer!
Step 6 ensures that you will not need to pay for any additional licenses for Portal-Only customers you wish to add to a security group. After completing all steps, the customer will experience Jira like a Portal-Only customer, but will be able to see issues in their Requests menu that have the corresponding Security Level.
I hope this helps somebody else.
All the best.
Addendum:
If the customer you want to add isn't already a Portal-Only customer, you can simply use the Invite users button in User Management > Users to invite the customers, making sure to deselect all of the options in Product access and specify the group(s) you want to add them to under Group membership.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.