|
|
efd6f59fca
|
Populate ComplianceReportRequest on site review page
|
2026-04-17 21:40:04 +00:00 |
|
|
|
ac552be7e7
|
Send compliance report data with lead data
|
2026-04-17 20:51:07 +00:00 |
|
|
|
fa675f293d
|
Add initial work on getting compliance data for leads
|
2026-04-17 19:43:40 +00:00 |
|
|
|
617631063f
|
Add quick'n'dirty interface for leads and features
|
2026-04-17 02:59:01 +00:00 |
|
|
|
6b90edf053
|
Fix creation of signal for mailer
|
2026-04-16 10:47:13 +00:00 |
|
|
|
2ea47f03f4
|
Start wiring together request for a mailer to database
|
2026-04-16 10:15:28 +00:00 |
|
|
|
4a440e3022
|
Add a resource for getting service requests
|
2026-04-14 19:59:32 +00:00 |
|
|
|
21180816be
|
Start providing organization info and URLs is user/self
The new frontend needs it to do its work.
|
2026-03-22 01:22:44 +00:00 |
|
|
|
aa94cce2ad
|
Fix creation of signal from a communication report
I had broken this when altering the signal model to always require a
location
|
2026-03-20 18:03:32 +00:00 |
|
|
|
908ac4faea
|
Make signals, not leads, from public reports.
|
2026-03-19 17:41:56 +00:00 |
|
|
|
21e8b9880d
|
Remove report_location view, add lat lng to report table
|
2026-03-18 18:55:50 +00:00 |
|
|
|
e2af49a323
|
Make lead creation and invalidation for public reports work
The only thing wrong at this point that I can tell is that address
aren't being correctly populated when I reverse geocode.
|
2026-03-14 01:14:30 +00:00 |
|
