Users unable to create tickets through Slack/Teams integrations in JSM Cloud

Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

Summary

Users encounter an error when attempting to raise requests via Teams or Slack. The causes may vary, but this documentation provides common ones.

Customer Role Required

When using the Slack integration, users occasionally receive an error stating, 'You can't raise a request on behalf of this user because they need the customer role on your site managed by your organization admins.' This issue prevents users from creating tickets, and it is unclear which users are affected.

Add the customer role to the user or group

When it comes to product access, it's possible to add a single user or a group to the desired product or role. 

By following the steps below, you can add the group or user to the Customer role.

Centralized user managementOriginal user management

To give one user access to a product:

  1. Go to admin.atlassian.com. Select your organization if you have more than one.

  2. Select Directory > Users.

  3. Select a user.

  4. Select Grant access to view a list of products the user doesn’t have access to.

  5. From the Product Roles dropdown for Jira Service Management, select the Customer role.

  6. Select Grant access.

To give one user product access:

  1. Under the product name, determine the group where you want to add the user. If you aren’t sure, select the group with the Default access group lozenge. In this case, the group is jira-servicemanagement-customers-<yourdomain>.

  2. Select Show group’s details from the dropdown for the group where you want to add the users.

  3. Click Add members, search and select the people you want to add and click Add.

To give users in a group access to a product:

  1. Go to admin.atlassian.com. Select your organization if you have more than one.

  2. Select Products from the header.

  3. For the product you want users to access, select Manage Product.

  4. From the product details page, select Add Groups at the top of the page. Search and select the group you want to add, choose a product role, then select Add.
    This will grant product access to all the users within that group.

To give users in a group product access:

  1. If your group doesn’t exist yet, create a group.

  2. Under the product name, click Add group, search and select the group you want to add, and click Add.


Character limit

An user atteps to create a request, but it fails with the following error:

Something went wrong. We were unable to create a ticket. We've notified the agents for this channel.
Share this error ID with support: a03333bf33f33333bba33d33c33c3333

To identify the correct root cause, it might be necessary to reach out to Atlassian Support via support.atlassian.com, but before that, you can try confirming if the user is not exceeding the character limit of the text fields.

An example of the logs Atlassian Support may find is:

   errorMessage: Your request could not be created. Please check the fields have been correctly filled in. URL (text field) can't exceed 255 characters

In Jira Cloud, some fields have 255 character limit:

  • Text field (read only)

    • A read-only text label. Only possible to create values programmatically. Maximum of 255 characters.

  • User Property Field (<255 characters)

    • Choose multiple users from the user base via a popup picker window.

  • Short text (plain text only)

    • A single line of plain text for short lengths of text (up to 255 characters). 

For Paragraph fields (like the Description and Comment), the limit is 32767 characteres.


Select list custom field having more than 100 options

Similar to the above, when an user tries to create a request, the error "Something went wrong" appears with no further details about the cause.

A possible issue might be a select list custom field having more then 100 options.

A select element may contain up to 100 selections, provided as an array of hashes in the form element's options field, (or an option_groups array).

Request type field configuration changes

This error occurs when a Project Admin make changes in the Request Type, for example, making a field 'Required'. 

A screenshot of a form with three fields. Each field has a right-pointing arrow indicating further details or input options.  The Summary and blurred field are marked as REQUIRED. A blue arrow points to the blurred, required field, suggesting it's the current focus.

Once a change is made, it may take a few seconds to reflect in Slack. In case the user creates a ticket using Emoji at the same time, it will fail since the change might not have reflected yet.


Last modified on Dec 24, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.