2. Enable development mode in your Jira instance underGear Icon > Manage Apps > Settings
3. Upload the Atlassian connect descriptor to Jira. It can be found at:
https://[your-domain]/extensions/jira/descriptor/ or in Sentry’s case: https://sentry.io/extensions/jira/descriptor/
Once you get here, you’ll need to add your Atlassian connector descriptor into this field from a public domain. Jira will turn that into a JSON file that Jira will use to install the integration.
Went through this install procedure, and it installs fine. But when I try to link/create a jira issue it doesn’t seem to be able to search for the Reporter field nor the Assignee field. The projects field, however, is populated with lots of projects, so that part works. Without Reporter it’s impossible to complete the form, so this integration is not working.
Version 9.1.1 Sentry on premise and Jira Cloud.
I’ve tried this method after I tried the marketplace plugin. But the installation process fails with the error message “The app “sentry.io.jira” could not be installed as a local app as it has previously been installed from Atlassian Marketplace”
Hi, following your instructions above. When I try to click the configure button in jira cloud, the process freezes at this step “App is not responding. Wait or cancel?” Maybe I misconfigured something? please any help will be sentry sentry version 9.1.1.
Worked fine for us. Make sure you’re using the connect descriptor from your domain (NOT the link to Sentry’s!) and that you can successfully resolve that on the public internet.
Hello, this workaround works fine, but i have one problem. I cannot get any users from our JIRA (fields Reporter, Tester, Assigne). I have checked our Privacy policy and e-mails are set with public visibitlity. When i have tried call API endpoint with list of users from browser, everything was fine. Can you help with this problem?
after more than a year of dodging this bug by sentry support I can only confirm same issue occurs in latter version than yours. I got 10.1.0.dev 0b7df514 and facing the very same problem.
I have uploaded the app, using the descriptor for our hosted Sentry, but when I click configure it goes to a blank screen with a spinner, and times-out after 30 seconds or so.
Are the pre-requisites for these instructions that I missed? e.g. API keys etc.
Hello there!
I found a decision for this bug and finished setup process.
The problem is that Jira Cloud couldn’t open configure process in iframe (don’t know the real reason for this) But, after you followed the above instructions, you have allow Jira access to your Sentry organisation.
I solved this following these steps:
0. Installed custom Jira Application and clicked Get Stared or Configure (both of them are ok) at Manage Apps screen in Jira.
When I saw loader, I’ve opened browser console and found an error which starts with
Invalid ‘X-Frame-Options’ header encountered when loading …
I copied and pasted URL for this request and opened that in another tab in browser. You will see something like accept dialogue window. Mark the organisation you need to link and Save Settings
After all, if you go to Integrations settings in your Sentry, you will see, that set up finished successfully. That’s all.
After turning off uBlock Origin for this domain and following @alewkinr’s instructions I got Jira integration in Sentry (Settings > Integrations) that I was able to configure.
However, when trying to create a new Jira issue from Sentry (using Link Jira Issue) Sentry is unable to read Jira users (Reporter and Assignee field).
Even though Reporter is marked as a mandatory field I can create the Jira issue without it and the ticket says Reporter is Sentry.
Hi @summerkiflain, no, never managed to solve the issue, so we just tolerated the fact that every new Jira ticket created from Sentry has Sentry as its author.
@mbonaci Sorry to bother you again, but can you tell me sentry version you guys are using?
I using using 9.1.2 and I am thinking maybe upgrading version of on-premise sentry might resolve the issue, because the ajax calls that goes to Jira for fetching reporters & assignee responds with 400 bad request.
