Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1402

Added participants cannot access Issues to which they have been added

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      According the SD2.2.0 Release Notes customers can be added as participants to Issues to allow them to access said Issue. After upgrading, I am able to add participants as a normal Jira User/SD Agent, however, the user added cannot access the ticket. The issue does not appear in the "My Requests" screen for the added participant, the added participant cannot search on them, and it the URL is used a permission error is returned.

      I am not sure which OD release of the 2.2 is installed.

            [JSDSERVER-1402] Added participants cannot access Issues to which they have been added

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2305204 ] New: JAC Bug Workflow v3 [ 3126003 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]

            I don't have any issue level security set up. And yet even despite this my requested participants don't have access to the ticket.

             

            Not sure how to get around this.

             

             

            Patrick Dufresne added a comment - I don't have any issue level security set up. And yet even despite this my requested participants don't have access to the ticket.   Not sure how to get around this.    
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2059144 ] New: JSD Bug Workflow v5 - TEMP [ 2305204 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056547 ] New: JSD Bug Workflow v5 [ 2059144 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956149 ] New: JSD Bug Workflow v5 - TEMP [ 2056547 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1615014 ] New: JSD Bug Workflow v5 [ 1956149 ]
            jonah (Inactive) made changes -
            Description Original: According the [SD2.2.0 Release Notes|https://confluence.atlassian.com/display/SERVICEDESK/JIRA+Service+Desk+2.2+Release+Notes] customers can be added as participants to Issues to allow them to access said Issue. After upgrading, I am able to add participants as a normal Jira User/SD Agent, however, the user added cannot access the ticket. The issue does not appear in the "My Requests" screen for the added participant, the added participant cannot search on them, and it the URL is used a permission error is returned.

            I am not sure which OD release of the 2.2 is installed.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1402].
              {panel}

            According the [SD2.2.0 Release Notes|https://confluence.atlassian.com/display/SERVICEDESK/JIRA+Service+Desk+2.2+Release+Notes] customers can be added as participants to Issues to allow them to access said Issue. After upgrading, I am able to add participants as a normal Jira User/SD Agent, however, the user added cannot access the ticket. The issue does not appear in the "My Requests" screen for the added participant, the added participant cannot search on them, and it the URL is used a permission error is returned.

            I am not sure which OD release of the 2.2 is installed.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-1402 [ JSDCLOUD-1402 ]
            Michelle Chin made changes -
            Comment [ A comment with security level 'atlassian-staff' was removed. ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-cloud New: affects-cloud affects-server

              Unassigned Unassigned
              a4899c7f4141 Ben Bowen
              Affected customers:
              0 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: