| ID | Category | Released in | Score | Why this score | Status | Assignee |
|---|
Scoring weights — how the score is calculated
Each signal contributes up to the points below, out of 100. Points are log-scaled from the underlying measure, so an order of magnitude is one visible step. Every weight is a judgement about priorities; what each signal is derived from is not adjustable.
Client profile & discovery tickets
What this client's business is, and what they are working on now. Both weight the tracker by meaning rather than keyword — a note about the bug in a discovery ticket surfaces even when it shares no words with it.
Test plan & LLM triage
Fetching needs JIRA_BASE_URL, JIRA_EMAIL and
JIRA_API_TOKEN in the server's environment. Without them, paste the
ticket below — the analysis is identical, it just cannot read the ticket for you.
Fields are recognised only where the index confirms them, and the ticket key fills
update_zephyr_integration.jiraId in the payloads.
Paste the ticket text instead
Fields this ticket names
| Field | Matched on | How | Stmts | Crit | Why this table |
|---|
Three ways into the same index: one field, one configuration, or the whole enterprise ranked. Open the one you need — the others stay out of the way.
Impact of changing a field
Start typing to filter. Column entries show total statements and, in brackets, the ones using the column in a WHERE or JOIN.
Configuration
A configuration is anything that reads or writes columns: a feed, stored query, workflow rule or resultset. Kind narrows the list; typing filters it.
Critical data points
Derive tests for these columns builds one plan for
every column in the ranking above — identical tests arising from several columns are
merged, so the result stays reviewable. It costs one impact analysis per column and
the cost is uneven — user-defined fields take under a second each, heavily-referenced
keys about five, so the top 25 overall can take a minute. Capped at 25 columns.
Ranks blast radius across every table, not likelihood of change.
Keys top the list because everything references them; leave UDF columns only
unticked and the report includes a user-defined-field section as well.
Everything below is generated on opening this tab: the order workflow by security type, the top 10 user-defined fields by blast radius with a test plan derived from each, and a placeholder per deployed add-in. Detail is collapsed — click a test to open it, or jump to one from the index.
Order workflow coverage
Loading order volume…
Change the coverage and press Re-run to derive the workflow cases again.
By table and column
Pick a table and a column for a test plan. Pick a table
on its own for the value vocabulary of the whole table:
every column an indexed configuration compares against a literal, and the values it
is held to — the de-facto code list, read from the SQL rather than from
documentation. The UDF box narrows it. Both download as .md.
Nothing is
created in Zephyr or XLR8. Download payloads .json gives the
exact create_zephyr_test_case → create_test → create_assertion →
update_zephyr_integration chain, for review before anything is created.
Run from the search box at the top right.
Plain words use the full-text index. Anything with punctuation is matched literally against the SQL.
Loading metrics...
The 20 columns with the widest blast radius in each half of the schema. Ranks blast radius, not likelihood of change — keys top the vendor list because everything references them, while user-defined fields are the ones the business actually redefines. Click any row for its full impact analysis.