CA/Incident Dashboard: Difference between revisions

From MozillaWiki
< CA
Jump to navigation Jump to search
m (Gerv moved page CA/ca-bugs to CA/Incident Dashboard)
m (Added column last_change_time)
Line 11: Line 11:
         "whiteboard":"ca-investigation",
         "whiteboard":"ca-investigation",
         "cf_blocking_b2g_type":"contains",
         "cf_blocking_b2g_type":"contains",
         "include_fields": "id, summary, status, assigned_to, whiteboard"
         "include_fields": "id, summary, status, assigned_to, whiteboard, last_change_time"
     }
     }
</bugzilla>
</bugzilla>
Line 23: Line 23:
         "whiteboard":"ca-incident",
         "whiteboard":"ca-incident",
         "cf_blocking_b2g_type":"contains",
         "cf_blocking_b2g_type":"contains",
         "include_fields": "id, summary, status, assigned_to, whiteboard"
         "include_fields": "id, summary, status, assigned_to, whiteboard, last_change_time"
     }
     }
</bugzilla>
</bugzilla>
Line 40: Line 40:
         "whiteboard":"compliance",
         "whiteboard":"compliance",
         "cf_blocking_b2g_type":"contains",
         "cf_blocking_b2g_type":"contains",
         "include_fields": "id, summary, status, assigned_to, whiteboard"
         "include_fields": "id, summary, status, assigned_to, whiteboard, last_change_time"
     }
     }
</bugzilla>
</bugzilla>

Revision as of 20:39, 16 August 2017

Open CA Bugs in Bugzilla

Open Incident Related Bugs

Investigation or Discussion

Concern has been raised about certificates that a CA has issued. Investigation and/or discussion in progress.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Resulting CA Action Items

The concern about a CA's certificates has been confirmed, and the CA has follow-up action items.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


Open CA Compliance Bugs

A CA compliance bug relates to a concern about a CA's certificates failing to comply with Mozilla's CA Certificate Policy and/or the CA/Browser Forum's Baseline Requirements, and is determined to not be an imminent security concern.

Anyone may create a CA Compliance bug as follows:

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);