This guide discusses Behave Pro for Jira Cloud. If you want to configure a Server or Data Center deployment of Behave Pro with Bitbucket please read this article.

There two major steps to connect Behave Pro with Bitbucket:

  1. Installing the Behave Pro Git connector to your Bitbucket workspace. Behave Pro will then be able to access the required repositories within the workspace. A user with Jira Administration privileges and permissions to install apps within Bitbucket will need to do this step.
  2. Enabling Behave Pro on your Jira project and configuring it to synchronize with a repository within the Bitbucket workspace. A user with Jira Project administration privilege will be required for this step.

Installing the Behave Pro git connector into Bitbucket

Behave Pro needs to be installed into Bitbucket to enable communication to and from Jira. This installation to be done by Users with Administrator privileges in Jira and Bitbucket.

Within Jira open the settings menu on the right-hand side of the top navigation bar and select Apps. This will open the App manage for Jira

Within Jira's Apps manager find Behave Pro on the left-hand navigation and select Getting started. This will open the setup task for Behave Pro.

Behave Pro's setup process will allow you to choose which repository provider to connect to and clicking on Connect will start the installation process for Behave Pro on Bitbucket.

Bitbucket will ask you to authorize access for Behave Pro. If you have more than one Bitbucket workspaces a drop-down menu will allow you to choose a workspace to install Behave Pro into. Please check you have the correct workspace before clicking Grant access to complete the installation process.

Note, if you have multiple Bitbucket workspaces and want Behave Pro to work with all of them then you need to repeat these complete setup instructions for each workspace.

Once Behave Pro has been successfully installed into Bitbucket you will be automatically returned to Jira. Once back in Jira you will be given a choice of projects to select for configuring Behave Pro. If you are the project administrator you can select your project or leave the next section to be completed by the project administrator.

Enabling Behave Pro and Bitbucket on a Jira project

If you have completed the previous section Installing the Behave Pro git connector into Bitbucket then you will be able to search/select a project to configure for Behave Pro and this will send you to the page titled Select Your Workflow.

If your Jira Administrator has installed Behave Pro for you and connected it to Behave Pro for you then you will need to start the project installation process. Open your project settings, and select Behave Pro on the left-hand menu. This will open the Behave Pro settings for your project and you can see that is currently disabled

Click on the slide toggle opposite User Story discovery with BDD toggle to start the Behave Pro project configuration process.

The first step is to click Select within the git section.

Next, you will need to select your Bitbucket workspace in Organisation and choose the repository you wish to connect. Before clicking continue, you will need to select your teams branching strategy, this is an important decision as Behave Pro will work with the repository in different ways depending on this setting.

If you and your team create branches for every user story or bug and open Pull Requests to perform code reviews before merging then select Feature branching. If changes are committed directly to the main/master/trunk branch without creating any branches then select Trunk based.

If you are still unsure about your team's strategy please read this article to help you decide which strategy works for you.

Once you have configured these settings and click Continue you will be presented with the branch settings page.

In the branch list, you should select your base or default branch for the repository. This is usually called master, main, or trunk for Feature Branching or Trunk based development projects. For a repository using a Gitflow strategy then the branch will be called develop instead of master.

Behave Pro needs to understand where feature files should be stored within your repository and this is specified in the Feature file directory. This directory should already exist within the repository and any feature files stored at this location will be automatically imported into Behave Pro.

Once this has been configured you've successfully configured Behave Pro.

At the end of the this installation flow you will be redirected to the requirements page of your project where you can begin to create feature files, write scenarios and see them appear in your Bitbucket project.

Did this answer your question?