Progressify
Forge-native · Runs on Atlassian

Atlassian apps built for teams that run on trust.

Progressify ships Forge-native apps for Jira, Confluence, and Jira Service Management — engineered so your data never leaves Atlassian, and your teams never leave their workflow.

Browse apps Why Forge?
Session · Live
ACME Sprint 42 · Backlog refinement
8 voters
ACME-142
Add multi-region failover to booking API
3 of 12
?
2
?
5
?
?
21
Average
5.8
Median
5
↵confirm

Built natively on Atlassian Forge — the only platform where your data never leaves Atlassian.

Atlassian ForgeJira CloudJira Service ManagementConfluence CloudRuns on Atlassian
Agile estimation

Planning Poker for Jira

Planning poker directly inside Jira Cloud — no iframes, no external servers, no context switching. Teams estimate backlog issues together in real time and results save straight to Jira fields.

  • Live voting with simultaneous reveals, powered by Forge Realtime
  • Keyboard-first: number keys to vote, Enter to confirm, no mouse required
  • Fibonacci and T-shirt decks — estimates save to Story Points or any custom field
Learn more
Session · Live
ACME Sprint 42 · Backlog refinement
8 voters
ACME-142
Add multi-region failover to booking API
3 of 12
?
2
?
5
?
?
21
Average
5.8
Median
5
↵confirm
Progress tracking

Better Epic Roll-up & Progress

Automatic progress tracking on every epic — status categories, story points, and time tracking — with visual bars on the issue view and a dashboard gadget for multi-epic reporting. Zero configuration required.

  • Three metric types: status categories, story points, and time tracking
  • Event-driven updates recalculate within seconds of child issue changes
  • Dashboard gadget with JQL filtering across up to 50 epics per page
Learn more
Epic · ACME-42
Q2 Launch — Booking platform v2
Updated 2m ago
Status categories62% · 18 of 29 issues
Done 13In progress 5To do 11
Story points40 / 64

24 points remaining across 11 issues

Time tracking38h / 60h

22h remaining, 4h logged this week

Auto-recalculates on child changeRefresh now
Workflow automation

Default Field Values for Jira

A visual rule builder that auto-populates Jira fields when issues are created or transitioned. Replaces ScriptRunner Groovy post-functions with a modern, maintainable, Forge-native alternative.

  • Visual rule builder — no Groovy, no scripts, no consultants
  • Triggers on issue create and workflow transitions
  • Supports every standard and custom field with conditional logic
Learn more
Rule
Incoming Payments escalation
Active
When
Issue is created in project Payments
If
Issue type is Incident and labels contain prod
Then set
  • PriorityHigh
  • ComponentPayments · Backend
  • Due date+ 3 business days
  • AssigneeRotates team-ops-lead
Applied to 1,284 issues · last 30 daysSave rule
The numbers

Forge-native by design, trusted by default.

9Forge-native apps shipped or in active build
100%Runs on Atlassian — zero external infrastructure
0Bytes of customer data that ever leave Atlassian
96%Peak unit-test coverage across the flagship apps
The full portfolio

More ways to ship trust inside Atlassian.

View all apps
Jira Cloud

Issue Templates

Reusable templates for faster, more consistent issue creation.

Workflow automation
Jira Cloud

Duplicate Detection

Find and consolidate duplicate issues with field matching.

Data quality
Jira Cloud

Recurring Tasks

Automatic issue creation on a schedule, from templates.

Workflow automation
Jira Cloud

Dashboard Charts

Rich dashboard gadgets — burndown, velocity, cumulative flow.

Data & analytics
Jira Cloud

Issue Reminders

Personal and team reminders on issues via Jira and email.

Productivity
Jira Service Management

AI Triage

Automatic classification and routing for service requests.

AI & automation
Security

Enterprise trust, inherited from Atlassian.

Every Progressify app runs inside Atlassian's Forge platform — so your security, compliance, and data-residency guarantees carry over automatically. Nothing you approve for Atlassian Cloud needs re-approving for us.

Runs on Atlassian
Eligible
Forge Platform
Native
SOC 2
Roadmap
GDPR
Compliant

Zero data egress

Customer data never leaves Atlassian. Storage, compute, and events all stay inside the Forge platform sandbox.

Forge sandbox isolation

Each app runs in an isolated sandbox with least-privilege scopes. No shared infrastructure, no cross-tenant risk.

Atlassian-managed infra

No servers to patch. No AWS accounts to audit. Atlassian owns the runtime so you inherit their compliance posture.

Scoped OAuth

Every app requests the minimum Atlassian scopes required. Read-only where possible, explicit write consent where needed.

Audit-ready logging

Forge platform logs every app invocation. Pair with your existing Atlassian audit log for full traceability.

No third-party LLMs

AI features use the Forge LLMs API exclusively. Your prompts and completions never leave the Atlassian trust boundary.

Frequently asked

Questions we hear before the first deployment.

What does Forge-native actually mean?
Every app is built on Atlassian Forge — Atlassian's first-party development platform. Storage, compute, events, and UI all run inside Atlassian infrastructure, which means your data never leaves the trust boundary you already approved for Jira or Confluence. No external servers, no AWS accounts to audit, no separate vendor assessment.
How is this different from Connect apps?
Connect apps run on third-party infrastructure and pipe Atlassian data back and forth over HTTPS. Forge apps run inside Atlassian's own sandbox with zero external egress. Atlassian has publicly committed to Forge as the future of the Marketplace, and sets end-of-life plans for Connect apps.
Where does my data live?
Inside your Atlassian Cloud tenant. Forge Storage lives in the same region and compliance envelope as your Jira or Confluence data — no replication to outside regions, no caching on our infrastructure, no analytics exports. If you're on Atlassian Government Cloud, your Forge data stays inside that boundary too.
How is pricing structured?
Per-user, billed through the Atlassian Marketplace on the same invoice as your other apps. Every app has a free tier for the first 10 users so small teams and pilots cost nothing, with transparent tiered pricing above that. We don't hide the price list behind a sales call.
Do you support Atlassian Government Cloud (AGC)?
AGC readiness is on the roadmap for every app we ship. Because Forge apps inherit the underlying platform's compliance posture, AGC support is a matter of Marketplace listing and testing — not a re-architecture.
What's the support experience like?
You get a named support channel and a human who knows the app. We don't staff a rotating level-1 queue. If you're evaluating an app for a large rollout, ask for a working session — we'll help plan the deployment.
Do your AI features send my data to OpenAI or Anthropic?
No. All AI features use the Forge LLMs API exclusively — the same trust boundary as the rest of the platform. Prompts, completions, and embeddings stay inside Atlassian. We will not ship AI features via third-party model providers.

Ship trust into your Atlassian workflows.

Browse the Marketplace Contact us