JAMMS Project Dashboard

Last refreshed: September 11, 2026  |  Orases Internal

Active Releases

Pending reply: Ragha's Sept 4 email correcting JAMMS-680 classification still needs a response. She also asked whether JAMMS-682 (mobile crash) can be included in the next release.
3.19

Pearl Special  UAT

Desktop QA complete. Mobile QA passed after prod data copy to beta. Now in client UAT with Ragha's team.

Target production: Sept 17, 2026  ·  UAT deadline: Sept 14
3.20

Coordinates + Attachments  Pending QA

4 tickets in scope: JAMMS-680 (WO coordinates), JAMMS-690 (facility WO map), JAMMS-691 (DWR cleanup), JAMMS-681 (mobile attachments). Brent on PTO next week.

Target deploy: Sept 12, 2026

Known Issues

JAMMS-682
Draft
Mobile app crash on DWR creation (Project 53, TxDOT Austin IH35)
Root cause unconfirmed. Knox device logs received from Scott Smith (Sept 10). Under active investigation by Ben/Hyun. Do NOT tell client root cause is confirmed.
JAMMS-678
Open
Assets not appearing in WO search on mobile
Confirmed still broken as of Sept 1 (Ben). Not in 3.20 scope.

Active Tickets (v3.20)

1
In Progress
2
Pending QA
1
UAT (3.19)
Sept 17
3.19 Prod Target
v3.20 — In Progress
JAMMS-691
Align DWR editable_pointpair check with JAMMS-680 fix
Brent Decker  ·  Updated Sept 11
In Progress
v3.20 — Pending QA
JAMMS-681
Mobile attachment uploads fail silently (204 prod failures)
Ben Matray  ·  High priority
Pending QA
JAMMS-616
Internal error when creating Work Order on Beta
Ben Matray  ·  Updated Sept 7
Pending QA
Not in this release
JAMMS-682
Mobile app crash (DWR creation, Project 53)
Root cause unconfirmed  ·  Knox logs under review
Draft

Recent Activity

Email
📧
Knox Device Logs received from Scott Smith (RJA IT)
Hyun added Ragha + Scott to thread, removed Marc. Knox diagnostics for Trent Struck and Angel Soto attached. Crash investigation (JAMMS-682) active.
Sept 10
📧
JAMMS Artifact Review — accepted for Sept 16, 9:30-10am
Invited by Hyun. Tom accepted.
Sept 10
📧
Action needed: Ragha's reply to JAMMS P1 API Release Update
"JAMMS-680 was NOT API feedback. It was break fix of the GPS coordinates discrepancy in WO module. Timelines sound good, but can we also include the mobile app crash issue reported a couple weeks ago?" — No reply sent yet.
Sept 4
📧
Monica Olaya: "Please provide a testing script"
Reply to the JAMMS P1 API Release Update thread. No response sent.
Sept 8
Slack (#proj-jamms)
💬
Hyun: 3.19 UAT deadline Sept 14, prod target Sept 17 — Brent confirmed no objections
681 may require a new mobile build.
Sept 10
💬
Ben: JAMMS-677 (typeahead) fixed; JAMMS-678 (assets in WO search) still broken
Confirmed in #proj-jamms Sept 1.
Sept 1
💬
Brent: prod DB copied to beta — API keys need to be recreated after copy
Production data now on beta for 3.19 mobile testing.
Aug 31

Recent Commits (beta)

3c23592
Gate ApiServices nav on is_superuser instead of is_immutable
beta
1f7879a
Allow Scalar docs bundle in CSP (fixes blank /admin/api_services/docs)
beta
5ab8916
Merge branch 'main' into beta
beta
71e5df6
JAMMS-667 add SecurityHeadersMiddleware for CSP and required HTTP response headers
beta
7ba44fa
Merge branch 'api-v1' into beta
beta
cec5634
ApiServices: field-parity fixes — WO coordinates + work_description, asset polygon geometry
beta
21808cb
ApiServices: /api/v1/attachments resource (4 endpoints) + bearer-gated download
beta

Upcoming

📅
3.19 UAT deadline
Ragha's team to complete UAT. No blocking feedback = prod push Sept 17.
Sept 14
📅
JAMMS Artifact Review (Hyun + Tom)
Google Meet — 9:30-10am EDT
Sept 16
📅
3.19 Production deploy (target)
Contingent on clean UAT by Sept 14. Brent deploys.
Sept 17
📅
3.20 QA + deploy
4 tickets (680/690/691/681) — Brent on PTO next week, timing TBD.
TBD