Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-5768

Total number of requests is not taking into an account Issue Security level

      Summary

      On the Customer Portal, total number of My requests on the right corner doesn't take into an account Issue Security level. In other words, it's showing invalid number which contains the tickets that the user doesn't have the access.

      Steps to reproduce

      1. Create JSD project, create issue security schema (for example. not allow to see ticket if you are not agent)
      2. Create Organisation and put Customers and agent to it
      3. Lets say there are right now 5 open tickets by customer
      4. Create ticket1, share with the Organisation
      5. Apply Security level created before

      Expected results

      "My requests" contains number of tickets which customer can see and doesn't include those tickets hidden behind security level.
      So, total number is 5

      Actual results

      User can see total number of tickets including those which he has no access to see
      Total number is 6

          Form Name

            [JSDCLOUD-5768] Total number of requests is not taking into an account Issue Security level

            Dylan added a comment -

            Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage.

            Cheers,

            Dylan - Service Enablement @ Atlassian

            Dylan added a comment - Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage. Cheers, Dylan - Service Enablement @ Atlassian

            sraj2@atlassian.com: this bug has been labelled as "no-cvss-required", what does that mean in practice in terms of security classification?

            Federico (Inactive) added a comment - sraj2@atlassian.com : this bug has been labelled as "no-cvss-required", what does that mean in practice in terms of security classification?

              Unassigned Unassigned
              aromanenko ari (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: