Skip to content

Something messed up in reviews #2777

Description

@ietf-svn-bot

resolution_overtaken by events type_defect | by kivinen@iki.fi


I had reviewer who had two assigned documents, but he said he cannot do them and wanted to be marked away. I marked him being completely unavailable, and then marked that he rejected two two assignments made for him, as I wanted to assign them to someone else.

After this something got messed up.

https://datatracker.ietf.org/group/secdir/reviewers/

page correctly shows him unavailable, and shows that last reviews done by him are rejected.

If you click 2019-07-04 link for the draft-ietf-intarea-frag-fragile document to see the actual review request you get link:

https://datatracker.ietf.org/doc/draft-ietf-intarea-frag-fragile/reviewrequest/10637/

but there the data in the page is from completely wrong document (draft-ietf-spring-segment-routing-ldp-interop) and wrong review.

If you find the actual doc page for the document:

https://datatracker.ietf.org/doc/draft-ietf-intarea-frag-fragile/

you will notice that it will not list any reviews from the Secdir at all, even not as an open or closed review. The review assigned and rejected to Miller has disappeared from the list.

Same thing happened to the

https://datatracker.ietf.org/doc/draft-ietf-core-multipart-ct/reviewrequest/10401/
https://datatracker.ietf.org/doc/draft-ietf-core-multipart-ct/

i.e., reviewrequest lists completely wrong document and wrong results, and the actual document does not include any assignments for secdir.

If I enable the closed reviews view to show me reviews from 1 year back, I can find the draft-ietf-core-multipart-ct from the list:

https://datatracker.ietf.org/doc/draft-ietf-core-multipart-ct/reviewrequest/11807/

but I cannot find the draft-ietf-intarea-frag-fragile from the closed list at all.

Also when I check the "Closed" date for the draft-ietf-core-multipart-ct it should be now, as I rejected the document now, but the Closed data is 2019-03-18, which is funny as it is BEFORE the assigned date of 2019-03-22 and before deadline
date of 2019-04-08.

I have now idea how I can get those documents back for me so I can reassign them to someone else. I would have assumed that when I reject them, then they will come back to the secretary for reassignment, but perhaps I should have done that BEFORE I marked the person unavailable.

Anyway now there are some items in the datatracker which are not in sync anymore, i.e., there are links for reviews pointing to wrong document and I wonder if this will cause more issues in the future. This is the reason I marked this issue as critical. If there will not be any problems in the future for this errors in database, then I think this can be just marked with medium priority.


Issue migrated from trac:2777 at 2022-03-04 07:15:23 +0000

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions