JSM webhook payloads presenting project permission errors in some fields when triggered by customers

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • 1
    • Hide

      Issue Summary

      When a user that only customer permissions in JSM interacts with an issue, webhooks for that interaction display errors such as the one below in the JSM fields, such as request types and SLAs:

      customfield_10225=
          {errorMessage=You don't have permission to access this service project.,
          i18nErrorMessage=
              {i18nKey=sd.agent.servicedesk.error.project.nopermission, parameters=[]}
          }
      

      Steps to Reproduce

      1. Set up a JSM 10.3
      2. Create a JSM project
      3. Add a user that's just a customer, with no other permissions
      4. (optional) Create an automation rule just to receive the webhook and print it in the audit logs (using the {{webhookData}} smart value)
      5. Create a native Jira webhook
      6. Create/update issues with that user
      7. Check the webhook data

      Expected Results

      All data is presented in the webhook.

      Actual Results

      JSM fields are presented like this:

      customfield_10225=
          {errorMessage=You don't have permission to access this service project.,
          i18nErrorMessage=
              {i18nKey=sd.agent.servicedesk.error.project.nopermission, parameters=[]}
          }
      

      Workaround

      Currently there is no known workaround for this behavior.

      An automation can be created to copy the field value to a regular custom field, so it is sent over the webhook.

      Show
      Issue Summary When a user that only customer permissions in JSM interacts with an issue, webhooks for that interaction display errors such as the one below in the JSM fields, such as request types and SLAs: customfield_10225= {errorMessage=You don't have permission to access this service project., i18nErrorMessage= {i18nKey=sd.agent.servicedesk.error.project.nopermission, parameters=[]} } Steps to Reproduce Set up a JSM 10.3 Create a JSM project Add a user that's just a customer, with no other permissions (optional) Create an automation rule just to receive the webhook and print it in the audit logs (using the {{ webhookData }} smart value) Create a native Jira webhook Create/update issues with that user Check the webhook data Expected Results All data is presented in the webhook. Actual Results JSM fields are presented like this: customfield_10225= {errorMessage=You don't have permission to access this service project., i18nErrorMessage= {i18nKey=sd.agent.servicedesk.error.project.nopermission, parameters=[]} } Workaround Currently there is no known workaround for this behavior. An automation can be created to copy the field value to a regular custom field, so it is sent over the webhook.

      Issue Summary

      When a user that only customer permissions in JSM interacts with an issue, webhooks for that interaction display errors such as the one below in the JSM fields, such as request types and SLAs:

      customfield_10225=
          {errorMessage=You don't have permission to access this service project.,
          i18nErrorMessage=
              {i18nKey=sd.agent.servicedesk.error.project.nopermission, parameters=[]}
          }
      

      Steps to Reproduce

      1. Set up a JSM 10.3
      2. Create a JSM project
      3. Add a user that's just a customer, with no other permissions
      4. (optional) Create an automation rule just to receive the webhook and print it in the audit logs (using the {{webhookData}} smart value)
      5. Create a native Jira webhook
      6. Create/update issues with that user
      7. Check the webhook data

      Expected Results

      All data is presented in the webhook.

      Actual Results

      JSM fields are presented like this:

      customfield_10225=
          {errorMessage=You don't have permission to access this service project.,
          i18nErrorMessage=
              {i18nKey=sd.agent.servicedesk.error.project.nopermission, parameters=[]}
          }
      

      Workaround

      Currently there is no known workaround for this behavior.

      An automation can be created to copy the field value to a regular custom field, so it is sent over the webhook.

              Assignee:
              Benjamin Woodforde
              Reporter:
              Allan Gandelman
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: