List view
- No due date•18/26 issues closed
Work to get the tool successfully reviewed and found to meet the DPG Standard so that it can be added to the DPG registry (https://digitalpublicgoods.net/registry/). DPG status is valid for a period of one year from its approval, after which all applications undergo an automatic review process. This is to ensure that all solutions comply with the latest version of the DPG Standard. https://docs.google.com/spreadsheets/d/1p_esCblUeBHmkx0AL5ZpAaJMYYbatdSyL4YIugXZPg8/edit#gid=0
No due date•2/2 issues closedThis is work for all the technical setup prior to any feature development for the Complaint Manager. https://github.com/orgs/PublicDataWorks/projects/1/views/1?pane=issue&itemId=54682487
Overdue by 1 year(s)•Due by June 30, 2024•4/21 issues closed- Overdue by 2 year(s)•Due by March 31, 2024•7/11 issues closed
- No due date•8/18 issues closed
- No due date•6/18 issues closed
- No due date•10/20 issues closed
Goal: - To fix critical and high bugs only - To implement minor changes requested by users to increase adoption Big criteria: 1. Critical - Critical bugs are those that can cause serious problems if not fixed. They should be fixed as soon as possible. 2. High - High-priority bugs are those that may cause some inconvenience, but don't necessarily pose a threat to the system or users. They should be fixed as soon as possible, but may not take priority over critical bugs. 3. Normal - Normal-priority bugs are those that don't necessarily affect the system or users, but could still be fixed if necessary. They should not be ignored, but may not take priority over other bug fixes. 4. Low - Low-priority bugs are those that do not pose a threat to the system or users, but could still be troublesome if not fixed. They should only be addressed if there is no other option and they don't conflict with other projects.
No due date•12/39 issues closed