Experienced Behavior:

      Trouble is experienced when an agent or customer shares a link with a user who has permission to view the issue in JIRA but is not an agent and is not listed as a customer or request participant on that issue.

      • As a customer, I encounter trouble sharing the link when I am viewing an issue through the customer portal.
        • Example link: BASEURL/servicedesk/customer/portal/1/DESK-1
      • As an agent, I also encounter trouble when sharing the link when I am viewing an issue through the customer portal.
      • As an agent, I encounter trouble share the link when I am viewing an issue from the queues screen.
        • Example link: BASEURL/projects/DESK/queues/1/DESK-1

      In both cases the user receiving the link is unable to access the request using the link. This user is able to access the request using BASEURL/browse/DESK-1

      Message seen when visiting portal URL

      Message seen when visiting queues URL

      Expected behavior:

      The ability to provide another user with the link that is shown in my browser's address bar and for that user to be able to access the request using that link, provided they have permission to access the request.

      Suggested Resolution

      Automatically redirect the user so that they are able to view the request.

          Form Name

            [JSDSERVER-3426] Agents and customers experience problems when sharing links

            Atlassian Update - 03 March 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.

            Kind regards,
            Jira Service Management Data Center

            Ishwinder Kaur added a comment - Atlassian Update - 03 March 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact. We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Jira Service Management Data Center

              Unassigned Unassigned
              tevans Tim Evans (Inactive)
              Affected customers:
              5 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: