JIRA Marketplace Apps
JIRA covers a wide range of needs out of the box, yet some teams want extra abilities: richer charts, test management, diagram drawing, or special field types. The Atlassian Marketplace offers thousands of add-ons, called apps, built by Atlassian and by independent companies.
Layman's View: A Phone App Store
A new phone works fine on day one. Owners later install apps for maps, music, and banking. Each app adds one ability. The Marketplace plays the same role for JIRA. Teams browse, try, and install only what they need.
Team needs a new ability
|
v
Browse the Marketplace
|
v
Start a free trial
|
v
Admin approves and installs
|
v
Team uses the new feature inside JIRA
Popular App Categories
Kinds of JIRA Apps
| Category | Purpose | Sample Use |
|---|---|---|
| Reporting and Charts | Extra reports and dashboard gadgets | Show workload by person in one chart |
| Test Management | Write and run test cases | Link test results to stories |
| Time and Billing | Detailed timesheets and invoices | Bill clients from logged hours |
| Diagrams and Whiteboards | Draw flows inside issues | Sketch a login flow beside the story |
| Automation and Workflow | Add actions and conditions | Run a custom step on a transition |
| Integrations | Connect other tools | Send alerts to a chat tool |
Installing an App
- Open the apps menu and choose the option to find new apps.
- Search by name or browse by category.
- Read the description, reviews, and listed permissions.
- Start a free trial when the app offers one.
- Approve the install. Most sites require an administrator for this step.
- Configure the app and test it in a practice project.
Judging an App Before Install
A careful check prevents costly surprises. Use a simple scorecard.
App Evaluation Checklist
| Question | Why It Matters |
|---|---|
| Does the vendor offer clear support? | Problems need quick answers |
| What do recent reviews say? | Fresh reviews reflect current quality |
| Which permissions does the app request? | Apps may read or change issue data |
| Does the app run on your edition? | Cloud and Data Center versions differ |
| What does the price look like at your team size? | Many apps charge per user |
| Does the vendor publish security details? | Company data may pass through the app |
Atlassian runs programs that mark apps with extra security and reliability checks. Look for those labels on the listing page, and read the exact terms of each program on the official site.
Costs
Some apps cost nothing, and many charge a monthly or yearly fee that grows with the user count. Trials let teams test features before paying. Add up the cost for the full team before committing, since a small fee per user grows quickly across hundreds of accounts.
Risks to Manage
- Too many apps slow the site and complicate upgrades.
- Reports that rely on an app stop working when the team removes it.
- Vendors may change pricing or end support.
- Apps with broad permissions deserve extra review.
Removing an App
Administrators uninstall apps from the same management page. Check which projects, dashboards, and workflows depend on the app first. Data created by the app may disappear, so export anything valuable before removal.
Real-World Example
A quality team wants to run test cases inside JIRA. The administrator lists three candidate apps, reads reviews, and tries each on a sample project for two weeks. One app fits the workflow and stays within budget. The team installs it for the wider group and trains users in a short session. Test results now appear beside the stories they verify.
Summary
The Marketplace adds abilities that JIRA lacks by default. Apps range from reports to test tools to integrations. A careful review of support, permissions, and cost protects the site. Small, planned installs keep JIRA fast and easy to maintain.