Status: Closed (View Workflow)
Severity 3 - Minor
When setting up custom team field mapping between Jira and Jira Align, spaces are allowed in the Custom Field ID value which can lead to connector sync failures for both Stories and parent Features.
Steps to Reproduce
- Configure custom team field mapping per article but leave a space in the custom field value:
- In Jira, create a Story and assign to Jira Epic and allow both to sync to Jira Align
- In Jira Align, assign the Story to a team and allow to sync
- Sync will fail with "Unexpected character while parsing path" reported in both Audit Logs and Jira Change Log > Issues
Not allow spaces in custom field ID values either by trimming spaces automatically or throwing error during Save.
Custom field ID values can be entered with a space without warning which leads to sync failures that are difficult to identify.
Currently there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
- relates to