We would like to avoid this mail verification process in case we already know them.
The reasoning behind is we use 'Usersnap' integration and our users never interact directly with JIRA.
But in order to get the proper 'Reporter' details in the JIRA case we need their mail in the customer list.
Assigning a rule would required them to be JIRA users.
The sole reason for existence of those 'users' in the 'customer list' is (would be) to get the 'Reporter' field properly set with their mail, so that when responding in JIRA Service Desk they get automatically notified directly via their mail (which is the whole purpose of 'Service Desk').
Yes, I suppose I missed that bit – Does this knowledgebase article help instead?
You can add customers without inviting them via email but you'll need to predefine their password and ask them to change it later once they login. Here is how you do that:
- Login to the JIRA application as an administrator
- Go to > User management
- Create User - here make sure to uncheck the "send an invitation" which will prompt you to enter a password that will be the users new password to login. Additionally make sure to uncheck "JIRA " and/or "Confluence" application access. Keeping those checked would allow that user login to JIRA and Confluence systems, allow them to access things based on default user permissions and consume user license in each system. In this case you are wanting to just create a free customer in Service Desk so uncheck all application access options.
- Click "Create User"
- Go to your Service Desk (from the top menu)
- Go to People tab
- Select Customers in the left nav
- Next to the Invite customers button on the right side of the screen you'll see an option for access settings. You'll want it to say "everyone can access". So if your current selection is "restricted access" click that text and change the selection.
Then simply distribute your Customer Portal link to your customer via website, email, or whatever way you wish to public the URL your customers may use to access the customer portal.
This works fine, thx.
IMHO: In terms of usability this could be handled more convenient in Service Desk 'customer' handling itself.
Now Atlassian only needs to fix the issue that 'Customer Request Type' isn't set by default ... causing notification mails not being sent ... amazing how many open (unsolved) issues there are in JIRA for JIRA
Well let's be honest – Software isn't easy and it isn't simple. Most software companies do not have public bug trackers.
Can I ask, how are you running into situations when you don't have Customer Request Type being set? This happens automatically through the Portal and Email channels.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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