Smart Metrics AI — Documentation

This guide explains how to install, configure, and use Smart Metrics AI on Atlassian Jira Cloud. The app is built on Atlassian Forge — all issue data stays inside your tenant.

Overview

Smart Metrics AI transforms Jira issue history into engineering intelligence: Lead Time, Cycle Time, Throughput, Friction Index, Monte Carlo forecasts, Value Stream Mapping (VSM), Active Sprint Health, and an optional Rovo Coach.

The app caches issue data in Forge Entity Storage scoped to your site. Metrics are calculated from that cache, which keeps dashboards fast and avoids live-fetch limitations.

Product page: smartflowstudio.com.br/apps/smart-metrics
Install on Marketplace: Smart Metrics AI listing

Requirements

• Jira Cloud (any plan). Data Center and self-hosted Jira are not supported (Forge is Cloud-only).
• A Jira user with permission to install Marketplace apps (typically a site administrator).
• A Jira user with Jira Admin access to open the Configuration screen and add projects.
• At least one Jira project with issues and a defined workflow (statuses such as To Do, In Progress, Done).

Installation

1. Open the Atlassian Marketplace and search for Smart Metrics AI (vendor: SmartFlow Studio).
2. Click Get it now (or Try it free on paid tiers).
3. Select your Jira Cloud site and confirm installation.
4. Review and accept the requested app permissions (see Permissions below).
5. After installation completes, open Jira and go to Apps → Smart Metrics AI from the top navigation (or the Apps menu, depending on your Jira layout).

Trial: paid plans include a 30-day full-featured trial managed by the Atlassian Marketplace. Teams with 1–10 Jira users on the site can use the app free forever on the free tier.

First-time configuration

Configuration is required before metrics appear for a project. Only Jira Admins can access this screen.

1. From the Smart Metrics AI dashboard, click the gear icon (top right) → Configuration,
   or navigate to Apps → Smart Metrics AI → Configuration.
2. Click Add project and select a Jira project from the dropdown.
3. Map workflow statuses:
   • Done statuses — statuses that mean work is complete (e.g. Done, Closed, Resolved). At least one is required.
   • Active statuses — statuses that mean work is in progress (e.g. In Progress, Doing, In Review). Optional but recommended for accurate Cycle Time.
4. Choose a Cycle Time strategy:
   • Total Span (default) — from the first entry into an active status until the last Done transition. Best for end-to-end delivery predictability.
   • Accumulated — sums only time spent in active statuses. Best for measuring pure engineering effort.
5. (Optional) Under Team management, add team members and mark who counts toward Story Points per Dev capacity.
6. Click Save.

After saving, the app starts a bootstrap sync in the background. The Configuration list shows a syncing status, then an issue count when the first batch completes.

Status mapping tips

• Map every status that should count as “finished” under Done. Unmapped Done-like statuses are ignored and can skew Lead Time.
• If your workflow uses a single “In Progress” column on the board, map that status under Active.
• You can re-open Configuration later to adjust mappings after workflow changes.

VSM phase layout (optional)

For the Value Stream Map tab, open VSM Editor from the app navigation. Drag Jira statuses into flow phases (e.g. Discovery → Build → Validate → Deliver), set SLA targets, and save. The VSM Health Matrix uses this layout per project.

Sync behavior

First dashboard load: KPI cards may show a “syncing initial data” state for up to ~60 seconds on smaller projects. Larger projects sync in chunks; refresh once if numbers are still empty.

Force full synchronization: on the Configuration page, click the Sync icon next to a project. Confirm in the dialog. Full sync can take 1–2 minutes and re-processes issue history sequentially.

Using the app

After configuration and sync, open Apps → Smart Metrics AI and select your project (or use the project picker).

Use the filter panel (left) to narrow by sprint, issue type, label, or date range. Filter presets can be saved for recurring reviews.

Rovo Coach (optional, paid)

Open the Rovo panel in Jira and select Coach Smart Metrics AI. The coach uses aggregated metric values only when you explicitly ask — not raw issue text. Requires a paid Marketplace license.

Demo project

The app includes DEMO-PROJECT with sample data so you can explore all workspaces before configuring a real project.

Permissions

Smart Metrics AI requests the minimum Forge scopes needed to read Jira work items and store configuration:

The app does not create, update, or delete Jira issues. It does not call external servers outside the Atlassian platform for core metrics.

Licensing

Some features are limited on the free tier (e.g. number of configured projects, VSM phases, Executive Report slides, Rovo Coach). DEMO-PROJECT always shows full premium behavior for exploration.

Billing, trials, and upgrades are managed entirely through the Atlassian Marketplace — not through SmartFlow Studio directly.

Troubleshooting

For bugs and feature requests, open a public issue:
github.com/smartmetricssupport/smart-metrics-ai-legal/issues

Support

• Email: support@smartflowstudio.com.br (reply within 2 business days; critical incidents within 24 hours)
• Contact form: smartflowstudio.com.br/contact
• GitHub issues: smartmetricssupport/smart-metrics-ai-legal

Uninstall and data deletion

• Delete one project: Configuration → Delete project on the project row. This removes cached issues and settings for that project only. Jira issues are not modified.
• Uninstall the app: Jira Settings → Apps → Manage apps → Smart Metrics AI → Uninstall. Atlassian automatically deletes all Forge storage for the app on your site.

Related documents

• Privacy Policy
• Terms of Service
• Security & vulnerability disclosure

Smart Metrics AI is an independent product and is not affiliated with or endorsed by Atlassian Pty Ltd.