-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
As per https://jira.atlassian.com/browse/JSD-62 feature, the Customers now are able to go directly to Customer Portal on login. However, they are still given the ability to navigate back to JIRA, even though they cannot do anything. But it will be much more elegant if the customers were only directed to Customer Portal without the ability to navigate back.
Currently, the workaround for this is as per this comment, whereby you have to include the following script in Announcement Banner of the instance, which will direct the users back to Customer Portal anytime they try to navigate to JIRA:
<script type='text/javascript'> function pageFormatNotLoggedInOrNoProjectAccess() { //All Pages AJS.$("#home_link").parent().hide(); //Hide Dashboards Menu AJS.$("#quicksearch").hide(); //Hide Search Box AJS.$("#system-help-menu").hide(); //Hide Help Menu //Agile Menu if (AJS.$("#greenhopper_menu").length) { AJS.$("#greenhopper_menu").parent().hide(); //Hide Agile menu } if (AJS.$("#greenhopper_menu_no_project").length) { AJS.$("#greenhopper_menu_no_project").parent().hide(); //Hide Agile menu } } function pageFormatNoProjectAccess() { //All Pages AJS.$("#view_profile").parent().parent().parent().hide(); //Hide Profile Menu Item AJS.$("#set_my_jira_home").parent().hide(); //Hide Profile Jira Home Menu AJS.$("#upm-requests-link").parent().hide(); //Hide Profile Marketplace Link //Dashboard if (window.location.href.indexOf("/secure/Dashboard.jspa") != -1 || window.location.href.indexOf("/secure/MyJiraHome.jspa") != -1) { AJS.$("#dashboard").hide(); //Hide Entire Dashboard Screen } } AJS.$(document).ready(function() { //All Pages AJS.$("#announcement-banner").css("padding", "0px"); //Remove Padding From Announcement Banner //Check Login & Service Desk Only User Status if (AJS.$("#header-details-user-fullname").length == 0) { //Format Page pageFormatNotLoggedInOrNoProjectAccess(); //Redirect To Login Page if (window.location.href.indexOf("/secure/Dashboard.jspa") != -1) { window.location = "/login.jsp"; } } else { if (AJS.$("#browse_link").length == 0) { //Format Page pageFormatNotLoggedInOrNoProjectAccess(); pageFormatNoProjectAccess(); //Redirect To Service Desk if (window.location.href.indexOf("/servicedesk/customer/<your service desk project key>") == -1) { window.location = "/servicedesk/customer/<your service desk project key>"; } } } }); </script>
Note: this workaround isn't available for the OnDemand platform.
- is duplicated by
-
JSDSERVER-512 Using the default Service Desk Permissions doesn't direct customers to Service Desk
-
- Closed
-
- relates to
-
- Closed
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-547] Customers to be directed to only Customer Portal without the ability to navigate back to JIRA
There are several use cases, JIRA should be smart enough to silently redirect a user that doesn't have access to normal JIRA interface to the customer portal.
As an user I am really pissed of of clicking the ticket ID from email notifications from support.atlassian.com, just to get a page telling me that I do not have access to that view.
In fact I do think that the decision of viewing simple-view or normal-view should be based on user profile/cookie, both should have the same URL, displaying one view or another based on permission and/or preference.
Feature like this should be well designed in order to provide the best user experience.
They can just go to the JIRA URL, what does happen as some of our customers had access to our JIRA before we implemented Service Desk.
How do customers navigate from the Customer Portal to JIRA?
Is there a link to JIRA in the Customer Portal or do you mean that they can just go to the base URL / JIRA URL?
Actually, the problem is that users that only need access to the Customer Portal, still need to be in the jira-users group and therefore can login to the main JIRA interface, although they cannot do anything there. That is where the script comes in and redirects the users to the Customer Portal.
The elegant solution in my view would be that you put the Customer Portal users in a specific group (not jira-users), which prevents them from logging in to the main JIRA interface.
This has not been resolved. The comment from 18-Sep-2014, above, describes the problem well.
User complained about this to me today.