self-hosted
self-hosted copied to clipboard
Can not create Jira Server Issue in issue details page of Sentry.
Self-Hosted Version
22.11.0
CPU Architecture
x86_64
Docker Version
20.10.7
Docker Compose Version
1.29.2
Steps to Reproduce
1.Click "Jira Server Issue" button on the issue details page of Sentry
Expected Result
show error: Oops! Something went wrong It looks like you've hit an issue in our client application. Don't worry though! We use Sentry to monitor Sentry and it's likely we're already looking into this!
If you're daring, you may want to try the following:
Give it a few seconds and reload the page. If all else fails, contact us with more details.
Actual Result
can create jira issue
Event ID
No response
Hi there, are there any logs in your docker containers that could be helpful here? Particularly web?
@hubertdeng123
sentry-self-hosted-web-1 | 07:02:12 [INFO] sentry.integrations.client: integration.http_response (status_string='400' error='400 Client Error: for url: https://jira.foxitsoftware.cn/rest/api/2/issue' integration='jira_server')
curl 'https://sentry.xxxx.com/api/0/groups/376/integrations/2/'
-H 'Accept-Language: zh-CN,zh;q=0.9,en;q=0.8,en-GB;q=0.7,en-US;q=0.6'
-H 'Cache-Control: no-cache'
-H 'Connection: keep-alive'
-H 'Origin: https://sentry.xxxx.com'
-H 'Pragma: no-cache'
-H 'Referer: https://sentry.xxxx.com/organizations/foxit/issues/376/?query=is%3Aunresolved&referrer=issue-stream'
-H 'Sec-Fetch-Dest: empty'
-H 'Sec-Fetch-Mode: cors'
-H 'Sec-Fetch-Site: same-origin'
-H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36 Edg/113.0.1774.50'
-H 'accept: application/json; charset=utf-8'
-H 'baggage: sentry-environment=production,sentry-release=frontend%4022.11.0%2B60999b0f47b3ffe7f2fbbd5e86d9bb9711e5a2c0,sentry-transaction=externalIssueForm.submit,sentry-public_key=b0158496e6f34b4ba249a3d957178b52,sentry-trace_id=241015dfffa04140838491ceacd04fcc,sentry-sample_rate=0'
-H 'content-type: application/json'
-H 'sec-ch-ua: "Microsoft Edge";v="113", "Chromium";v="113", "Not-A.Brand";v="24"'
-H 'sec-ch-ua-mobile: ?0'
-H 'sec-ch-ua-platform: "macOS"'
-H 'sentry-trace: 241015dfffa04140838491ceacd04fcc-ae233d3648e7b812-0'
--data-raw '{"project":"14247","title":"ApiError","description":"Sentry Issue: [INTERNAL-P|https://sentry.xxxx.com:443/organizations/foxit/issues/376/?referrer=jira_integration]\n\n{code}\nHTTPError: 400 Client Error: for url: https://jira.foxitsoftware.cn/rest/api/2/issue/createmeta/10043/issuetypes\n File "sentry/shared_integrations/client/base.py", line 132, in _request\n resp.raise_for_status()\n\nApiError: \n(11 additional frame(s) were not displayed)\n...\n File "sentry/integrations/jira_server/client.py", line 123, in get_issue_types\n return self.get_cached(self.ISSUE_TYPES_URL % (project_id))\n File "sentry/shared_integrations/client/base.py", line 183, in get_cached\n return self._get_cached(path, "GET", *args, **kwargs)\n File "sentry/shared_integrations/client/base.py", line 178, in _get_cached\n result = self.request(method, path, *args, **kwargs)\n File "sentry/integrations/jira_server/client.py", line 89, in request\n return self._request(**request_spec)\n File "sentry/shared_integrations/client/base.py", line 152, in _request\n raise ApiError.from_response(resp, url=full_url)\n{code}","issuetype":"1","priority":"1","fixVersions":"","components":["20028"],"assignee":"[email protected]","customfield_12230":"","customfield_12233":"","customfield_12537":""[email protected]"","customfield_13045":"","labels":"","versions":""}'
--compressed
This problem is solved, but now in the dev member field in jira iusse, an error will be reported: could not find usernames
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog
or Status: In Progress
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
@hubertdeng123
Is there a way to patch this issue for older versions of sentry or is a full upgrade required?
@ZMDominik Do you also encounter the same problem?
Looks like this is still an issue as of here, so keeping this open
Hi, we faced the same problem. https://github.com/getsentry/self-hosted/issues/2718 I saw somebodies noticed the problem is solved. How did you solve the problem? did you able to integrate with Jira Server with a version 9.0.4 or above? Because Atlassian noticed they changed API - createmeta. --> https://confluence.atlassian.com/jiracore/jira-9-4-rest-api-change-log-1178876796.html