d5bae45799
* fix: Do not add user to the top of queue after reject (fixes #4505) Added a checkbox in the reject review dialog to ask whether user wants to be added to the top of the queue or not. Default is off. * Do not change request_assignment_next if wants_to_be_next is not True. Set the request_assignment_next also in LeastRecentlyUsedReviewerQueuePolicy so it can be used to override the assignment policy rules (i.e., if someone has once per month, but he rejects review with wants_to_be_next set to true, he will get new assignment immediately, not after one month). * Added wants_to_be_next to test cases too. * Fixed test function prototypes, they can't have any parameters, only self. Added test cases for test_return_reviewer_to_rotation_top both for RotateAlphabeticallyReviewerQueuePolicyTest and LeastRecentlyUsedReviewerQueuePolicyTest.
12 lines
240 B
Plaintext
12 lines
240 B
Plaintext
{% autoescape off %}Reviewer assignment rejected by {{ by }}.{% if message_to_secretary %}
|
|
|
|
Explanation:
|
|
|
|
{{ message_to_secretary }}
|
|
|
|
{% endif %}
|
|
{% if wants_to_be_next %}
|
|
User requested to be next in queue.
|
|
{% endif %}
|
|
{% endautoescape %}
|