Hi Aaron, Thank you for bringing this to our attention and for providing so much detail. We resolved the issue and you should now witness the expected result you described.
I have been unable to find any descriptions of similar bugs on ccadb.org or > in the add/update root request help doc > <https://docs.google.com/document/d/1AUbwbyqCq3jR7wP0fSWjL1us9s4sZIbXGRyo_ko77QM/edit?tab=t.0#heading=h.8bo6t2asenen>, > and I'm not aware of a more formal way to file bugs against CCADB, so I am > sending this message here. Thanks for taking the time to review these resources. Rob is correct in that we use the 'Common CA Database <https://bugzilla.mozilla.org/enter_bug.cgi?product=CA%20Program&component=Common%20CA%20Database>' component in the 'CA Program' product of Bugzilla to formally track bugs and enhancement requests. You are always welcome to file items there for our consideration. It's common for issues with CCADB Cases to be sent to [email protected] for quick attention. CA Owners also have the ability to add comments to Cases, which get reviewed during Steering Committee rotations and regular Case processing. All of these are acceptable approaches for bringing issues to our attention. Thank you! -Chris On Thu, Nov 7, 2024 at 5:13 AM 'Rob Stradling' via CCADB Public < [email protected]> wrote: > > and I'm not aware of a more formal way to file bugs against CCADB > > There's a Bugzilla component: > > https://bugzilla.mozilla.org/buglist.cgi?component=Common%20CA%20Database&query_format=advanced&product=CA%20Program&list_id=17308086 > > So presumably here? > > https://bugzilla.mozilla.org/enter_bug.cgi?product=CA%20Program&component=Common%20CA%20Database > > ------------------------------ > *From:* 'Aaron Gable' via CCADB Public <[email protected]> > *Sent:* 07 November 2024 00:15 > *To:* CCADB Public List <[email protected]> > *Subject:* Issues selecting applicable roots for audit documents > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > Hi CCADB team, > > I am attempting to run draft audit reports through ALV prior to requesting > final audit reports and submitting them to CCADB. However, I am unable to > select "applicable root certificates" for the new audit documents. > > Steps to reproduce: > 1. Create a new Add/Update Root Request case > 2. Navigate to Audits -> Standard Audit Information -> Edit > 3. Fill out the audit link, type, statement date, and audit period dates > 4. Select one or more of the available applicable roots > 5. Click "Save" > > Expected result: > 6. The modal dialog box closes and saves my entered information > > Actual result: > 6. After a few moments, it pops up a red toast saying "Error: > Script-thrown exception" > 7. The js console shows a traceback: > outputField.js:1 Error: Field [] was not found > at Object.y [as getUiField] (fieldUtils.js:1:1822) > at G.updateFieldInfo (outputField.js:1:7283) > at G.wireRecordUi (outputField.js:1:8024) > at po (aura_prod.js:49:42976) > at c.<anonymous> (aura_prod.js:49:21800) > at eval (baseRecordForm.js:1:2731) > at Array.forEach (<anonymous>) > at h.handleData (baseRecordForm.js:1:2717) > at h.handleRecordUiData (recordEditFormEdit.js:1:2061) > at aura_prod.js:49:19446 > 8. The loading throbber spins forever, until I refresh the page > 9. The refreshed page shows some of the data saved, but not the applicable > roots > > The dialog box saves just fine if I don't select any applicable roots. It > fails as described above when I pick one, or more than one, or use the > "select all" checkbox. > > Because I cannot select applicable roots, I cannot run ALV (it says > "Please provide audit statement information and indicate which root > certificates each audit applies to." when I try). > > I have been unable to find any descriptions of similar bugs on ccadb.org or > in the add/update root request help doc > <https://docs.google.com/document/d/1AUbwbyqCq3jR7wP0fSWjL1us9s4sZIbXGRyo_ko77QM/edit?tab=t.0#heading=h.8bo6t2asenen>, > and I'm not aware of a more formal way to file bugs against CCADB, so I am > sending this message here. > > Thank you, > Aaron > -- > You received this message because you are subscribed to the Google Groups > "CCADB Public" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/a/ccadb.org/d/msgid/public/CAEmnErfjLJKZsC-zyGvVC1vMCt-vk_8mTsHyiV%3Dbc%2BKZF4TKiw%40mail.gmail.com > <https://groups.google.com/a/ccadb.org/d/msgid/public/CAEmnErfjLJKZsC-zyGvVC1vMCt-vk_8mTsHyiV%3Dbc%2BKZF4TKiw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to the Google Groups > "CCADB Public" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/a/ccadb.org/d/msgid/public/MW4PR17MB47290E53289A3CF945F86808AA5C2%40MW4PR17MB4729.namprd17.prod.outlook.com > <https://groups.google.com/a/ccadb.org/d/msgid/public/MW4PR17MB47290E53289A3CF945F86808AA5C2%40MW4PR17MB4729.namprd17.prod.outlook.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "CCADB Public" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/ccadb.org/d/msgid/public/CAAbw9mC6%2B9VH-82gqtuuP8X3cTntsPD5ngkULGdbiWdAhhb5AQ%40mail.gmail.com.
