Skip to content

Find tickets across funds and assignments

Why tickets can "disappear" that are actually just filtered out

MRC's search panel has two layers of scoping, and both default to narrow. The signed FDD (Common 10.2.5 MRC Search Criteria) documents this landing behavior deliberately: the grid is meant to default to "do I have anything open assigned to me?" rather than showing everything, as a fallback for a dropped email-notification feature. That intent is correct, but it means a lot of "missing ticket" reports are really a filter-scoping question, not a visibility bug.

Default filters hide everything on first landing

Per e2e/crawl/docs/mrc.md, the Status filter defaults to Open and the Assigned To Me checkbox defaults to checked. In UAT, this combination showed "No items to display" / 0 rows for the Super User test account on first landing, even though 76 tickets actually existed. To broaden the search:

  1. Uncheck Assigned To Me (#chkMRCAssignedToMe).
  2. Open the Status multiselect dropdown and click "Select all" rather than leaving it on just "Open."
  3. Click Search — note this module uses its own #btnSearchMRCFilters / #btnClearMRCFilters, not the generic #btnSearchFilters/#btnClearFilters buttons used elsewhere in PRIZM, so a reused search-button selector from another module silently does nothing here.

The top-nav Fund dropdown silently scopes results

Separate from every filter in the search panel, the Fund dropdown in the page header (Union / ETF / H&W — the same control used to switch fund context everywhere in PRIZM) determines which tickets MRC shows at all. A ticket generated for the H&W fund will not appear while this dropdown is set to Union, even with every in-panel filter broadened — Assigned To Me unchecked, Status set to all, Member name searched directly — the search simply returns 0 rows with no message explaining why.

Things to watch out for

The Fund dropdown, not the trigger, is often the real reason a ticket 'isn't there yet'

During IUOE-2748 UAT validation, this cost roughly 15 minutes of false "nothing created yet" checks on a terminated-work-record trigger before the actual cause turned out to be the Fund context being set to Union while the generated ticket lived under H&W — not a broken trigger. Switch the Fund dropdown to match the ticket you're expecting (e.g. H&W) before concluding a search came up empty for a real reason. (IUOE-2748)

An empty Assigned dropdown is data-driven, not broken

The Assigned-to dropdown's available options are driven off currently-open tickets under the active filter — if "Assigned To Me" is checked and nobody else has open tickets visible under that scope, the dropdown can look empty. Deselecting "Assigned to me" revealed the expected options in a confirmed case. (IUOE-2200)

A visibility report can trace to a UAT environment reset rather than a code bug

One "can't see another user's tickets" report traced to a UAT environment data reset (a February wipe) rather than any targeted defect — the tickets reappeared once the environment had live data again, with no code fix involved. Rule out a recent environment/data reset before escalating a visibility complaint as a bug. (IUOE-2102)

Check the Fund dropdown and Assigned-to-me checkbox first, in that order

These two settings are the most common reasons an MRC ticket "disappears" that staff actually file as bugs. Check both — and rule out a recent environment/data reset — before escalating a new "I can't find this ticket" report.

See Log and track an MRC ticket for the Assignment History grid referenced above, and Understand MRC triggers and pre-population for why a trigger-generated ticket might take longer to appear than expected even once you're searching the right Fund.

Who can do this

Role Access
Super User Add/Update
Business Agent Add/Update
Management Add/Update
Membership Staff Add/Update
Accounting Add/Update
Contract Add/Update
H&W Staff Add/Update
ETF Staff Add/Update

All 8 roles have identical Add/Update access to MRC tickets, and the search/filter screen itself has no role-based restriction either. Anyone who needs to confirm whether a ticket already exists, check on something assigned to them, or audit activity across a fund needs to search MRC — and everyone hits the same filter-scoping gotchas described below, regardless of role.

Screen: Sidebar > MRC (Landing / ticket-search screen)