Issue Summary

When attempting to update the Customer request type system field, if the name includes an extra space at the end, the update fails to execute from the automation rule. Although the automation rule correctly sends the value with the additional space, on the JSM side, it appears to be trimming the space, resulting in a mismatch of values. Consequently, it is unable to update the Customer request type field, generating the error below:

Invalid customer request value 

Steps to Reproduce

• Install JSM 
• Navigate to Project Settings --> Request Type --> Edit the request type name and add an additional space at the end.
• Create a sample automation rule and attempt to update the customer Request type field by adding an additional space at the end from the Advanced Field option.

• Example:

• {
     "fields":{
        "Customer Request Type": "IT help "
     }
    }  

  

• Even though the hardcoded value we are providing contains additional space at the end, the automation rule is sending the value with the extra space. However, on the JSM side, it still fails to update the value, resulting in the following error:

• Invalid customer request value   

Expected Results

The value provided by the automation rule has extra space, so it should update the Customer request type field.

Actual Results

The value provided by the automation rule has extra space, but it is failing to update the Customer request type field, throwing the following error:

Invalid customer request value 

Workaround

• We can use the request type key (guid) value instead of the request type name. For more details, refer to this KB article: How to clone an issue and update the customer request type using Automation for Jira