A Jira-native dashboard that gives engineering managers a single view across Jira and GitHub — surfacing what needs attention, not just what happened.
See what's insideLives inside your Jira project. No separate login, no third-party hosting — it's a Forge app, so it runs natively within Atlassian's platform.
Stale PRs and stuck In Progress issues, surfaced with configurable thresholds. Know what's blocking your team before the standup.
A chronological stream of Jira events with a per-person summary strip and filter. See who's been active and on what, at a glance.
Combined bar charts of Jira events and GitHub PRs/commits per person over the last 7 days, with per-user issue tables and linked PRs.
Commits and pull requests from your tracked repos, with Jira keys automatically extracted and hyperlinked back to tickets.
One row per Jira ticket found in GitHub activity — live status, linked PRs, and assignee. Instantly see which work has code behind it.
Daily snapshots of team velocity stored in Forge SQL — open issues, PRs merged, commits, and stale items — charted over time.
Deploy to your Atlassian site using the Forge CLI. No separate infrastructure — the app runs natively inside Jira's platform.
Paste a GitHub PAT in the settings page, select the repos to track, and map git author emails to Jira accounts. Done in minutes.
Activity Tracker appears as a Jira project page. Jira events start flowing in immediately via webhooks; GitHub data pulls on demand.
A daily scheduled snapshot captures team metrics into Forge SQL. Trends become meaningful after a week or two of data.
No servers to run, no hosting to manage. Activity Tracker uses Atlassian's native Forge platform for compute, storage, and webhooks.
Runs natively inside Jira with no iframe overhead. Looks like Jira, because it is Jira.
Activity events in a KVS ring buffer; daily metric snapshots in a Forge MySQL table for trend queries.
Issue created, updated, and comment events are captured in real time — no polling required.
Pulls commits and PRs from selected repos. Author attribution is keyed on git commit email, not login, so it works with shared accounts.
A daily Forge trigger upserts one row of team metrics into the SQL table, building up a queryable history over time.
Everything runs inside the Forge sandbox. GitHub data is fetched at request time and stored in Forge-managed infrastructure only.
We deploy and configure it for you, or hand over the source for your team to own. Get in touch to discuss what fits.
Contact us