-
From ken9ross2/support *ken.ross*
More reports
-----
From [==ken.ross]
create incident More incidents
-
- [x] PDR sent (date - initials)
- [x] Response received
- [x] Agency requests clarification
- [x] Clarification sent (date(s)) - by phone 7/16/24 (see comment)
- [x] Data received (installmen…
-
For prod data, a large majority of incidents' and incident reports' report entries are system-generated (e.g. "Abraham added incident type Junk"). We should consider filtering out those entries from o…
-
As @Kirkman found in #597 , a scraper can stop producing output without triggering an error in workflow.
While a few states keep WARN and non-WARN layoffs in the same database it's unlikely that ma…
-
👋 I thought this might be more useful for me to raise this here rather than via email. On [Conferences – Support for event organizers - Before the event](https://github.com/django/code-of-conduct/blob…
-
- [x] PDR sent (6/7/24 - hk)
- [x] Receipt of PDR confirmed by Rana Hoover on portal: https://pacificwa.govqa.us/WEBAPP/_rs/(S(xqlhbphmd04qedjc4zhysf22))/RequestEdit.aspx?sSessionID=71212136178:5721…
-
Rendering report with about 5000 incidents currently consumes about 200 MB on the server to generate. This should be reduced.
Example of such report: https://reports.phpmyadmin.net/reports/view/18227…
nijel updated
7 years ago
-
**Describe the enhancement**
- [x] Add an additional field, which would be used as impact title
- [x] Have a better display of sector and subsector in the creation (they are now ordered)
- [x] add …
-
This issue is an early attempt to explain a challenge we have. It yet has to become more defined to make it a meaningful task description / roadmap item.
## Summary
How can we enable customers to fi…
-
Incidents should be stored in a database of sorts to allow sharing, cooperation and persistence of incident reports