Overview
PulseView is a Jira Cloud app that analyzes your team's Jira activity and presents it as structured delivery insights. It reads issue transitions, sprint data, business value scores, and workflow patterns — then surfaces metrics like cycle time, throughput, bottleneck location, delivery health, and performance trends.
PulseView is organized into six main views, each designed for a different aspect of delivery understanding:
- Dashboard — High-level team performance and key metrics at a glance
- Team — Team-level delivery analysis: issues, business value, and flow metrics
- People — Individual member rankings, contributions, and performance patterns
- Work — Complete issue history with breakdowns by type, priority, and contributor
- Trends — Weekly performance trends and progress tracking over time
- Reports — Structured analytical reports generated from your team data
Getting Started
PulseView installs from Atlassian Marketplace and connects to your Jira Cloud instance.
Installation
- Go to Atlassian Marketplace and search for PulseView
- Click "Try it free" to begin installation
- Authorize PulseView to access your Jira Cloud instance
- Once installed, PulseView appears as an app in your Jira navigation
First use
After installation, open PulseView and select a project. The app begins by selecting your team — you'll see filters for Metrics, Members, and Spaces at the top. Choose your date range and team scope. The dashboard loads automatically with your team's key metrics.
Dashboard
The Dashboard is your high-level entry point. It shows team performance at a glance through key metric cards and manager alerts.
Key metrics
Manager Alerts
The dashboard surfaces automated alerts when something needs attention — a team member's metrics have changed significantly, delivery health needs review, or anomalies are detected.
Team View
The Team tab provides team-level analysis with performance trends and patterns. It shows key performance indicators and automated insight cards.
Issues panel
Total issues resolved and delivery rate per week and per member. Shows completed count, weekly rate, per-member totals, and per-member weekly averages.
Business Value panel
Strategic impact delivered — total and weekly averages. Breaks down into completed total, weekly rate, per-member total, and per-member weekly rate. This helps you understand not just volume but the value weight of what's being delivered.
Flow Metrics panel
How fast work flows from creation to resolution. Includes:
- Lead Time — Total time from issue creation to resolution
- Cycle Time — Time from when work actively starts to when it's done
Performance Index breakdown
Below the metrics, you'll find the Performance Index breakdown showing the weighting between Business Value and Task Count contributions.
People View
The People tab provides individual analysis — member rankings and contributions. This is where you understand how work is distributed across your team.
Team insights
PulseView generates automated analysis of your team's performance patterns. Examples:
- Excellent Delivery Consistency — Team delivery is highly consistent, velocity stable
- Great Week — Team delivered significantly above average this period
- Scoring Anomaly — Unusually high BV scores detected that may indicate inconsistent scoring
People insights
Individual performance signals and team health indicators, including:
- Top Performer Concentration — Whether output is distributed or concentrated in a few members
- Participation Health — Activity ratio across team members
- Velocity Spread — Gap between fastest and slowest delivery speeds
- Value Distribution — How business value delivery is spread across the team
- Team Growth Signal — Whether team output is growing or declining over time
Member Ranking
Members ranked by Performance Index. The table shows PI score, Velocity, Value, Cycle Time, Consistency, and Participation for each member. Click any member to see their detailed profile.
Member detail view
Clicking a member opens their individual profile with:
- Personal metric cards (PI, Velocity, Business Value, Consistency, Cycle Time)
- Forecast Contribution percentage
- Automated member insights (e.g., "High Business Value Contributor", "Reliable Contributor", "Delivery Streak")
- Planning Signals comparing their patterns to the team
Planning Signals
Planning Signals show personal delivery patterns and how they compare to the team. Displayed at both team and individual levels:
- Velocity Trajectory — Is output growing, stable, or declining?
- Delivery Health — Composite score across throughput, consistency, and workload balance
- Weekly Delivery Target — Team-wide weekly delivery target
- Value Delivery — Is business value output growing?
- Delivery Predictability — Consistency score out of 100
Work View
The Work tab is the detailed view — complete issue history with breakdowns. It gives you the raw data behind the metrics.
Issue breakdowns
- Issue Types — Distribution across Task, Bug, Story
- Priorities — Distribution across Medium, High, Low, Highest
- Contributors — Who completed the most issues in the period
What changed?
Intra-range progress — comparing the first and last periods within your selected date range. Shows throughput and business value changes with percentage differences (e.g., "+37 (+925%)" throughput improvement).
Accumulated Issues & Issue detail list
Cumulative issue completion over time with 4-week average trendlines. Plus a full issue list with Key, Summary, Assignee, Resolved date, Type, Business Value, Lead Time, Cycle Time, and Priority — filterable and searchable.
Cycle Time Distribution
Histogram showing how cycle times are distributed across your issues. Displays P50 (median) and P85 percentiles. This helps you understand your typical delivery speed and identify outliers.
Trends
The Trends tab shows weekly performance and delivery metrics over time. It provides the velocity view with progress tracking.
Summary cards
Progress
Shows how key metrics evolved across the selected date range. Highlights whether all tracked metrics are trending upward ("strong momentum") or if some need attention. Includes period-over-period comparisons for Throughput and Business Value.
Performance trends charts
Individual member performance trends shown as line charts with Issues and Business Value tabs. Tracks each member's accumulated delivery over time against the team average. Available in Weekly, 4-Week Avg, 13-Week Avg, and Monthly views.
Output by member
Horizontal bar charts comparing individual output. Shows both Issues and Business Value side by side with team max and average reference lines.
Performance distribution
Team Health Snapshot showing how many members are Healthy, Need Attention, or At Risk. The performance distribution chart visualizes the spread across the team.
Reports
The Reports tab generates structured analytical reports from your team data and current filters. These are not static templates — they analyze your actual delivery data and produce contextual findings.
Available reports
- Delivery Insights — Delivery analysis with velocity trends, risk detection, and recommendations
- Retrospective Digest — Automated retrospective summaries highlighting wins, challenges, and improvement areas
- Team Health Check — Aggregated team health overview with member-level signals, risk indicators, and recommendations
- Member Spotlight — Deep per-member analysis with personalized insights, planning signals, and performance recommendations
- Workload Analyzer — Time allocation analysis showing workload distribution, overload detection, and balance recommendations
Each report shows the date range, number of team members, and metrics analyzed. Click "Generate" to create the report from your current data.
Core Metrics
Performance Index (PI)
A composite score from 0–100 that combines velocity, business value delivery, consistency, and cycle time into a single readability signal. The weighting between Business Value and Task Count is shown in the Performance Index breakdown on the Dashboard.
Velocity
Issues completed per week. Shown as a rate (issues/week) and as a total count. Useful for understanding capacity and tracking whether output is stable, growing, or declining.
Business Value
Strategic impact delivered — measured through value points assigned to Jira issues. Shown as total value, weekly average, per-member total, and per-member weekly rate. Higher business value doesn't necessarily mean more issues — it means higher-impact work.
Cycle Time
Time from when work actively starts to when it's marked done. Displayed as a single value (e.g., "4.5 days") per member or team. The Work view also shows a full Cycle Time Distribution histogram with P50 and P85 percentiles.
Lead Time
Total time from issue creation to resolution. Lead Time is always equal to or longer than Cycle Time, because it includes time the issue sits before work begins.
Consistency
How predictable your delivery is, scored 0–100. A Consistency score of 100 means delivery volume is very stable week-over-week. Lower scores indicate high variability — some weeks you deliver a lot, other weeks very little.
BV Health
Business Value Health — combining coverage percentage and outlier rate. A "Healthy" BV Health with 100% coverage and low outlier rate means value scoring is being applied consistently across issues.
BV Score Consistency
Shows the average BV, standard deviation, and coefficient of variation across teams and members. Helps identify if business value scoring is applied consistently or if some teams/members have scoring anomalies.
Best Practices
Review weekly, not daily
Delivery metrics are noisy at the daily level. Review PulseView once a week or once per sprint. Look at 4+ week trends, not single-week numbers.
Use insights as conversation starters
When PulseView flags something — a velocity drop, a consistency issue, a bottleneck — treat it as a question to explore, not a verdict. Ask "why" before acting.
Don't use metrics for individual performance reviews
Performance Index and velocity are team delivery signals. Using them to rank individuals in HR reviews will destroy trust and produce gaming behavior. Use them for team planning and delivery improvement.
Compare teams to their own baselines
Different teams work on different types of work. A platform team's cycle time will look different from a product team's. Compare each team to its own history, not to other teams.
Context matters
A throughput drop during a holiday week, a team offsite, or a major refactoring sprint is expected. Always consider external factors before drawing conclusions from the data.
Keep your Jira data clean
PulseView is only as good as your Jira data. Move issues through workflow stages consistently. Assign business value scores. Close resolved issues. The better your Jira hygiene, the more accurate PulseView's insights.
FAQ
Who should use PulseView?
Engineering managers, team leads, and CTOs who need delivery visibility beyond what Jira's built-in reports provide. If you manage software delivery and use Jira Cloud, PulseView is for you.
Does PulseView replace Jira reports?
No. Jira's reports serve a different purpose (sprint backlogs, velocity charts, ticket-level tracking). PulseView adds a delivery intelligence layer focused on patterns, trends, and management-level insights.
Is PulseView a chart builder?
No. PulseView provides structured delivery insights that are already designed around engineering management needs. You don't configure reports from scratch — the views are pre-built and data-driven.
How is the Performance Index calculated?
The Performance Index is a composite score (0–100) that combines velocity, business value delivery, consistency, and cycle time. The weighting between Business Value and Task Count is shown in the Dashboard breakdown.
What is Business Value?
Business Value is a score assigned to Jira issues that represents strategic impact. PulseView reads these values and aggregates them into delivery metrics. If your team doesn't use BV scoring in Jira, those metrics will be empty or less meaningful.
Can PulseView identify bottlenecks automatically?
Yes. PulseView measures time-in-status across workflow stages and highlights where issues spend disproportionately more time. The Flow Metrics panel and Cycle Time Distribution help you pinpoint where work stalls.
Limitations
- Output quality depends on Jira data quality. If your team doesn't move issues through workflow stages consistently, or doesn't assign business value scores, PulseView's metrics will be incomplete or unreliable.
- PulseView is read-only. You cannot create, assign, or modify Jira issues from PulseView.
- PulseView is not an employee evaluation system. It does not produce HR-compatible performance reviews. Do not use it for that purpose.
- Jira Cloud only. Jira Data Center and Jira Server are not currently supported. TODO: clarify DC/Server plans
- Time tracking data requires enabling the Time Spent metric. As noted in the Reports tab: "Time tracking data is not available. Enable the Time Spent metric to use this tool."
- Data refresh interval. Metrics update based on Jira Cloud API availability. There may be a short delay between issue changes and metric updates. TODO: clarify refresh interval