Conflict Review ballots seem to have disappeared

[ietf-svn-bot]

resolution_overtaken by events type_defect | by avezza@amsl.com

---

https://datatracker.ietf.org/doc/conflict-review-vesely-authmethod-dnswl/history/ shows that there has been a ballot, and positions have been taken, but the document's main page claims no ballot has been issued, and the controls for sending the approval message are not available.

---

Issue migrated from trac:2851 at 2022-03-04 07:37:56 +0000

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

The issue here is that the new IRSG ballot code assumes there are only two ballot type slugs in existance (approve and irsg-approve). However, there are many more, all currently used by the IESG to do things like ballot conflict-reviews and status changes.

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

From 5773d62:

Works around a problem with displaying IESG evaluation information for non-approve ballot types. Partially addresses #2851. Commit ready for merge.

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

This is patched into production as 6.115.0p1 (yes, I missed the . before p1)

[ietf-svn-bot]

@rjsparks@nostrum.com changed priority from critical to medium

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

Shifting the priority since production is no longer blocked. We can work on model and test improvements for this at the regular pace.

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

From 2961f4d:

Merged in 5773d62 from rjsparks@nostrum.com:
Works around a problem with displaying IESG evaluation information for non-approve ballot types. Partially addresses #2851.

[ietf-svn-bot]

@rjsparks@nostrum.com changed status from new to accepted

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

This ticket is only waiting for improved tests.

[ietf-svn-bot]

@rjsparks@nostrum.com changed status from accepted to closed

[ietf-svn-bot]

@rjsparks@nostrum.com set resolution to overtaken by events