Mortise Apps Browse apps

Known limitations

Last updated 2026-11-09

These come from the Atlassian platform, not from the app. We state them plainly so you can plan.

  1. Team membership is not readable by apps. Atlassian's Teams API does not grant Forge apps access to member lists (tracked as JRACLOUD-92072). The app can show team size and whether you are a member. Features such as myTeams(), "notify the whole team" and per-member workload by team will ship when Atlassian opens the API, which their Teams product team has said they aim to do by the end of 2026.
  2. Native gadgets stay unchanged. The app cannot add Team to Jira's own Two Dimensional Filter Statistics or Pie Chart gadgets. It provides its own gadgets instead.
  3. No visual changes to Jira. Team colours, icons and card layouts cannot be altered by any app.
  4. 5,000 issues per gadget, 3,000 issues per report scope. Narrow the JQL for larger data sets; the page says when a cap was hit.
  5. Velocity is computed from the Sprint field, not from board history. Each issue's Sprint field lists every sprint it was in, so committed, completed and carried-over counts need no board configuration and work across boards. The trade-off: work added or removed mid-sprint is not modelled; a sprint is credited with what it held at close. Jira's own Sprint Report on a single board remains the place for mid-sprint scope changes.
  6. Velocity needs Jira Software sprints. Business and Service Management projects get Workload, Dependencies, Aging and Hygiene, and an empty Velocity tab.
  7. JQL function form. App functions must be written as issue in teamIn(...), not Team in teamIn(...). This is how Jira Cloud exposes all app-provided functions.
  8. teamIn() resolves names from a team directory snapshot. JQL functions have no user context, so the app does not call Atlassian APIs while a query runs. Team names are matched against a directory (ids and display names) refreshed hourly, on install or upgrade, and whenever the gadget, team panel or Team reports load teams. A team created or renamed within the last hour may not match until then. Up to ten names per teamIn() call, and at most 1,000 matched teams per call.
  9. Cloud only. Not available for Jira Data Center.

Was this page helpful? Email support@mortiseapps.com.