Software Engineering - Dashboard
📊
No data yet

Connect to JIRA in the Settings tab, then select a Space, Customer, and Project to load quality metrics.

⭐ Favorites

📅 Key Dates ▼
Project Status Notes
User Story/Feature Progress — ▼
Completion
Load a project to see data.
Test Status — ▼
Loading…
Issues
# Issue Key Type Priority Summary Assignee Status Sprint Created Original Est. Actual Variance Updated Children
Test Runs
Run Name Total Passed Failed Blocked Untested Retest Pass %
Load a project with a TestRail_ID to see runs.
Test Cases
Status Title Assignee Run
Load a project with a TestRail_ID to see test cases.
Customer Reported —
Monthly Trend — Issue Type
Customer Reported Issues by Product
Customer Reported Issues
Key Type Priority Summary Assignee Product Status Created Updated
Select a date range, then click Load.
Total Cases —
Open Cases —
Assignees Involved —
Monthly Trend — Issue Type
Engineering Cases by Product
Engineering Cases
Key Type Priority Summary Assignee Product Status Created Updated
Select a project and date range, then click Load.
Breakdown by Type
Monthly Trend
Tickets by Status
RCA/EDA Items
Key Type Priority Summary Assignee Product Status Created Updated
Click Load to fetch MCA project RCA/EDA items.
Total Tests —
Passed —
Failed —
Blocked —
Untested —
Retest —
Test Runs in Plan
Run Name Total Passed Failed Blocked Untested Retest Pass %
Enter a Test Plan ID and click Load.
Test Cases
Status Title Assignee Run
Load a plan or run to see test cases.
Total Tickets (incl. sub-tasks) —
Est. Coverage (excl. sub-tasks) —
Time Logged Coverage (excl. sub-tasks) —
Sprint Progress
By Tickets
Completed Tickets %
—
By Effort
— —
Sprint Progress by Type
Burndown — Remaining Effort (Time Tracking)
Sprint Issues
# KeySummaryType PriorityAssigneeStatus Original EstimateTime Tracking (Actual)Variance
Select a board to load sprint issues.
Click Load Dashboard to aggregate Sprint Conformity & Release Quality across all teams.
Team Roster

One lead per line, format Name: email. Saved in this browser.

Click Load Team KPIs to fetch released-epic metrics for each team lead.
🔌 Connection Status
JIRA: Not connected TestRail: Not connected
🔑 JIRA Login
How to connect — takes about a minute
  1. Domain — the part before .atlassian.net in your JIRA URL. Example: for acme.atlassian.net enter acme.
  2. Email — the email you use to sign in to JIRA.
  3. API Token — create one at id.atlassian.com → API tokens, click Create API token, copy it, and paste it below. (Use a token, not your password.)
  4. Click Connect. Your token is stored locally on this machine only.
🧩 TestRail Login (optional — only for the Test Rail tab)
How to connect
Enter your TestRail Server URL up to (but not including) /index.php. For example, if your browser shows http://hostname/testrail/index.php?/plans/view/123, enter http://hostname/testrail. Sign in with your TestRail email and password.
⚙️ Advanced (optional — defaults usually work)

These map JIRA custom fields to the dashboard. The defaults work for most instances — only change a value if the related chart shows blank or zero. Click Auto-detect to find the right field ID automatically.

Defaults to customfield_10016. Use if story points show as 0.

For the "Issues Found in Rev & Build" chart (Software Revision & Build).

For the "Products" field on Open Epics cards.

For the Sprint column in the drill-down table (type gh-sprint).

Customer Reported Issues queries tickets where "Phase Found" is one of: Production, Post-Release, Customer Product Approval, UAT, Customer System Integration. This uses the JIRA field name directly — no configuration needed.

Loading…