Connect Enterprise Architect with Jira Cloud

[ED DevOps D2]

We recently downloaded a trial version of an atlassian jira add-on named 'EA Connector for Jira' which is meant to connect Jira with Enterprise Architect desktop appilcation.

However, when we try to login to Jira Cloud from within EA using our Jira credentials, we get a message that the connection could not be established. The logs include the following error: 'The remote server returned an error: (401) Unauthorized.'
We tried logging in using both a username (full email) and a password, as well as a username (full email) and an api token combination but none of them worked.

The company selling the add-on cannot provide support at the moment, so we are stuck.

Has anyone used this add-on and managed to successfully log-in or have any idea about what the problem might be?

[OpsHub - Enterprise class Integration and Migration Solutions for Jira]

Hi @ED DevOps D2

This usually points to an authentication problem with the EA Connector for Jira between the two systems. Here are a few things you can check:

• Jira Cloud API Token – Since you're using Jira Cloud, ensure that you're using an API token rather than your regular Jira password. Jira Cloud has moved to API tokens for authentication, so make sure you're generating a new token from your Jira Cloud account settings and using that instead of a password.
• Permissions – Make sure the account you’re using has the appropriate permissions in Jira Cloud, especially when it comes to using the API. Check that your account has access to the necessary Jira projects and the required admin rights to allow the integration to work.
• Connector Configuration – Double-check how you’ve configured the EA Connector settings. There might be specific configurations or connection details (e.g., URL format or region-specific issues) that are missing or incorrect.
• Check URL Formatting – Sometimes, the error can occur if the Jira URL used in the connector setup is wrong (for example, you might be using the wrong subdomain or missing a part of the URL).
• Authentication Type – If the add-on is still using the old username/password combo, that might be a red flag since Jira Cloud has moved to OAuth or API tokens for authentication.

If you’re still stuck, and the add-on support isn’t available, it might be worth looking into a different integration approach that handles the integration more reliably. You may consider OpsHub Integration Manager, an Atlassian Partner and a no-plugin solution to connect Jira Cloud with Enterprise Architect. It supports a wide range of integrations, is easy to configure, and doesn’t require technical setup. Plus, it works without worrying about manual authentication issues like you’re encountering.

You may refer to our Atlassian listing on EA - Jira integration on Atlassian Marketplace.

Hope it helps!