License a Forge app migrated from Connect

Forge Adopting Forge from Connect
,
3

Hi @jhazelwood,

thanks for your reply.

My question stems from exactly what you’re saying.

Let me explain in detail:

As I mentioned, I migrated my Connect app to Forge. The Forge app only consists of the manifest.yml file, which includes the Connect app as “remotes”

Now I have two scenarios:

  • Scenario 1: If I had the licensed Connect app installed in a Jira instance, and I update it with the Forge app… everything works.

  • Scenario 2: If I install the Forge app in a clean Jira instance (without the Connect app installed), it doesn’t recognize the license.

image
image722×179 3.47 KB

I’ve tried two ways:

  1. The old version: using an environment variable.
forge variables set -e development LICENSE_OVERRIDE active
  1. Installing with the license enabled.
forge install --environment development --license active

I’m also not sure if it could be an issue with the Forge environment, because I had a similar experience with storage in another Forge app.

Hence my question:
when the Forge app replaces the Connect app in the Marketplace, will users who didn’t previously have the Connect app licensed and install the Forge app be able to use it without licensing issues? Will the Forge license be used to access the Connect app “remotes”?

Thank you very much.