Metric display editor for Jira and Confluence analytics add-ons

An ops manager using a Jira analytics add-on wants to change how a specific metric is labeled, grouped, or formatted in a report they share with their director every week. They find they can filter and sort, but 'limited customisation available for changes in metrics' means the number on screen doesn't match the definition their company actually uses. They either export to Excel and reformat manually, or they ship a report that prompts a question every single week.

This gap is structural. Jira add-on vendors like Appfire build against Atlassian's data model, and that model is designed for issue tracking, not flexible metric definition. Changing how a metric is computed or displayed requires either a new add-on feature (which the vendor prioritizes against their whole user base) or scripting access that most ops users don't have. The user is not a developer, but the only path to customization assumes they are.

What users actually need is not a new chart type — they need to rename a field label without asking IT, define a custom rollup formula for their team's specific KPI, and save that as a named metric that persists across reports. None of the current Jira-native or Jira-adjacent analytics tools let a non-technical user do that without writing a ScriptRunner expression or filing a request.

This is a business because the Jira ecosystem is large, the ops and delivery manager audience within it is enormous, and their reporting cadence is weekly or biweekly — meaning this problem recurs on a fixed schedule indefinitely. The cost of not having it is a mix of manual Excel work and eroded trust in the numbers being reported.

What to build

Build a Jira Cloud app that lets ops and delivery managers define named custom metrics — including label overrides, field-level rollup formulas using a no-code formula builder, and display format rules — and attach those metric definitions to any existing Jira dashboard gadget or board report without touching ScriptRunner or JQL beyond basic filters.

Where to start

Launch specifically for teams using Jira's built-in 'Control Chart' and 'Velocity Chart' gadgets — both are notoriously rigid in labeling and display, and the user base complaining about them is easy to find in the Atlassian Community forums, giving you a ready-made beta cohort.

The hard part

Atlassian's Marketplace approval process is slow and the Connect/Forge framework limits what you can do with real-time data, so the first version will have latency or data freshness constraints that enterprise buyers will push back on immediately.

How it makes money

Per-site subscription on the Atlassian Marketplace, tiered by Jira user count — follows the standard Marketplace billing model buyers already trust, with a 30-day free trial to lower procurement friction.