Change project
MONTH
MEMBER
JIRA SYNCED STATUS -
AVERAGE CYCLE TIME
- days ↘ --
-

Average work item cycle time

FIRST PASS YIELD %
- % ↗ --
-

First-time merge success rate

MAINTENANCE TAX %
- % ↘ --
-

Effort spent on bug fixes/chores

UTILIZATION %
- % ↗ --
-

Team direct active capacity utilized

CHANGE FAILURE RATE %
- % ↗ --
-

Production deploy failure rate

Team Member Performance Matrix

Summary of sprint and period contributions across tracked delivery, quality, effort, and capacity metrics

Team Member Total Logged Hours Utilization% Waiting for Work% First Pass Yield (FPY) Rework Rate% Avg Cycle Time Active Backlog Capacity
Loading performance matrix data...

EOLE ServiceNow Portal Gateway

Access live incident queues in ServiceNow. The charts and metrics below display delivery performance and logs harvested directly from your ServiceNow instance.

Chandan ServiceNow Queue Piyali ServiceNow Queue
ServiceNow Date Filters:
Start Date:
End Date:

ServiceNow Avg Cycle Time

- Hours

Avg time from CIT.WL.Eole.2ndL assignment to Closed/Resolved (Click to view)

Mean Time to Response (MTTR)

- Hours

Avg time from CIT.WL.Eole.2ndL (Pending) to In Progress (Click to view)

Change Failure Rate (CFR)

- %

Tickets returning from Resolved to Pending assignment (Click to view)

Total ServiceNow Records

- Tickets

Active and resolved tickets tracked for EOLE team (Click to view)

Cycle Time Trend (Days)

Average resolution cycle times by week

Rework Rate Distribution

Rework occurrences count breakdown

EOLE ServiceNow Live Queue & Incident Table

Showing active and completed incidents and change requests mapped to EOLE developers (Chandan Kumar & Piyali Roy)

Record Number Short Description State Assignment Group Assigned To Priority & Risk Rework Loops Last Updated
Loading ServiceNow records...
Showing 0 to 0 of 0 entries
Page 1 of 1

JIRA Ticket Lifecycle & Process Flow

A visual representation of development transitions, defect branching, and failure loops

To Do Sprint Backlog Open Ready for Dev In Progress Active Coding In Review PR & Code Audit Resolved QA Approved Done Merged to Main READY START SUBMIT PASS FO TEAM'S REVIEW 📋 Review Ticket (Assigned to Lead) Team Creates 🐞 Bug Ticket (Assigned to Developer) Defect Found RE-ASSIGN DEV ⚠️ FAILURE SCENARIO: QA REJECTED ⚠️ FAILURE SCENARIO: REOPENED PROCESS REQUIREMENT: Leads create the Ticket with description. Tickets must contain explicit Definition of Ready (DoR).
Planning & Sourcing (To Do / Open)
Active Development (In Progress)
Quality Verification (In Review)
Released / Merged (Resolved / Done)
Failure scenario / Bug rework loops
Interactively hover over card elements to view workflow stages.