SIAgentNews.com
← All news
Developing

Atlassian lets older Connect apps add Forge features without a rewrite

Partners can now add Forge-only features to existing Connect apps step by step, and Atlassian says the first one takes under an hour.

· First reported by atlassian.com

over 100Connect apps already using Forge features since the pilot

The short version

  • Connect apps can now adopt Forge modules without a companion app or full rewrite
  • Atlassian says adding the first Forge module takes less than an hour
  • One command converts the Connect descriptor into a Forge manifest
  • Over 100 Connect apps have started using Forge features since the pilot began
  • Bitbucket Connect apps and apps using certain features are not eligible yet

Why it matters

If your team uses add-ons for Jira, this change should mean fewer clunky double installs and faster arrival of new features. It also shows a common pattern in software platforms: move people to the new system in small steps rather than forcing a big-bang rewrite. Your vendor's pace on this is worth asking about.

What Atlassian announced

As atlassian.com reported in a developer blog post, companies that build add-on apps for Atlassian products can now bring Forge features into apps they already have on Connect. The page we reviewed is a reader comment on that post, and the substance comes from the post itself.

Connect and Forge are two ways to build apps for Atlassian products such as Jira. Forge offers extension points, meaning the places where an app can plug into the product. Two examples are custom fields and changes to Jira's user interface. Until now, Connect apps had a hard time using those Forge-only features.

Some partners worked around this by building a second, companion Forge app that installs next to the main Connect app. Atlassian says that meant extra work for partners and a less intuitive experience for customers, who ended up with two things to manage.

How the move works

The process is meant to be gradual. A developer does not have to rebuild the app on Forge. Instead they add Forge pieces, called modules, one at a time. Atlassian says that with its new tooling, adding the first module takes less than an hour.

The preparation has a few steps:

  • Convert the Connect descriptor, a settings file that describes the app, into a Forge manifest, which is the Forge version of that file. A command-line tool (CLI, a program you run by typing commands) does this with a single command.
  • Register the app as a Forge app with the forge register command, so Atlassian recognizes it later.
  • Deploy the app to the Forge environment and install it on a development site for testing.

Atlassian says none of this changes or overrides the existing Connect app. The Connect version stays unchanged and available on the Atlassian Marketplace, the store where customers find apps.

What customers see

Once a developer has added and tested one or more Forge modules, they can publish a Forge successor to their Connect Marketplace listing. Atlassian says this keeps the existing listing and carries over all reviews and installs.

When current customers upgrade, or new customers install, they get the version that includes the new Forge modules. For the customer, the goal is one app that simply gains features, not two pieces of software to keep in sync.

Developers can also go further. They can keep using the Connect app as a remote backend for a Forge app. Atlassian points to guides for two Connect toolkits, Atlassian Connect Express and Atlassian Connect Spring Boot, for that route.

Early signs and limits

Atlassian says more than 100 Connect apps have started using Forge features since it began working with a pilot group. One partner, Toolsplus, is quoted. Tobias Binna of that company said, "we have confidence that we are moving in the right direction." That is a vendor's view, shared on Atlassian's own blog, so it is a good sign but not an independent test.

There are limits. Atlassian says its analysis shows most Connect apps can start adopting Forge, but apps that use certain features cannot yet. Bitbucket Connect apps are also not eligible for now. The company points developers to a limitations page and suggests watching the linked issues there to see when blockers are removed.

The post does not say how many apps are not eligible, or when the remaining gaps will close.

What happens next

Atlassian is inviting feedback through its developer community, where it says it will watch for questions. It also plans a community event session in the coming weeks, with a live demo and a question-and-answer period. There will be two sessions with the same content, one timed for Europe and one for the US.

Atlassian's stated reason is that as Forge gains new capabilities, it wants all apps to have access to the best of what Forge offers. For non-developers, the practical question is how quickly the apps you rely on take advantage of this.

What to watch

  • Which of the blocked app types become eligible as Atlassian clears items on its limitations page
  • Whether Bitbucket Connect apps get a path to adopt Forge
  • How many Connect apps publish Forge successor listings beyond the first 100

Try it

If your team relies on a Jira add-on, check the vendor's Marketplace listing or release notes, or ask them whether they plan to add Forge features.

Sources and links

First reported by atlassian.com. Written by the SI Agent News Desk from the reporting above.Written with AI from the source above. Every number is checked against the source. Spot a mistake? Corrections.

Liked it? Say why

Add a line for other readers.

No account needed. We never show your email. Comments with links, ads or abuse are held and not shown. Your comment shows after a quick check.

More AI news