• Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Knowledge Base
    • None
    • 1
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Issue Summary

      If a customer searches for an issue in JIRA Service Desk Customer portal and logs in for the first time, they are directed to Confluence and from here, the Customer can access any pages even those that they should not have access to.

      Steps to Reproduce
      1. Go to your customer portal as a newly created customer.
      2. Perform a search and Select one of the suggested pages.
      3. Due to this being the first login, JIRA would direct the user to the customer portal.
      4. While at confluence, if a page is not restricted, it would be visible even if the user should not have been able to view the page originally (if it was restricted with a label).
      5. Also other spaces may be accessible if the link for them appear in any tickets in the page the customer is accessing.
      Feature Request

      Can JIRA Service Desk handle all the authentication without requiring the redirection to Confluence or can it automatically redirect the user back to itself following a login to prevent the user from accessing Confluence proper.

      Workaround

      Confluence page restriction can be used to restrict the pages from the user, however, this may not necessarily be scalable depending on how many pages are involved at the point the confluence was connected to JIRA Service Desk to serve as a knowledge base.

          Form Name

            [JSDSERVER-5324] Other Spaces and Pages Accessible From Knowledge Base article

            Alex Cooksey made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Atlassian Update – 27 Jan 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            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.

            Regards,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 27 Jan 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . 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 . Regards, Jira Service Management, Server & Data Center
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012549 ] New: JAC Suggestion Workflow 3 [ 3649853 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2663621 ] New: JAC Suggestion Workflow [ 3012549 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2421384 ] New: Confluence Workflow - Public Facing v4 [ 2663621 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]

            I wonder how come I'm the first one to notice this behavior?

            I believe one Confluence space should be used to it's full capacity: documentation, project management, knowledge base etc. But with this bug the user who accesses the customers portal and uses the search can access all of the documents from the space safe if one restricts each document manually (which is not scalable).

            Other option would be to have 2 Confluence spaces, one for the project management and another for the support, but this makes for the confusion with the spaces naming and complicates things further.

             

            Please fix this bug, because that's what it is, a bug, not a feature request.

            Nemanja Milosavljevic added a comment - I wonder how come I'm the first one to notice this behavior? I believe one Confluence space should be used to it's full capacity: documentation, project management, knowledge base etc. But with this bug the user who accesses the customers portal and uses the search can access all of the documents from the space safe if one restricts each document manually (which is not scalable). Other option would be to have 2 Confluence spaces, one for the project management and another for the support, but this makes for the confusion with the spaces naming and complicates things further.   Please fix this bug, because that's what it is, a bug , not a feature request.
            Ismael Olusula Jimoh (Inactive) created issue -

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: