You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When jira is hosted under https://sub.domain.com/jira, danswer tries to call the jira api with https://sub.domain.com/rest/api instead of https://sub.domain.com/jira/rest/api
05/15/2024 01:07:10 PM run_indexing.py 356 : [Attempt ID: 78] Running indexing attempt for connector: 'JiraConnector-https://sub.domain/jira/projects/PID', with config: '{'jira_project_url': 'https://sub.domain/jira/projects/PID', 'comment_email_blacklist': []}', and with credentials: '1'
05/15/2024 01:07:10 PM run_indexing.py 71 : [Attempt ID: 78] Unable to instantiate connector due to JiraError HTTP 404 url: https://sub.domain.com/rest/api/2/serverInfo
When jira is hosted under
https://sub.domain.com/jira
, danswer tries to call the jira api withhttps://sub.domain.com/rest/api
instead ofhttps://sub.domain.com/jira/rest/api
This is due to the assumption that the jira base url is just the "netloc"
https://github.com/danswer-ai/danswer/blob/main/backend/danswer/connectors/danswer_jira/connector.py#L32
There should be logic similar to the confluence connector where the path is analysed to determine the base url
https://github.com/danswer-ai/danswer/blob/main/backend/danswer/connectors/confluence/connector.py#L68
This could be done using "projects" as an indicator for the start of the actual jira url (e.g. in https://sub.domain/jira/projects/PID/xxxx)
The text was updated successfully, but these errors were encountered: