Copado Essentials Plus allows you to take advantage of a bi-directional sync with Jira, helping you to easily search and select any pre existing Jira issue for assignment to a Work Item or Deployment. Any changes made using Copado Essentials Plus will then be reflected in your Jira issue history, and any changes made to Issue status in Jira will be reflected in Copado Essentials Plus.

The video below will take you through how to set up the Jira integration with Essentials Plus:

In order to set up this integration, you'll start by opening the Settings within Jira, clicking on Security, then "Create and Manage API Tokens". From here, you can name and generate an API token that can then be copied for use with Copado Essentials Plus.

Next, navigate to Copado Essentials Plus, click on the user icon on the top right of the screen, and select Account Settings. The Jira Integration Settings will be in the column on the lefthand side of the screen, which is where you can insert your Jira username, base URL for the Jira instance, and the unique API token that has been generated in Jira.

Note: Currently the Jira Integration with Copado Essentials is only supported with Jira Cloud and does not support Jira Server (on premise). The easiest way to see if you are on Jira Cloud or Server is to look at the menu, if the main menu for Jira is on the left side with you avatar at the bottom you are on Jira Cloud. If the menus are at the top with your avatar on the right then you are on Jira Server.

After successfully integrating with Jira, you're now able to select any available Jira issue to associate with either a Work Item or Deployment from the Issue drop down field.

Once you hit save you will be brought to the familiar components selection screen. After you run the deployment/Work Item you can then click into the section titles Issue & Note:

Any changes made in Jira will be reflected here in Essentials within the Issue & Note section.
​
​Note: "Status" field is currently not bi-directional and changes would need to be made in Jira in order to update the status in Copado Essentials.

Prior to utilizing an API token for integrations with Jira, Copado Essentials Plus utilized an integration between Jira and Version Control facilitated by a DVCS connector. This remains an option for teams that prefer a Git centric approach to development, and setting up this integration will allow you to associate your Essentials Plus work items or deployments with a Jira ticket (aka User Story).

To connect Jira to Bitbucket, please follow this guide: https://support.atlassian.com/jira-cloud-administration/docs/connect-jira-cloud-to-bitbucket/

To connect Jira to GitHub, please follow this guide: https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/

To connect Jira to GitLab, please follow this guide: https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-gitlab/

Once you connected Jira to Bitbucket, GitHub, or GitLab via the steps above, Copado Essentials will ensure that deployment activities including Git commits, branches and pull requests are automatically reflected in Jira. All you need to do is to associate each Copado Essentials deployment with a Jira Issue, like below:

As soon as you perform a Git commit via Copado Essentials Plus, you can see development activities updated immediately in Jira as below: