then later, the reviewer manually approved the add-on
then later, the version got rejected as the delayed rejection timer ran out and it was never cleared.
What did you expect to happen?
I'm trying to think if this is an intended behaviour, but so far I feel like this shouldn't happen. If a reviewer approves a version pending rejection, they won't intend on still rejecting it at date that was set in the original review verdict.
If multiple versions are delayed rejected, the delayed rejection should only be dropped for the version manually approved.
What happened?
For add-on 869700 version 24.3.48.1 I see that
What did you expect to happen?
I'm trying to think if this is an intended behaviour, but so far I feel like this shouldn't happen. If a reviewer approves a version pending rejection, they won't intend on still rejecting it at date that was set in the original review verdict.
If multiple versions are delayed rejected, the delayed rejection should only be dropped for the version manually approved.
Is there an existing issue for this?
┆Issue is synchronized with this Jira Task