Sentry 23.3.1 Jira Integration Failing

cah-michel-bitar commented 2 weeks ago

Self-Hosted Version

23.3.1

CPU Architecture

x86_64

Docker Version

20.10.18

Docker Compose Version

1.29.2

Steps to Reproduce

After an upgrade all the way from 21.8.0 where Jira integration was functioning normally to 23.3.1, Jira Cloud integration stopped working.

We tried reconfiguring everything multiple times and the integration was still failing.

Expected Result

We expect to be able to create Jira tickets through Sentry

Actual Result

It is actually failing with the following error:

And the only indicative log I was able to find was the following:

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/sentry/api/base.py", line 188, in handle_exception
    response = super().handle_exception(exc)
  File "/usr/local/lib/python3.8/site-packages/rest_framework/views.py", line 469, in handle_exception
    self.raise_uncaught_exception(exc)
  File "/usr/local/lib/python3.8/site-packages/rest_framework/views.py", line 480, in raise_uncaught_exception
    raise exc
  File "/usr/local/lib/python3.8/site-packages/sentry/api/base.py", line 305, in dispatch
    response = handler(request, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/sentry/api/endpoints/group_integration_details.py", line 116, in get
    config = installation.get_create_issue_config(
  File "/usr/local/lib/python3.8/site-packages/sentry/integrations/jira_server/integration.py", line 721, in get_create_issue_config
    (choice["id"], choice["name"]) for choice in issue_type_choices["values"]
KeyError: 'values'

And actually, if I am quick enough to click on the "Link" tab that opens up before the error comes up, I am able to Link issues. Just not to create them. After taking a look at the code, it seems like sentry tries to get a list of issue types from Jira, but it seems like it is being returned as null/empty.

azaslavsky commented 1 week ago

Is there any reason you are not upgrading all the way to the latest release? The one you upgraded to is over a year old, and the offending line of code has already been removed, so upgrading further could resolve the issue.

cah-michel-bitar commented 1 week ago

@azaslavsky The upgrade is quite complicated in our setup and not really straightforward. It could take us some time. Are you confirming however that this is indeed an issue within the code that cannot be fixed without an upgrade?

hubertdeng123 commented 1 week ago

This may be an issue that has been ongoing actually. I'm going to transfer this over to sentry and see what they have to say

https://github.com/getsentry/self-hosted/issues/2153

getsantry[bot] commented 1 week ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 1 week ago

Routing to @getsentry/product-owners-settings-integrations for triage ⏲️

getsentry / sentry