-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
25
-
3
-
NOTE: This bug report is for Jira Service Management Data Center and Server. Using Jira Service Management Cloud? See the corresponding bug report.
Hi everyone,
Thank you for your interest in this issue.
A fix for this was investigated by the Jira Service Management team in 2015, however it was soon realised that different approaches lead to what could be considered a more confusing experience for customers. During subsequent reviews we have repeatedly come to the same conclusion. A permanent fix requires significant work and changes to permission schemes which unfortunately we are not able to commit to at this time. We will continue to monitor this issue to determine demand for a more comprehensive solution.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Kind regards,
Jira Service Management, Data Center & Server
Issue Summary
Jira Service Management Customer cannot view public Jira when logged in to Jira Service Management
Steps to Reproduce
- Create a regular project and some issues in Jira which can be viewed by anonymous users
- Create Service Desk project and create a customer
- Log in to the customer portal with the customer account
- Using the same session, try to access an issue in the project from step #1 by manually entering link in browser
- Customer will not be able to access the issue. Instead, they just get stuck at the customer portal
Expected Results
Logged in Jira Service Management Customer can see the issues in a public Jira when they are logged in to Jira Service Management.
Actual Results
Customer can see the issues in a public Jira when they are not logged in to Jira Service Management. Once they login to Jira Service Management, they can't no longer view the issues in the public Jira. The user keeps getting redirected to the Jira Service Management portal.
Workaround
- Option 1: Make the links to public info inside Jira (Like project issues, filters etc..) built out of an alias of the Jira server (if you don't have an existing alias, create a new alias recognised by DNS). The system doesn't recognise the cookie as the same & gives the same public view for a customer portal user as a non-logged in user. However, the data is the same.
- Option 2: Use Confluence knowledge base integration & create a wiki page to show the dynamic data from Jira in it. Make the links which you want customer portal users to see point to the wiki instead of directly in Jira.
- Option 3: Open link in private / incognito mode
All our customers can have a service desk customer account which they need to ask support. If a customer uses this service desk to e.g. request a feature, we might log this as a feature request in our "public" Jira (a Jira project where anyone can view the issues and see their progress). Typically, the service desk ticket is then closed with a message that a feature request is made (with a link to it) and that we plan to deliver this feature then or then.
An anonymous user can - like expected - view the ticket. If that user then clicks on login, they can login using their service desk customer login, and can still see the ticket and navigate to the public Jira project. However, once the user visits the service desk portal, they cannot return to the public Jira project anymore, as they keep being redirected to the service desk customer portal.
However, we want all users (anonymous and service desk customers) to view and browse our public jira project.
- duplicates
-
JSDSERVER-3263 Service Desk customers are not able to access public issues in JIRA Software projects
- Closed
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
- relates to
-
-
- Long Term Backlog
-
- is cloned by
-
DESK-4150 Failed to load
- links to
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
- was cloned as
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-1367] Service Desk Customer cannot view public JIRA when logged in to JIRA Service Desk
There is an ugly workaround which consists of creating a new DNS alias, and use it for links that are shared with a customer. Result: cookie generated by the browser is different, so the customer is not logged when using this link, so he can see the "normal" public ticket in Jira.
Test Apps
added a comment - There is an ugly workaround which consists of creating a new DNS alias, and use it for links that are shared with a customer. Result: cookie generated by the browser is different, so the customer is not logged when using this link, so he can see the "normal" public ticket in Jira.
Test Apps
added a comment - There is an ugly workaround which consists of creating a new DNS alias, and use it for links that are shared with a customer. Result: cookie generated by the browser is different, so the customer is not logged when using this link, so he can see the "normal" public ticket in Jira. Hey Atlassian,
I agree it's a rare case where you have exactly this situation but it's even more annoying in this specific cases. We have another customer with the same issue and currently the only solution seems to be s split of Jira Service Desk and Jira Software in two different instances or can you at least propose in the meantime a "better" work around?
Regards,
Reto
Hi Guys
Our customers have begun seeing this issue, have there been any thoughts around how we could get around this?
Thank you
Agreed with Daniel, this bug shouldn't have priority as Low. It's funny that Cloud issue JSDCLOUD-1367 has priority Medium and this is a Low.
Atlassian please provide a better attention to this issue.
3 years and no solution... what a shame.
But I know, there are other bugs unresolved and open since more then a decade. This is the reason why we pay thousand of dollars every year...
I diagree with Prio "Low". Usability is broken.
@vsharma@atlassian.com after several years of inactivity, the assignee has now changed to unassigned - an action you performed. Does this mean it is now going to get attention? Is the current component/s "API and Integrations" an accurate component for this issue?
I'm just looking to make sure this issue is categorised correctly so it's on the Atlassian radar.
We are going to move away from the Jira Service Desk and look at other solutions. It's simply too constrained and Atlassian are not responsive enough to customer feedback (this issues been opened since 2015).
I don't understand how a company with the resources Atlassian would have - can say with a straight face to an audience (of which a significant number of which would be software developers) that this is too hard for you to do... and to take several years to come to this disappointing conclusion.
The unresponsive support is one the the reasons we stopped paying for and upgrading our Jira ServiceDesk.