Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[OJS 3.4] The email "A new submission needs an editor to be assigned" is not available in the email template list #10463

Open
pilasou opened this issue Sep 20, 2024 · 0 comments

Comments

@pilasou
Copy link

pilasou commented Sep 20, 2024

Describe the bug
A new email that was added to OJS 3.4 is automaticaly sent each time a new submission is made. The subject of the email is "A new submission needs an editor to be assigned an editor to be assigned" and its content is :


Dear [user first name and last name],
The following submission has been submitted and there is no editor assigned.
[Title of the submission](URL of the submission)
Name of the author
Abstract
This is an automated email from [Journal Name]


This email cannot be found in the email template list and thus cannot be edited.

It is sent to all user with editor role, and the user has no opportunity to disable the notification in his/her OJS profil.

Finally, each email sent is recorded in the submission activity log (as shown below from our OJS test instance).

image

To Reproduce
Steps to reproduce the behavior:

  1. Ensure you have more than one user with editor role
  2. As author, make a new submission
  3. Do not assign editor to the submission
  4. The email is sent to the editor (should be not long after the new submission email)
  5. See the activity log (should be one entry for each user with editor role)

Additional information
This new email must be added to the email template list.

A user must have the ability to disable the notification for this email. Ideally, a delay should be set up so that this email is not sent along with the new submission email.

For the activity log, I am not certain of the best solution (keep as is? only use a generic entry if at least one email has been sent?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant