Sentry to Jira when the project has required custom fields
A common failure when connecting Sentry to Jira: the Jira project has a required custom field (team, component, severity, customer), and ticket creation from Sentry fails or needs a person to fill it in. This guide covers why it happens and your options.
Disclosure: Integration Yard makes Autoticket, one of the options below. Autoticket is pending Atlassian Marketplace approval as of October 22, 2026.
Why it happens
Jira rejects a create request that leaves a required field empty. Sentry's Jira integration docs state that custom required fields are not supported, so automatic ticket rules can't fill them. Manual creation from Sentry asks a person to complete the form instead.
Your options
- Make the field optional for the issue type Sentry uses, or give it a default value in the Jira field configuration. Simplest, if your Jira admins agree.
- Use a separate issue type (for example "Error") whose screen doesn't require the field.
- Fill the field after creation with a Jira Automation rule triggered on issue created (only works if the field isn't required at create time).
- Create tickets from Sentry webhooks yourself (a small service or no-code tool calling the Jira REST API with the field set).
- Autoticket: map each required field to a fixed value or a Sentry token, for example
customfield_10051={{environment}}. Tokens include title, environment, release, level, project and count. Select fields take JSON such as{"value":"{{environment}}"}.
Which to choose
If you can change the Jira configuration, options 1–2 cost nothing and need no extra software. Choose an app or your own webhook service when the field must stay required and needs a different value per ticket. See the Autoticket setup guide for the exact mapping format.
Sentry is a trademark of Functional Software, Inc. Jira and Atlassian are trademarks of Atlassian. Integration Yard is not affiliated with or endorsed by either company.