We recently ran into the issue of descriptions not being transferred to the Jira ticket when creating one from sentry. This was caused by the fact that we have custom field configurations for our different issue types which sets a new id for the description field (so not the standard 10001 of the default field configurations).
Solution Brainstorm
Unlike with custom fields, the description is a standard field and should be referable to by name in the API call. If this is correct, it would simply be a matter of using the field name instead of the ID in the request body.
Problem Statement
We recently ran into the issue of descriptions not being transferred to the Jira ticket when creating one from sentry. This was caused by the fact that we have custom field configurations for our different issue types which sets a new id for the description field (so not the standard 10001 of the default field configurations).
Solution Brainstorm
Unlike with custom fields, the description is a standard field and should be referable to by name in the API call. If this is correct, it would simply be a matter of using the field name instead of the ID in the request body.