CA/CCADB Dashboard: Difference between revisions
< CA
Jump to navigation
Jump to search
m (Add Severity column to help with priorities.) |
(Updated to the new way that CCADB SC uses Bugzilla Bugs to track enhancement requests.) |
||
| Line 1: | Line 1: | ||
= Dashboard for Common CA Database Updates = | = Dashboard for Common CA Database Updates = | ||
== CCADB API Access== | == CCADB API Access== | ||
| Line 11: | Line 9: | ||
"resolution": "---", | "resolution": "---", | ||
"status_whiteboard":"ccadb-api", | "status_whiteboard":"ccadb-api", | ||
"include_fields": "whiteboard, id, summary | "include_fields": "whiteboard, id, summary, last_change_time", | ||
"order": "status_whiteboard ASC, assigned_to DESC" | "order": "status_whiteboard ASC, assigned_to DESC" | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
== | == Bugs == | ||
Bugs that unintentionally remove pre-existing functionality or negatively impact CCADB users should have priority over Enhancements, and should be set to P1. Low impact bugs will start at P4 and be considered with ERs. If it's a low LOE bug (less than 4 hours of work) it can go from P4 to P1 without prioritization/design. | |||
<bugzilla> | <bugzilla> | ||
{ | { | ||
| Line 48: | Line 22: | ||
"resolution": "---", | "resolution": "---", | ||
"whiteboard":"ccadb-bug", | "whiteboard":"ccadb-bug", | ||
"include_fields": "priority, id, summary | "include_fields": "priority, id, summary, last_change_time", | ||
"order": "priority ASC, assigned_to DESC" | "order": "priority ASC, assigned_to DESC" | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
== Enhancement Requests == | |||
The Priority values are used as follows: | |||
* P1 - Development in progress | |||
* P2 - Design complete | |||
* P3 - Prioritized | |||
* P4 or not set - To be prioritized and scheduled later | |||
<bugzilla> | <bugzilla> | ||
{ | { | ||
| Line 65: | Line 43: | ||
"o2": "nowordssubstr", | "o2": "nowordssubstr", | ||
"v2": "ccadb", | "v2": "ccadb", | ||
"include_fields": "priority, id, summary | "include_fields": "priority, id, summary,last_change_time" | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
Revision as of 21:12, 3 May 2023
Dashboard for Common CA Database Updates
CCADB API Access
Requests for API access to the CCADB as per https://github.com/mozilla/CCADB-Tools/tree/master/API_AddUpdateIntermediateCert
| Whiteboard | ID | Summary | Last change time |
|---|---|---|---|
| [ccadb-api] | 1798894 | Chrome Root Program - Provide OAuth and API for Chrome to automate root store updates to the CCADB | 2025-01-07T16:02:32Z |
| [ccadb-api] | 1901864 | Certainly: Request for access to CCADB API | 2025-04-01T15:51:05Z |
| [ccadb-api] | 1916851 | Amazon Trust Services - Request for Access to CCADB API | 2024-09-13T16:08:07Z |
| [ccadb-api] in sandbox | 1770056 | Google Trust Services - Request for access to CCADB API | 2022-11-14T22:22:21Z |
| [ccadb-api] in sandbox | 1779692 | NAVER Cloud - Request for access to CCADB API | 2023-01-12T18:25:21Z |
| [ccadb-api] in sandbox | 1793511 | Microsoft - Request for access to CCADB API | 2023-09-18T16:26:31Z |
6 Total; 6 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Bugs
Bugs that unintentionally remove pre-existing functionality or negatively impact CCADB users should have priority over Enhancements, and should be set to P1. Low impact bugs will start at P4 and be considered with ERs. If it's a low LOE bug (less than 4 hours of work) it can go from P4 to P1 without prioritization/design.
| Priority | ID | Summary | Last change time |
|---|---|---|---|
| P3 | 1747829 | Disable the pull-down (Edit and Change Owner) in all tab views for CAs and Root Store Operators | 2025-01-08T16:35:52Z |
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Enhancement Requests
The Priority values are used as follows:
- P1 - Development in progress
- P2 - Design complete
- P3 - Prioritized
- P4 or not set - To be prioritized and scheduled later
70 Total; 70 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Closed
A historical view of past CCADB updates (from May 2021 onward) may be found here: