Name formatting on iesg agenda changed and inconsistent #776
Comments
|
@olau@iola.dk commented Right. I had a look at this, first part is an oversight in the proxy layer. Second part with section 3 and 4 is a little bit more involved because we're storing the name of the token holder in the WG action model (that model is a remnant that we didn't get converted to something more sensible yet). But I've changed the edit select box to use full names, so if you go in and add or edit an action on https://datatracker.ietf.org/iesg/wgactions/, it'll use the same name as the rest of the agenda. Note that if you edit a current one, it'll look for a full name and get a mismatch so it will have to ask for the token name (by setting it to (None)). So if you go in and edit and save all the existing ones, the names should be perfect. If not, please let me know. :) Will commit now, then it should be live when Henrik deploys it. |
|
@olau@iola.dk changed status from |
|
@olau@iola.dk changed resolution from `` to |
|
@olau@iola.dk commented Fixed in 8723e7f: Use Person.plain_name as token holder names in proxy, and also in the WGAction form, fixes #776. |
|
@henrik@levkowetz.com changed status from |
owner:olau@iola.dkresolution_fixedtype_defect| by housley@vigilsec.comThe names that appear as the token holder on the agenda are just a wee bit different. It used to be first and last name, but now I see some titles too.
I have always wondered why the format of the token holder is dfferent is section 3 of the agenda and section 4 of the agenda. Since you will be in the code, maybe this is a good time to harmonize the format.
Issue migrated from trac:776 at 2022-03-04 01:59:16 +0000
The text was updated successfully, but these errors were encountered: