Extra Fields for Jira Service Management

Known Issues and Possible Solutions

1. AJAX Error 400

This error can occur if the request type linked to the request no longer exists in the Jira Service Management project. This may happen if the request type was renamed, deleted, or replaced.

Screenshot 2025-08-11 at 2.17.09 PM.png

How to Confirm:

  1. Open the affected request in the Jira Service Management portal.

  2. Check the Request type field:

    1. If it appears empty, the linked request type no longer exists.

  3. In the affected Jira Service Management project, go to:
    Project settingsRequest managementRequest types.

  4. Look for the missing request type in the list.

    1. If it’s not listed, this confirms the cause of the error

Possible Workaround:
Edit the affected request from the JSM board and change its request type to an existing request type in the project. After this, the request should work as expected.

Screenshot 2025-08-11 at 2.41.58 PM.png


2. Some attachments are not displayed in customer portal

If you create a ticket internally (not from customer portal) and share with customer, attachments might not be displayed to customer. This is caused by Jira permission issue.

As an alternative option, you can create a ticket from customer portal on behalf of customer instead of creating a ticket internally and sharing it with them.

JSM-create-on-behalf-of-customer.png

Attachments added here will be visible to the customer and any other customers whom the ticket is shared afterward.