You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a version has multiple delayed-rejections pending (issues on different days), when the delay times out, we seem to use the copy of the first delayed-rejection, instead of the last.
STR (not verified, but we believe this is what happened on prod):
A developer submits an add-on
A reviewer delay-rejects with message "A"
A few days later, a reviewer delay-rejects with message "B" (this can happen when A was missing source code which was provided by the developer in the meantime)
When the delay times out, the rejection is executed with reason "A"
What did you expect to happen?
When the delay times out, the rejection is executed with reason "B" (the copy of the last delayed-rejection issued).
What happened?
When a version has multiple delayed-rejections pending (issues on different days), when the delay times out, we seem to use the copy of the first delayed-rejection, instead of the last.
STR (not verified, but we believe this is what happened on prod):
What did you expect to happen?
When the delay times out, the rejection is executed with reason "B" (the copy of the last delayed-rejection issued).
Is there an existing issue for this?
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: