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

CANCEL_REVIEW_ROUND decision isn't being recorded #10995

Open
1 task done
Vitaliy-1 opened this issue Feb 27, 2025 · 1 comment
Open
1 task done

CANCEL_REVIEW_ROUND decision isn't being recorded #10995

Vitaliy-1 opened this issue Feb 27, 2025 · 1 comment
Assignees
Labels
Bug:1:Minor A bug found in uncommon paths, with low consequences, limited users or has an easy workaround
Milestone

Comments

@Vitaliy-1
Copy link
Collaborator

Valid Title

  • I have updated the title to accurately reflect the bug description

Description

When submission is in a review stage, it's possible to make a decision - CANCEL_REVIEW_ROUND. After making this decision, correspondent entry isn't recorded in the edit_decisions table

Steps to Reproduce

  1. Make a submission
  2. Pass it to the review stage
  3. Click on 'CANCEL_REVIEW_ROUND'
  4. Record the decision
  5. If it was the first review round the submission goes back to the submission stage
  6. See that in edit_decisions table the correspondent entry is missing. Although it's being recorded in the event_log table

Expected Result

There should be an entry with the decision column equal to 31.

Actual Result

Without this record it's not reliable to calculate days in the submission stage, when the submission is returned from the review stage: #8893 (comment)

Environment Details

No response

Application Version

OJS main branch

Logs

No response

Additional Information

No response

@Vitaliy-1 Vitaliy-1 added the Bug:1:Minor A bug found in uncommon paths, with low consequences, limited users or has an easy workaround label Feb 27, 2025
@Vitaliy-1 Vitaliy-1 added this to the 3.5 Internal milestone Feb 27, 2025
@kaitlinnewson
Copy link
Member

Hi @Vitaliy-1, I looked into this a little and found this relevant thread - it seems this is also present in 3.4: #8477

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug:1:Minor A bug found in uncommon paths, with low consequences, limited users or has an easy workaround
Projects
None yet
Development

No branches or pull requests

3 participants