Enable project level access vs. org level for Jira integration

[nadecancode]

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

1. Use version 24.10.0
2. Use JIRA integration (Legacy)
3. Try to create a JIRA issue from an existing Sentry issue
4. Observe behavior for multi-select fields

Expected Result

Able to select freely with multi-select fields (e.g. Component/s, Fix version/s)

Actual Result

Frontend doesn't respond properly, when you click anything in the dropdown it resets your focus to the first item in dropdown. However, the states are properly updated (as in if you click something else in dropdown, and submit the form, it'll send right data to the backend).

Product Area

Other

Link

No response

DSN

No response

Version

24.10.0

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[bc-sentry]

Could you please try to reproduce this with the non-legacy Jira integration? Thank you.

[nadecancode]

Could you please try to reproduce this with the non-legacy Jira integration? Thank you.

Sorry we cannot use non-legacy Jira integration. This poses too much security risk to the corporate to allow an org-level Jira integration rather than project level integration.

[bc-sentry]

Understood. Tested on hosted Sentry and it worked properly. Transfering to integrations for further triage.

[getsantry]

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

[getsantry]

Assigning to @getsentry/support for routing ⏲️