Side-by-side comparison · 24 data points
- Add custom HTML to Confluence pages - Use CSS and Javascript to enhance looks and functionality - Run code snippets - Embed external contents and web pages as Iframe
| HTML Macro for Confluence | Awesome Custom Fields – Custom Fields for Jira & JSM | |
|---|---|---|
| Tagline | ||
| Description | ||
| Screenshots | — | — |
| Languages | ||
| Platforms | ||
| Developer | ||
| Listed | — | — |
| Last updated | — | — |
Custom fields that just work. Let teams capture structured data and surface key info at a glance in Jira and JSM. Faster decisions, fewer errors and work that keeps moving. Quick setup with zero maintenance.
| Metric | HTML Macro for Confluence | Awesome Custom Fields – Custom Fields for Jira & JSM |
|---|---|---|
| Rating | ★ 5.0 ★ | 5.0 ★ |
| Total reviews | ★ 31 | 27 |
| Active installs | 2,327+ | 1,120+ |
| Free plan | — | — |
| Pricing | From $0/yr | From $0/yr |
| Pricing tiers | 6 tiers | 6 tiers |
| Listed features | 3 | 3 |
HTML Macro for Confluence and Awesome Custom Fields – Custom Fields for Jira & JSM are evenly matched on rating (5.0★ vs 5.0★) — the differentiator comes down to pricing fit, feature breadth, and which app's interaction pattern suits your team's workflow.
Pricing entry tiers: HTML Macro for Confluence at From $0/yr, Awesome Custom Fields – Custom Fields for Jira & JSM at From $0/yr. Check each app's tier structure for the capacity limits you actually need before deciding — the headline number is the same shape, but the gating shape per tier (seats, usage volume, integrations) varies.
Recommended evaluation path: install both apps' free tiers (where available) and run them in parallel on a small cohort for 7-14 days before committing. The data tables below show the per-feature breakdown — for most teams the deciding factor will be a single integration or workflow detail that's hard to compare from listing pages alone.
This verdict is generated from the live marketplace data on this page — rating, review count, pricing tier, and category position all refresh from the canonical Atlassian Marketplace listing every 24 hours. AppRanks does not accept payment to influence comparison outcomes; the methodology is documented on the About page and applies identically to every pair on the site.
Read each app's audit: HTML Macro for Confluence audit • Awesome Custom Fields – Custom Fields for Jira & JSM audit
| Keyword | HTML Macro for Confluence | Awesome Custom Fields – Custom Fields for Jira & JSM |
|---|---|---|
| forms | #54 | #150 |
| form | #98 | #191 |
Both HTML Macro for Confluence and Awesome Custom Fields – Custom Fields for Jira & JSM offer paid plans only. HTML Macro for Confluence starts at From $0/yr; Awesome Custom Fields – Custom Fields for Jira & JSM starts at From $0/yr. Compare the per-tier features in the Pricing section above before committing.
HTML Macro for Confluence (5.0★, 31 reviews) and Awesome Custom Fields – Custom Fields for Jira & JSM (5.0★, 27 reviews) are essentially tied on rating. Look at review velocity and individual reviewer quotes — both visible on each app's detail page — to differentiate.
HTML Macro for Confluence holds the higher average rating (5.0★ vs 5.0★). That is the one dimension AppRanks can separate them on here — read both apps' detail pages for the feature breakdown and recent listing changes.
Both apps are one-click installs from the Atlassian Marketplace. HTML Macro for Confluence has the deeper published review base (31 vs 27), which often — though not always — accompanies better-tested setup docs. AppRanks doesn't measure setup time directly: read the recent reviews on each app's detail page for user-reported install experience.
HTML Macro for Confluence typically suits early-stage and growth-mode teams based on its published review base (31 reviews). Awesome Custom Fields – Custom Fields for Jira & JSM typically suits early-stage and growth-mode teams based on its published review base (27 reviews). A larger review base generally means the app has been exercised at scale — relevant if you are processing high volume or handling enterprise compliance requirements.
Migration support varies by app and category. HTML Macro for Confluence and Awesome Custom Fields – Custom Fields for Jira & JSM both publish their export options on their marketplace listing pages (or in their support docs); some apps offer one-click import from competitors, others require CSV. The fastest check: search "import from Awesome Custom Fields – Custom Fields for Jira & JSM" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.