Finding Runs on the Dashboard
Use the dashboard filters to get from a long run list to the exact analysis you need, whether it is still active or already finished. Filtering first helps you avoid opening the wrong run when several jobs have similar names or many runs are happening at once.
Prerequisites
- You can sign in and open
Dashboard. - At least one analysis run exists. See Submitting Jenkins Builds and JUnit XML for details.
Quick Example
- Open
Dashboard. - Set
Statustorunning. - Choose a
Team. - If tags are available, click one under
Filter by tag. - Set
FromandToto the day range you care about. - Click the matching run.
Tip: Watch the run count above the table while you filter. Once it drops to a short list, open the run you want.
Step-by-Step
-
Start with the newest runs.
The dashboard shows the most recent runs first and refreshes automatically, so active runs can change status without a manual reload. -
Narrow the list by status.
UseStatusfirst to separate active work from finished or failed runs.
| If you want to find | Set Status to |
|---|---|
| A run still waiting on Jenkins | waiting |
| A run queued for analysis | pending |
| A run currently being analyzed | running |
| A finished report | completed |
| A run that ended with an analysis error | failed |
| An AI analysis timeout | timeout |
Note: Runs labeled
Analysis Timed Outare found with thetimeoutfilter.
- Add metadata filters.
UseTeam,Tier, andVersionto narrow the list by ownership or release. If your runs use tags, click one or more tags underFilter by tagto narrow the list further.
The Clear metadata button removes only the metadata filters, which makes it easy to try a different combination.
-
Limit the date range.
UseFromandToto keep only runs created inside the time window you care about. Use the clear button next to the date fields to remove both dates at once. -
Refine the short list.
Use the search box to narrow by run name. If you still have too many matches, sort byCreated,Failures,Reviewed,Comments, orChildren, and raiseRows per pageto50. -
Open the run you need.
Click the row or the run name. Active runs, failed runs, and timed-out runs open the live status view; completed runs open the full report.
Advanced Usage
- Tag filters use AND logic. If you select two tags, the dashboard shows only runs that have both tags.
FromandToare inclusive. A same-day range keeps runs from the start of that UTC day through the end of that UTC day.- Search is case-insensitive, which is useful after you have already narrowed the list with status or metadata.
Team,Tier,Version, tag, and date filters stay in the page URL. Refreshing keeps them, and you can bookmark or share that filtered view.- The search text and
Statuschoice do not stay in the URL, so they reset on a full reload. - Sort order is remembered for the current browser tab, which helps if you prefer scanning by
CreatedorFailures. - The dashboard shows the 500 most recent runs. If an older run is missing, it may have aged out of the dashboard list.
Warning: Date filtering uses the run's created date in UTC. A run close to midnight can fall on a different day than the local time shown in your browser.
Troubleshooting
- I do not see
Team,Tier,Version, or tag filters: those controls only appear when runs already have metadata values to choose from. - I see
No jobs match your filters: remove filters one at a time, starting with tags or date, then resetStatus, then clear the search text. - I cleared metadata, but the list is still empty:
Clear metadatadoes not remove the date range, search text, orStatusfilter. - A run looks like it should match the date, but it does not: hover over
Createdto check the exact timestamp, then compare it with the UTC date range.