Skip to content

[Return to Done] | Editorial Workflow Section - Submission Workflow, When returning to done as a participant with access it throws an error #13803

Closed

Description

@Tribunal33

Valid Title

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

Description

Previous tickets that didn't have specific requirements for roles or permissions #12798 and #12799.

This is really an investigation issue into a user scenario that causes an error. Once the investigation is complete we can include the A/C for the task or leave it as a bug and the repro steps will be the A/C.

Suggested A/C

  • Given that an editor or sub-editor is a participant of the submission, when they move a submission back into done workflow, then they should have permission.

Scenario from our base dataset: If I'm logged in as dbarnes the JM and they are a participant of the submission. Automatically added to most submissions in our base dataset. If I take one submission out of published queue and into the workflow and then move it back to done queue there shouldn't be a problem right? I don't think this was considered it in the original testing but when trying again there is an error.

Steps to Reproduce

  1. Preconditions: Have a submission that has been published and a Journal manager role added as a participant.
  2. Login with JM or sub-editor User/Role
  3. Navigate to the submission
  4. Click on Return to workflow
  5. Click on Return to Done

Expected Result

Should freely move between Done and Workflow queues.

Actual Result

Error message:
error call is this : {
"error": "user.authorization.roleBasedAccessDenied",
"errorMessage": "The current role does not have access to this operation."
}
image
image

Environment Details

No response

Application Version

OJS, OMP, OPS 3.6

Logs

No response

Additional Information

No response

PRs

main

ore

Activity

  1. added theissue type on Nov 13, 2026
  2. added this to the 3.6 milestone on Nov 13, 2026
  3. added
    TriageAn issue reported by a community member that needs to be reviewed and triaged by the PKP team.
    on Nov 13, 2026
  4. self-assigned this
    on Nov 13, 2026
  5. removed
    TriageAn issue reported by a community member that needs to be reviewed and triaged by the PKP team.
    on Nov 13, 2026
  6. added 2 commits that reference this issue on Nov 13, 2026
  7. ewhanson commented on Nov 13, 2026

    @ewhanson
    Contributor

    @Tribunal33, merged into main and ore if you'd like to test this one.

  8. Tribunal33 commented on Nov 14, 2026

    @Tribunal33
    ContributorAuthor

    @ewhanson Next time please provide evidence that this is passing before closing.

    I have tested this on my local repo and can confirm the repro steps are passing and exptected results are correct. Additionally I test some other cases based on some exploration and they also pass. Here are the scenarios that are now working.

    1. Original repro steps with Manager who is a participant ✅
    2. Manager who is not a participant should still be able to move freely between workflow and done ✅
    3. Sub-editor who is a participant should be able to move freely between workflow and done ✅
    4. Sub-editor who is not a participant should not be able to move between workflow and done receives a 401 ✅
    5. Sub-editor who is a participant but has only recommend only enabled is denied with a 401 when trying to move between done and workflow ✅
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions