Guides for Jira teams

Guide · Connect end of support

Behave Pro and the end of Connect: what to do with your scenarios

If your team writes BDD scenarios in Behave Pro on Jira Cloud, here is what Atlassian's move away from Connect means for you, how to take a full copy of your features today, and a calm way to decide what comes next.

What is changing

  • Connect end of support is 31 January 2027. After that date Atlassian no longer supports Connect apps, and they may stop working as the platform changes.
  • Connect apps can no longer ship updates through the Marketplace since spring 2026.
  • Jira has started telling admins, and then users, when an installed app "might stop working soon".

Apps built on Forge, Atlassian's current platform, are not affected.

Is your Behave Pro affected?

On the Atlassian Marketplace, the cloud version of Behave Pro: BDD in Jira with Cucumber is listed as a Connect app: its latest cloud version is 2.0.66-AC (the -AC ending marks Connect), released on 24 November 2022, as of October 2026. Two ways to check your own site:

  • In Jira, open Apps → Manage your apps and look for the "might stop working soon" notice next to Behave Pro.
  • Ask Hindsight Software, the vendor, whether a Forge version is planned and when. If one is coming, the simplest path may be to wait for it.

Data Center is a different story

The Data Center version of Behave Pro keeps receiving releases (3.0.2 on 1 October 2026), and Connect does not concern it. This guide is only about Jira Cloud.

Take a copy of your features now

Whatever you decide, keep a copy of every feature file. Behave Pro keeps features on its own service and can hand them out as standard .feature files through its export API, one .zip per project:

Terminal
curl --fail -u USER:API_KEY \
  "https://behave.pro/rest/cucumber/1.0/project/PROJECT_ID/features?manual=true" \
  --output features.zip

USER, API_KEY and PROJECT_ID are in Behave Pro's project settings. Do it once per Jira project, unzip, and check that the scenarios you care about are there. If your team already lets Behave Pro sync with a Git repository, that repository holds the same files, so you have a copy already.

What your test automation needs

Cucumber, SpecFlow, Behave and other Gherkin runners read plain .feature files from your repository. They do not need Behave Pro at run time. As long as the files are in Git, your automated tests keep running while you change the Jira side.

A calm way to switch

  1. Export every project

    As above, and keep the .zip files somewhere safe.

  2. Put the features in Git

    If they are not there yet, commit them to the repository your test runner uses.

  3. Install the replacement next to Behave Pro

    Both can run side by side. Nothing changes in your issues while you compare.

  4. Import and check one project

    Open a few stories and compare the scenarios on the issue with the old app.

  5. Point CI at the new place for results

    If you report test runs to Jira, switch that step last.

  6. Uninstall Behave Pro

    Once the team works in the new tool and the exports are stored.

Choosing a replacement

  • Built on Forge (look for "Runs on Atlassian" or ask the vendor), so you don't face the same move again.
  • Imports your export as it is, with a preview, so stories keep their scenarios.
  • Keeps .feature files in Git, both ways, so the files your tests run are the ones the team reviews in Jira.
  • Shows test results on each scenario, if your team used that.

FeatureBridge – BDD & Gherkin scenarios with Git sync (made by us, YTI Digital) is one option: a Forge app that keeps Gherkin scenarios on Jira issues, syncs them with GitHub, GitLab or Bitbucket in both directions, shows CI results per scenario, and imports a Behave Pro export with a preview of every match. Its import page walks through the steps, and we help at support@yti.digital. For the format itself, see Given/When/Then acceptance criteria in Jira and Gherkin feature files in Git and Jira.