AWS Q Business Jira Connector (Error 410 Gone)

It appears you're encountering an error with the Amazon Q Business Jira connector related to an API deprecation in Jira. The error message indicates that the Jira API endpoint being used by the connector has been removed, and Atlassian recommends migrating to the /rest/api/3/search/jql API instead.

Unfortunately, the Amazon Q Business Jira connector doesn't currently provide a way for users to directly modify the API endpoints it uses to connect to Jira. The connector is designed to work with specific Jira APIs, and if Atlassian has deprecated an API that the connector relies on, this could cause connectivity issues.

Since you mentioned that it worked on a personal account recently, there could be a few possible explanations:

1. Your personal Jira instance might be on a different version that still supports the deprecated API
2. There might be configuration differences between the environments
3. Atlassian might have fully removed the API very recently

I would recommend the following steps:

1. Verify that your Jira URL is correctly formatted (e.g., https://yourcompany.atlassian.net/)
2. Check that your authentication credentials (username and API token) are valid and have the necessary permissions
3. Contact AWS Support for assistance with this specific API deprecation issue, as they may need to update the connector to use Atlassian's new recommended API endpoint

The Amazon Q Business team would need to update their connector to use the new Jira API endpoints if Atlassian has fully deprecated the ones currently in use.
Sources
Connecting Amazon Q Business to Jira using the console - Amazon Q Business
Improve the productivity of your customer support and project management teams using Amazon Q Business and Atlassian Jira | AWS Machine Learning Blog
Jira connector overview - Amazon Q Business
Understand error codes in the Amazon Q Business Jira connector - Amazon Q Business