Log and track an MRC ticket¶
What creating a ticket involves¶
Per the signed FDD (Common 10.1.2 MRC Workflow), a new ticket starts from the Add MRC Ticket Detail button in the lower right of the Landing screen. The dialog initially shows only the Issue Category Group dropdown — there's no default, you must choose one. Picking a Group swaps in a data-entry pop-up with the fields and Issue Category list appropriate to that Group. The five Category Groups are:
- General Member Information
- New Person Record
- Existing Member Work and Union
- Member Life Events
- Employer/Jobsite/Contract
Required fields are marked in red and vary by Category, but Category and Assign To are required across every Group. A ticket must be assigned to at least one assignee (a specific PRIZM user, a Security Role, or a Fund Group) and can have multiple assignees. Assignment and Assignment Due Date communicate what the originator wants the assignee to actually do and by when.
Upon Submit: PRIZM assigns the next sequential ticket number, saves the ticket in Open status, and writes the first Action History record (creation date + creating user). If the user entering the ticket is a Business Agent, an additional Action History record is added automatically showing BA approval — the BA is assumed to have already acted on what they're reporting.
Add New Call is the companion action referenced in the matrix alongside Add New Ticket — treat it the same way: both are intake paths into the same ticket record, gated by the same Add/Update permission for all 8 roles.
The Assignment History grid and Add New Assignment¶
Once a ticket exists, its detail screen (per e2e/crawl/docs/mrc.md) shows an Assignment
History grid — Date Added, Assigned By, Assignment, Assigned To, Due Date, Action, Notes,
Completion Date — and, below it, an Add New Assignment form with three required (red-label)
fields:
- Assignment (required)
- Assign To (required dropdown)
- Assignment Due Date (required)
- "Add New Assignment" button to submit
Every action taken on a ticket — Approve, Reject, Reassign, Assign to Additional User, Dismiss, Require More Information, Assignment Completed — writes a new row to this grid per the FDD's "General Ticket Action Rules." Only the assigned user (or someone in the assigned Security Role or Fund Group) can edit their own assignment line; an unassigned viewer can see the ticket but not act on it.
Ticket lifecycle¶
- A ticket stays Open as long as at least one assignment lacks a Completion Date.
- When the last open assignment is completed, PRIZM automatically flips the ticket to Closed.
- Closed tickets can no longer be edited.
- Editing fields or taking an action on a ticket never writes back to the underlying PRIZM member/employer/jobsite/contract record — MRC is a notification and workflow layer only, by design (FDD Common 10.1.2, repeated verbatim in FDD Common 10.1.3). If the actual member, employer, jobsite, or contract record needs to change, that still has to happen in its own module.
See Understand MRC triggers and pre-population for how a ticket can also be created automatically instead of through this manual Add New Ticket flow.
Things to watch out for¶
This screen loads in two waves
The Ticket detail screen settles its main form, then loads a second async widget shortly after — a single "wait for idle" check can catch it mid-"Loading.." state. If the screen looks incomplete right after opening a ticket, give it a second settle before concluding a field is missing.
There is no in-place edit for a wrong ticket
MRC tickets are immutable by design once created — the original intake fields are permanently locked for audit-trail purposes, confirmed as expected behavior rather than a bug. The two supported correction paths are: add a new Assignment noting the correction, or close the ticket and recreate it if it's wholly wrong. "Edit" will never be added as a feature. (IUOE-2103)
A creator can delete their own ticket, but may need a hard refresh first
Creator-initiated ticket deletion shipped in Prizm 2.21. The first reported failure to see the Delete control traced to a stale client cache, not a missing feature — a hard refresh (Ctrl+F5) resolved it. A minor cosmetic issue (the Delete button being cut off in the UI) was explicitly accepted as non-blocking rather than fixed. (IUOE-2612)
A reassignment reliably updates who's responsible, but check Assignment History for the full picture
The single-name "Assigned To" column on the search-results grid doesn't necessarily reflect every assignee once a ticket has bounced between multiple people or departments — that's confirmed as likely-expected behavior, not a bug. Open the ticket's own Assignment History for the authoritative multi-assignee state rather than trusting the grid column alone, especially on a ticket that's been reassigned more than once. (IUOE-2164)
Dialog cut off or won't scroll? Check menu position and OS text size first
Two separate reports of the Add/Edit ticket dialog being cut off or unscrollable both traced to settings outside MRC itself, not an MRC-specific layout bug: the app's menu position (switching the default from top to left freed enough vertical space to fix one case) and a user's own OS/browser display text-size setting (which caused a related scroll/spacing issue in another case). Check both before filing a new "MRC dialog is broken" ticket. (IUOE-2162, IUOE-2593)
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 |
Every one of the 8 PRIZM roles has Add/Update on Ticket, Add New Ticket, and Add New Call — this is one of the only modules in the system with zero role-based restriction. Whoever learns of a change — a member's status, a new hire, an employer or contract update — can open MRC and log it themselves rather than waiting on someone else's permissions.
Screen: Sidebar > MRC (Landing/search screen, plus a Ticket detail screen reached by opening an existing row)