-
Notifications
You must be signed in to change notification settings - Fork 509
Can't edit ballots for RFCs that are advancing in place #667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@[email protected] commented The related model bug is bug #668 |
@[email protected] commented Some progress on this at |
@[email protected] commented Replying to ietf-svn-conversion/datatracker#667 (comment:2):
Should have said 3134: |
@[email protected] changed status from |
@[email protected] changed resolution from `` to |
@[email protected] commented This will be addressed using the post-redesign schema. See ticket #803 |
resolution_overtaken by events
type_defect
| by [email protected]The tracker currently doesn't allow ballots issues against RFCs (for standards ladder advancement without revision) to be edited.
The Edit Position button on the IESG Evaluation tab of the main document view takes you to the ballot for the draft, not the ballot for the RFC.
The Edit Position button on the popup form you get when left clicking the position grid wherever it is displayed (same as right-clicking that position grid) takes you to a url that 404's
Example: https://datatracker.ietf.org/doc/rfc5590/edit/position/
For now, the IESG is working around this using the old tracker.
Related - the model (I think) assumes that there will only be zero or one ballots for an RFC. Until we change from the 3 tier model, there can be two.
Issue migrated from trac:667 at 2022-03-04 01:50:10 +0000
The text was updated successfully, but these errors were encountered: