Introduction

Teams who want to integrate MettleCI Workbench with Jira will usually need to engage a 3rd part Atlassian Jira Administration team to complete the configuration. While the integration method used by MettleCI is simple, secure and fully supported by Atlassian, most Jira Administrators are not familiar with the OAuth integration protocol used and are hesitant to configure the required AppLink to a non-Atlassian application such as MettleCI.

This page is intended for Jira Administrators who want to understand why MettleCI Workbench integrates with Jira via OAuth and provides the common questions asked while evaluating this type of Jira Integration is secure and won’t compromise the integrity of their Jira application or the security of the information contained.

What is MettleCI and how is it related to Jira?

For traditional software development such as Java or C/C++, developers make changes to source code on their local machines and commit their work to Git/Bitbucket using a Git client. Once in Git, modern software development tools such as those provided by Atlassian can automatically build, test and deploy software and provide a complete audit trail from software produced all the way back to issue raised in Jira. In contrast, DataStage development involves using graphical tools to develop ETL jobs on a shared server. There is no source code and no simple way of committing work to Git/Bitbucket.

MettleCI Workbench is an on premise, web based application which allows DataStage developers commit their changes to Git/Bitbucket and to leverage modern development practices. When a DataStage developer initiates a Git commit via MettleCI Workbench, they are presented with the following screen that allows them to select the DataStage assets to commit, associated one or more Jira Issue IDs and add a brief description of the change:

During the Git commit process, MettleCI Workbench ensures the message included with the Git commit is formatted so that Git/Bitbucket recognizes that there is a connection between the change and Jira: