Jira Service Management (JSM) portals are where customers file requests—and where generic Jira apps often feel wrong. Forge modules aimed at the customer portal let you add request actions and user-menu experiences without forcing agents into the wrong UI.
Useful portal modules
- Portal request view action — modal from the request details page.
- Portal user menu action — entry in the portal user menu.
Both can support unlicensed / customer accounts when configured correctly. Anonymous access is typically off—plan authentication accordingly.
Good portal app ideas
- Show order or subscription status from WooCommerce/Shopify beside a request.
- “Attach invoice” pulls a PDF from your billing API.
- Guided remediation steps before a ticket escalates to agents.
- Consent or KYC checklist stored as request properties.
UX constraints that matter
- Portal users are not Jira power users—copy must be plain language.
- Keep modals fast; portal traffic is bursty after outages.
- Never expose internal comments or agent-only fields.
- Match Atlassian design guidance; Marketplace review notices UI drift.
Security notes
- Treat portal callers as untrusted; authorise against the request and customer context.
- Minimise scopes; prefer request-scoped data over project-wide reads.
- Log access for regulated industries; avoid logging full PII payloads.
Build vs buy
Buy Marketplace portal widgets for commodity FAQ/knowledge. Build Forge when the portal must talk to your systems of record with EU-friendly hosting and a DPA you can sign.
Need this built? HostHob ships production integrations and Marketplace-ready apps from Rotterdam. See our services or Scope a JSM portal Forge app.