Pulse
Engineering intelligence
Live data
Data sources
J
JiraChecking status…
GitHubChecking status…
C
ConfluenceChecking status…
PROJECT INTELLIGENCE

Delivery by project

Move from portfolio context into the performance of a specific sprint.

1
2
3
Start: — · End: —

Choose a project

Sprint performance will appear here.

0Contributors
0Sprints tracked
Contributor Activity
Tickets done by team member and authored pull requests
Committed vs Deployed or Done
Team commitment at sprint start compared with tickets in Deployed or Done at sprint end
Sprint roll-over
Committed tickets not Deployed or Done by the end of each sprint
Metric mix
Distribution of delivery activity
Sprint roster
Contributors represented in this data source
0 people
DeveloperSourceTickets donePull requestsMerge time
Jira ticket verification
Live evidence from Jira for the selected sprint—not a stored copy
Load the source tickets when you want to verify the aggregated metrics.
1
2
3
Start: — · End: —
0hLogged in Jira
Activity timeline
Jira and GitHub contribution over time
Current activity profile
Metrics for the selected source, project, and sprint
Developer’s Jira tickets
Live tickets assigned to this developer in the selected sprint
Select a project and sprint, then load Jira evidence.
C
Confluence contributions
No page configured
Ready to configure
Pages updated
Comments
Spaces contributed
Last activity
Connect a specific Confluence page

Once configured, this area will show the developer’s version history, comments, and recent contribution timeline for that page.

Admin managed
i How are these metrics calculated?Open the metric glossary and measurement rules View definitions

Metrics describe delivery activity and workflow signals. They should be interpreted with project context and not used as a standalone performance ranking.