Assignment queue got stuck

[ietf-svn-bot]

type_defect | by kivinen@iki.fi

---

I did assignments 2020-01-19 and the list of next reviewers was:

Joseph Salowey
Rich Salz
Stefan Santesson
Yaron Sheffer
Rifaat Shekh-Yusef
Melinda Shore
Valery Smyslov
Robert Sparks
Takeshi Takahashi
Tina Tsou

I did next assignments last week 2020-01-23 and the list of next reviwers stayed exactly same, i.e., it did not get updated last week, and when I did assignements again now I assigned same documents again to people who did assignments last week, and the queue did not go forward even then.

The head of the queue is Joseph Salowey which is unavailable, so that might cause the issue.

---

Issue migrated from trac:2879 at 2022-03-04 07:40:46 +0000

[ietf-svn-bot]

@kivinen@iki.fi commented

---

Now I withdrawn all the assignments, and added skip count for all those people, and it still wants to assign them to same people. I guess it is seeing that person X was assigned last time (for review which was withdrawn) and then tries to assign it again to same person.

I.e., in the popup list it says:

Rich Salz: requested to be selected next for assignment; skip next 1; #2; 5 fully completed.

[ietf-svn-bot]

@kivinen@iki.fi commented

---

And when I withdraw the request, they are there now twice. Once for for the previous request, and second time for the auto-suggested, see attached picture.

[ietf-svn-bot]

@kivinen@iki.fi uploaded file Screenshot from 2020-01-30 14-48-49.png (93.3 KiB)

All assignment twice now.

[ietf-svn-bot]

@kivinen@iki.fi commented

---

And if I try to close those extra assignments, it closes also the auto-suggested one, i.e., I tried to close draft-halpern-gendispatch-consensusinformational and now I do not have that there anymore at all.

If I do the assignment for the auto-suggested one, and ignore the previous one, and save things, and then when I already have new assignment open, I can close the other one without affecting the other one.

[ietf-svn-bot]

@kivinen@iki.fi commented

---

But it still always says that Rich Salz, Yaron Sheffer, Rifaat Shekh-Yusef and Melinda Shore "requested to be selected next for assignment", and I have not found a way to clear that from the database. I did assignments manually, one by one to get them done this week, but I hope this can be fixed before next week...

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

I've manually reset the 'request_assignment_next' field in the ReviewerSettings objects for those reviewers. They won't appear as first the next time you try to make an assignment.

This field (a boolean) get set when a reviewer asks for the next assignment, using their reviewer settings page (see #2336).

It is also set when someone rejects a review or has a request withdrawn (see #2420).

Did the latter happen for these 4 people?

[ietf-svn-bot]

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

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

Lowered priority - Tero should be unstuck, but we need to keep talking about how things got stuck this time to determine what we need to change.

[ietf-svn-bot]

@kivinen@iki.fi commented

---

Replying to ietf-svn-conversion/datatracker#2879 (comment:5):

It is also set when someone rejects a review or has a request withdrawn (see #2420).

Did the latter happen for these 4 people?

Yes, as I said in my first comment, after I noticed I had reassigned new documents to same people again, I withdrawn them and tried to reassign them to next people.

[ietf-svn-bot]

@kivinen@iki.fi commented

---

This happened again. I did in order assignments for Vucinic, Wallace, Waltermire, Weis, Wierenga, Wood, Wouters, and Xia. In addition I did reassignment old document to Sheffer.

The queue got stuck again, after Watermire, i.e., now the top of the queue is Weiler, which is unavailable, and Weis, Wierenga, Wood, Wouters, and Xia are early in the queue, when they should be in the end.

If this is going to happen every time we come to reviewer who is unavailable (can do followups), this is will affect us almost every week, and should be fixed asap.

Can also someone reset secdir queue pointer from Weiler to Zhang.

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

I've reset the queue pointer to Zhang.

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

You already have the ability to change the request_assignment_next bit by going to the individual reviewer's ReviewerSetting page.

Navigation is by clicking on the names in the list at /group/secdir/reviewers/

Look for the "Select me next for an assignment checkbox"

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

From afb818c:

Allow review team secretaries and the secretariat to reset the next reviewer in queue for review teams using the RotateAlphabetically policy. Partially addresses #2879. Commit ready for merge.

[ietf-svn-bot]

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

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

From 334f013:

Merged in afb818c from rjsparks@nostrum.com:
Allow review team secretaries and the secretariat to reset the next reviewer in queue for review teams using the RotateAlphabetically policy. Partially addresses #2879.