Option 2: Use Confluence knowledge base integration & create a wiki page to show the dynamic data from Jira in it.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. 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 user keeps getting redirected to the Jira Service Management portal. Once they login to Jira Service Management, they can't no longer view the issues in the public Jira. Actual ResultsĬustomer can see the issues in a public Jira when they are not logged in to Jira Service Management. Logged in Jira Service Management Customer can see the issues in a public Jira when they are logged in to Jira Service Management. Instead, they just get stuck at the customer portal Customer will not be able to access the issue.Using the same session, try to access an issue in the project from step #1 by manually entering link in browser.Log in to the customer portal with the customer account.Create Service Desk project and create a customer.Create a regular project and some issues in Jira which can be viewed by anonymous users.Jira Service Management Customer cannot view public Jira when logged in to Jira Service Management Steps to Reproduce The customers (both portal-only customers and the ones having Atlassian account) can see the issues in the public Jira projects when they are not logged in to. Jira Service Management, Data Center & Server Issue Summary 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. We will continue to monitor this issue to determine demand for a more comprehensive solution.
A permanent fix requires significant work and changes to permission schemes which unfortunately we are not able to commit to at this time. During subsequent reviews we have repeatedly come to the same conclusion. Thank you for your interest in this issue.Ī 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.
0 kommentar(er)
