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 selecting the recipients of a mail among accept-class papers while also using the "Choose papers" function, I found a potentially confusing combination of options in the UI.
In case I choose:
To: "Contact authors of accept-class papers"
Tick "Choose papers"
some query "in "Submitted"" (e.g., !has:final)
it seems that non-accept-class papers also make it to the resulting list of papers for which the email should be sent. (In the HotCRP instance where I'm looking, the non-accept-class paper has no decision. I don't know if the behavior would be different for an explicitly rejected paper.)
I'm not sure how this actually pans out in practice (I'm not going to try 😉), i.e., whether the email will end up being sent to the non-accepted paper. In any case, the UI seems confusing in this regard, and emails may be unintentionally sent to non-accept-class papers despite the first selection in the "To:" field.
The text was updated successfully, but these errors were encountered:
When selecting the recipients of a mail among accept-class papers while also using the "Choose papers" function, I found a potentially confusing combination of options in the UI.
In case I choose:
!has:final
)it seems that non-accept-class papers also make it to the resulting list of papers for which the email should be sent. (In the HotCRP instance where I'm looking, the non-accept-class paper has no decision. I don't know if the behavior would be different for an explicitly rejected paper.)
I'm not sure how this actually pans out in practice (I'm not going to try 😉), i.e., whether the email will end up being sent to the non-accepted paper. In any case, the UI seems confusing in this regard, and emails may be unintentionally sent to non-accept-class papers despite the first selection in the "To:" field.
The text was updated successfully, but these errors were encountered: