Issue Summary

• When the T-shirt size is syncing successfully from Jira Align (JA) to Jira with the default values like XXL/XL.
• If there are some additional texts added with the T-shirt size, which contain special characters like ~ (for eg., Medium - ( ~1 iteration))
• These values result in an error "400 Bad response" upon syncing from JA to Jira, whereas when the same is synced from Jira to JA, no errors are shown, but the values aren't synced either.
• Refer the below scenarios:

Scenario 1

The sync fails if the options contain special characters configured.

Modified in JA:

By Sivashanmathi A on 17/07/2025 18:08:59
Feature Updated -
Team Weeks Changed - From [26] To [6]
T-Shirt Changed - From [XL] To [Medium - (Up to 24 sp / ~1 iteration)]
Points Changed - From [16] To [4]

Error syncing this to Jira field:

By External System on 17/07/2025 18:10:54
SV-22: Failed to update JiraID : 20819 - Response: 400 BadRequest Json: {"errorMessages":[],"errors":{"customfield_10653":"Specify a valid value for Siva_Tshirt"}}

Scenario 2

The sync succeeds with the special characters (both () and /) and when ~ is removed.

Modified in Jira directly:

Sivashanmathi A updated the Siva_Tshirt
July 17, 2025 at 6:54 PM
XXL -> Large - (Up to 48 sp / 2 iterations)

Successfully synced from Jira to JA field:

By External System on 17/07/2025 19:00:49
Updated -
Points Changed - From [48] To [10]
T-Shirt Changed - From [XXL] To [Large - (Up to 48 sp / 2 iterations)]
TW/MW Changed - From [80] To [16]

Steps to Reproduce

1. Navigate to Settings > Platform > Portfolio > Estimate conversations > Feature > Modify or Add any T-shirt size with the special character ~
2. Update the same in the Jira custom field for T-shirt size as well. 
3. Navigate to the Jira Settings > Jira Setup > T-shirt custom field > Configure >  Modify the Jira Value (JA value is updated automatically) and ensure this is the Bidirectional sync.
4. Now sync the Feature with the T-shirt size containing the special character ~

Expected Results

T-shirt size to be synced bidirectionally.

Actual Results

The error below is shown in the Feature audit logs for the Jira cloud instance.

Response: 400 BadRequest Json: {"errorMessages":[],"errors":{"customfield_xxxx":"Specify a valid value for Siva_Tshirt"  

The error below is shown in the Feature audit logs for the Jira server instance.

Response: 400 BadRequest Json: {"errorMessages":[],"errors":{"customfield_xxxx":"Option id 'null' is not valid"  

Workaround

Currently, the workaround is to avoid the ~ symbol in T-shirt Estimation values.