We're trialling the Service Desk and trying to understand how a user would know to access a customer portal rather than the standard JIRA interface.
Looking at the default configuration, if a user navigates to JIRA (e.g. https://jira.example.com) they are presented with the standard "System Dashboard". To get to the Customer Portal, they need to then
This seems to be rather long winded.
The alternative scenario I can see is that the customers are given a link directly to the customer portal e.g. https://jira.example.com/servicedesk/customer/spt
Is there a better way of helping customers (i.e. non-developer and non-administrative users) getting access to the Customer Portal?
Sorry to re-open this issue. We are using Service Desk 1.2.1 (latest) now and set up the permissions so a user is only able to see the service desk. However if a user lands on the default jira login page, on login the user is still taken to the system dashboard (showing nothgin due to permissions).
Did I miss something in the configuration or security? Also, under the profile tab, there is an option to set Service Desk as the defalt screen after login. However, this takes the user to the agent screen and the no permissions warning is show on the screen. Is there a way of allowing the user to go straight to the service desk after login?
The Service Desk teams knows that the discovery of "customer portals" is problematic and we are currently working on ways to give a much more directed experience for customers. The end goal would be that people would get a much more Service Desk customer portal oriented experience. But we are not there yet.
In the mean time your best bet is to give out direct links to the specific service desk links.
At Atlassian we have about 11 internal service desk instances that people use day to day and we use a combination of "short url redirect services" eg go/atlasdesk go/kudos go/payroll go/legal* and a Intranet Confluence page that list all the service desks out there for our different teams.
JIRA Service Desk Architect
* go/legal is my current favourite Service Desk usage in Atlassian. We now route requests to our fledgling legal department though Service Desk and JIRA :)
There is a slightly simpler flow for accessing a customer portal:
Additionally, once a user has raised a request through a customer portal, that request form is added to the user's Recent requests list, which can be accessed from the dropdown attached to the main Create issue button.
I set it up with the "pound" proxy in front and redirect from support.ex.co to jira.ex.co/servicedesk/customer/desk. Ideal would be to keep support.ex.co as the URL but I haven't been able to do that with pound. I'm guessing though, that jira wouldn't like being called with the wrong hostname.
I already use pound to redirect jira, confluence and crowd that are all run from the same server on different ports.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot