Jira Cloud and Server Plugins
The Jira integration plugins have been split out into two separate plugins to handle cloud and server Jira integrations separately. As of 29th April 2019, Atlassian deprecated user password functionality in their cloud version of Jira so as to align with European GDPR regulations. For TestRail, this means that cloud and server Jira integration need to be treated somewhat differently. In a nutshell:
- For Jira server integration, you should use the “Jira REST” (Jira Server 5.x, 6.x, 7.x and later) plugin, and authenticate the integration using your Jira username and password combination.
- For Jira cloud integration, you should use the “Jira Cloud” plugin, and authenticate the integration using your Jira email address and Jira API token.
Configuring Jira Server (TestRail 5.7 Onwards)
Follow the instructions here, using the Jira Server 5.x, 6.x, 7.x, and later plugin. For Jira Server, your Jira username and password must be used for the integration itself, and for individual users via their TestRail user settings.
Configuring Jira Cloud (TestRail 5.7 Onwards)
Follow the instructions here, using the Jira Cloud plugin when prompted to select. Note that for Jira Cloud, the integration requires both the integration administrator and individual users to provide their Jira email address and Jira API token. Instructions for generating Jira user API tokens can be found here
Upgrading to TestRail 5.7
If you’re upgrading to TestRail 5.7 and using a hosted Jira solution (i.e. Jira Cloud) – then you’ll need to change the integration plugin accordingly, since Atlassian will be deprecating some of their API functionality soon, which means that the Jira Server 5.x, 6.x, 7.x and later plugin will no longer work for Jira Cloud users.
Once the plugin has been changed, the existing jira_user and jira_password variables will be redundant, having been replaced by jira_email and jira_token variables instead. You will need to enter new credentials both at the integration administrator level and for all of the users that have configured user credentials stored for the integration in their TestRail User Settings page. We recommend removing the old jira_user and jira_password variables in this case, to prevent any confusion when asking users to upgrade their credentials.