Atlassian Marketplace in 2026: Growth, Ratings and Gaps

An admin opens the Atlassian Marketplace to find an app for a problem the team has had for months. The search shows dozens of results. The first one has 30,000 installs and 2.8 stars; the third has 800 installs and five stars. Which one is the safe choice?

Marketplace pages answer that one listing at a time. We wanted the whole picture, so we measured it: the apps Marketplace itself puts in front of customers, their installs, ratings and growth, what their unhappy customers write, and which features Jira and Confluence users have asked Atlassian for the longest. This post is that data.

How we measured

We build apps for Jira and Confluence and track the Marketplace for our own work. For this post:

• The apps: the top 100 of each of Marketplace’s own lists (popular, trending, new and top-grossing) for Jira cloud and Confluence cloud, read from the public Marketplace REST API on 17 October and 21 October 2026. That is 611 different apps on 21 October.
• Growth: the change in each app’s install count between the two snapshots. Marketplace reports active installs, so a number can go down as well as up.
• Unhappy reviews: reviews of three stars or less from the last three years for 47 big apps that customers rate low or that lead a field with no strong app, sorted into themes by keywords.
• Feature requests: the most-voted open requests on jira.atlassian.com, and the most-installed apps a Marketplace search finds for each.

The limits matter: four days is a short window, and installs say nothing about how many people use an app. Treat growth figures as a snapshot of momentum, not a forecast.

1. AI coding agents are growing fastest

Across all 611 apps, the single fastest-growing one was Claude Agent for Jira (by Atlassian): +364 installs in four days, to 9,689. That is more than four times the next app. Its listing says it lets you “assign a Claude Managed Agent to your work items and turn coding tasks into draft pull requests”.

Two more apps in the top five do the same job: GitHub Copilot for Jira (+74, 3,563 installs) and Cursor (+57, 3,726 installs). All three appeared at the top of Jira’s trending list.

What it means: teams are starting to hand Jira work items straight to coding agents. The ticket becomes the agent’s instructions, so whatever the ticket holds goes with it, including the parts nobody meant to share. More on that below.

2. The most installed apps are not the best rated

The ten most popular Jira apps are household names: GitHub for Atlassian (137,632 installs), Figma for Jira (48,401), ScriptRunner for Jira (34,482), GitLab for Jira Cloud (32,193), Checklists for Jira (Free) by HeroCoders (30,316), Timesheets by Tempo (26,318), Xray (25,157), Tempo Core (23,693), JMWE (16,406) and Sentry for Jira (16,301).

Ratings tell a different story. Among the 94 most popular Jira apps with at least 10 reviews, the median is 4.4 stars, but 14 are below 3.5. In Confluence it is 11 of 89, around a median of 4.3.

The pattern is clear: the lowest-rated big apps are mostly free integrations by large companies (source control, error tracking, chat, support desks). They are installed because the other product is already in use, not because they won a comparison. Specialist vendors whose whole business is the app sit at the top of the ratings: Checklists for Jira (4.8 from 1,009 reviews), JMWE (4.8 from 536) and ScriptRunner (4.6 from 826).

3. Why customers are unhappy

We read the recent reviews of three stars or less for 47 apps, 277 reviews in all. The most common theme by far is something that does not work (82 reviews): onboarding that cannot finish, sync that stops, a button that does nothing. Next come a missing feature (43) and support (38). Price came up in only 5.

The apps with the most unhappy reviews were GitLab for Jira Cloud (23), Sentry for Jira (20), the Mermaid diagrams viewer for Confluence (19), Google Chat for Jira Cloud (18) and GitHub for Atlassian (17). A recent one-star review of GitHub for Atlassian reads: “The onboarding flow is broken and cannot proceed when a GitHub account owns more than one organization.”

15 reviews mentioned a migration, most often the move from Atlassian’s older Connect platform to Forge. For buyers, a recent date on a low review matters more than the average.

4. Top-voted requests that are still open

The public Atlassian trackers show what users have asked for the longest. Here are the most-voted open requests on 21 October 2026, and the most-installed app a Marketplace search found for each.

Two things stand out. Some of the oldest requests have strong apps around them (Email This Issue, JMCF), so customers who need the feature today have an answer. Others, like adjusting the font size in Confluence (1,277 votes) or nesting macros (1,215 votes), have only small apps with a few hundred installs or fewer, even though thousands of people voted for them.

5. Where the money is

Marketplace’s top-grossing lists show which apps earn the most. They are not the free integrations that top the install counts.

In Jira, money follows testing, time tracking, admin automation and portfolio planning: jobs that a whole department depends on every day. In Confluence it follows diagrams and tables. Diagram tools are five of the eight most popular Confluence apps (draw.io, Lucidchart, Miro, Gliffy and the Mermaid viewer). We make diagram apps for Confluence ourselves, so read that with our stake in mind; the numbers are Marketplace’s.

Every top-grossing app above is rated 4.1 or higher. Paying customers seem to stay with apps they rate well, while the lowest ratings collect around free apps people install for a single integration.

6. A few vendors build a large share of the popular apps

Appfire has 15 of the 100 most popular Jira apps and 21 of the 100 most popular Confluence apps. Tempo Software has 9 in Jira, HeroCoders 6, and Atlassian itself 5 (plus 3 from Atlassian Labs). For buyers this cuts both ways: one vendor relationship can cover many needs, and one vendor’s pricing or platform decisions reach many of your apps at once.

7. New apps start from almost zero

Of the 100 newest Jira apps on 21 October, the median had 0 installs, only one had 10 or more, and only one had a review. Among the 100 newest Confluence apps, none had 10 installs; the highest had 7. New apps keep arriving, but customers find them slowly: search ranks lean on installs and reviews, which a new app does not have yet.

If you are evaluating a new app, check the vendor instead: their other apps, how fast they answer reviews, and whether the app runs on Forge, inside Atlassian’s infrastructure.

What to do with this as a buyer

1. Read the recent low reviews, not the average. A 4.5 average can hide a broken release last month; a 3.0 can come from years-old complaints that are fixed.
2. Check the Atlassian tracker before you buy. If the feature is “In Progress”, an app may only be a bridge for a few months.
3. Do not read installs as quality. Installs follow how long an app has been listed and how well it ranks in search. Our own comparison of Jira leave-tracking apps found the same.
4. Ask where the data goes. Our post on what enterprise security teams look for in Marketplace apps lists the questions.

Before you hand tickets to an AI agent

If the AI coding agents above are on your list, look at what your tickets contain first. People paste database passwords and API tokens into Jira comments to unblock a teammate; an agent assigned to that work item reads them as part of its instructions.

Secret Sentinel checks every Jira issue, comment and Confluence page when it is saved, redacts credentials in place and opens a Jira incident to rotate them. To see what one ticket exposes right now, paste it into our free API key leak checker; it runs only in your browser.