The planned release will not publish this Friday 1/16/26 and is now targeted for next Friday to allow time to resolve remaining bugs and ensure stability. 

Multiple offices are waiting on this release due to high-impact items, including Upload Center and Linked Folders. 

Linked Folders: Confirmed as part of the upcoming release. 

Upload Center: Also referenced as a key component users are waiting on. 

Confirmed Linked Folders is coming in the next release and will be working. 

- Some Investigator module features are coming in the next version. 

- Additional screens/functionality will follow. 

- CIP is using the STAC 3 rollout as an opportunity to improve/refactor complex legacy behavior rather than copying STAC 2 “as-is.” 

While editing relationships and moving between cases, the Relationships tab intermittently loads blank. 

Appears sporadic and more likely during high-volume updating (multiple relationship edits in succession). 

- When it happens, notify CIP right away so they can connect quickly. 

- CIP asked users to capture browser console errors using F12 when the issue occurs (if user is comfortable). 

- Review internal error logs and attempt to reproduce the issue. 

- Some environments (county configuration/security) may limit CIP’s ability to retrieve logs consistently.

- Search results appear not alphabetized; may be listed by Directory ID or screen sort state. 

CIP explanation: Results follow the current screen sort. If the user sorts a column, that becomes the ordering behavior going forward. 

Example described: searching “Mills, A” produced results not consistently aligned to the expected first-name starting letter. 

CIP request: If it happens again, record it (screen recording helps) so CIP can evaluate whether it’s a true bug or a sorting/filtering expectation issue. 

SA15 reported the About STAC screen throws an error when trying to retrieve the current version information. 

- Other offices did not report the same behavior. 

- CIP believes this is likely office-specific (possible service/account blocking), since About STAC checks a service that validates version. 

- Submit a ticket so CIP can connect and troubleshoot in that environment. 

- CIP clarified the philosophy of STAC 3 wizards: 

- STAC 3 keeps a small set of core common fields on the primary wizard page (e.g., arrest/agency-related items). 

- Other office-specific items are handled through the Events step, which is intended to be configurable. 

- STAC 3 extends wizard logic so offices can define required events by case type (instead of one rule set for all cases). 

- This model will apply to multiple workflows/wizards, including: 

Disposition 

Reopen 

File a case 

Sentencing 

Transfer case 

Officer Leave Requests currently cannot be saved without a comment, tied to a configuration/flag interaction. 

Enter any character (even a “.”) in the comment to save. 

CIP confirmed this is expected to be fixed in the next version so the record can be saved without requiring a comment. 

STAC 3 supports user preference for how dropdown searches behave: 

- Code only (matches STAC 2 behavior many users expect) 

- Description only 

- Code + description 

Users can adjust this under Profile / User Preferences to match their preferred behavior. 

Budgeting and storage impact from duplicate files; asked about de-duplication options. 

CIP confirmed STAC 3 files have a hash identifier when: 

- Added through STAC 3 

- Added via Link Parser 

CIP has a standard report: 

- CIP Standard Reports → “Duplicated Images” 

- Helps identify duplicates on a case. 

Files added via STAC 2 / current Upload Center do not have hashes (hashing was implemented for STAC 3). 

CIP redirected feature requests (auto-deduplication, draft hiding) as enhancement conversations to be handled outside the collab call. 

Request: Ability (like STAC 2) for supervisors/admins to toggle Admin Mode and view/manage other users’ notifications. 

Answer: Confirmed is coming, but not in the next release (targeted after RC3 as part of later admin feature rollout). 

Request: Ability to modify event dates/fields in admin capacity and view calendars for coverage when staff are out. 

Answer: Confirmed as coming, may not be implemented the exact same way as STAC 2 but will provide comparable capability. 

Confirmed template numbering/default behavior still differs from STAC 2. 

CIP stated improvements are being discussed for default email template behavior across: 

- Notes page 

- Image share via CIP Portal 

- Email-related workflows 

Demonstrated the Results area sometimes does not refresh correctly when using Enter; it refreshes properly when clicking the Search button. 

Observed as a delay/mismatch between typed value and results displayed. 

CIP confirmed it appears to be a real behavior difference / refresh timing issue and agreed it needs review. 

Noted workflow is fast paced; still acknowledged it should function reliably regardless. 

asked about the Enhancement tab. 

CIP confirmed it will be restored/returned after RC3, in the “final version” workstream. 

Find highlights hits but does not jump to the match; scrolling can behave oddly (appears stuck/reversing). 

Example document was ~33 pages. 

CIP to investigate; Jenn to ticket if needed with details. 

Request for an easy way/shortcut to insert the statute section symbol. 

Tip provided: The Microsoft Word shortcut key for the statute sign (§) is Alt+0167 and seems to also work in STAC 3.  

Printing via Ctrl+P vs in-app Print produces different output (fonts/formatting differ). 

 scan paper examples and submit a ticket. 

In some contexts (notably referenced on the Directory Search), clicking the pencil icon shows “cannot edit related address,” creating confusion. 

Double-click / right-click → Edit works, but pencil icon does not. 

CIP to review pencil behavior and why it differs from other edit paths. 

During New Case Wizard, user adds a directory and gets a prompt that the directory may already exist (SSN/DL/etc.). 

The hyperlink in the warning is intended to let the user open the directory card to verify the match. 

To use the existing record in the case wizard workflow: 

User must cancel the wizard and then search/select the existing directory. 

asked for a right-click option to mark phone numbers “not current” (especially because current phones display in Details). 

CIP cautioned about adding shortcuts/options that increase screen complexity if not widely used. 

CIP clarified “current” is a STAC 3 concept intended to make validity clearer at a glance (and impacts merges/texting workflows). 

Real-world use case validated by Edward and Damon: clients frequently change phone numbers; old numbers remaining “current” causes communication issues. 

The system behavior for “current” handling depends on business rules: 

For addresses: current handling may depend on type. 

For phones: discussion revealed behavior and expectation differences; CIP clarified there is reasoning behind current logic, and the request should focus on long-term workflow need vs one-time cleanup.