Hyrax is a Ruby on Rails Engine built by the Samvera community. Hyrax provides a foundation for creating many different digital repository applications.
In Sirenia, if a user transfers their work, and the receiving user accepts the transfer and selects the option to allow the original depositor to retain access, the access is not granted.
Steps to reproduce the behavior in User Interface (UI)
See also QA testing steps for W_1.14
Login as basic_user (non-Admin)
Go to the Dashboard > Works
Click on the Actions menu, and select Transfer ownership of work
Complete the steps to transfer the work to another user (admin user)
Login as the admin user
Go to Your Activity > Transfers
Accept the transfer, and select the option to allow the original depositor to retain access
Login as the basic_user
Go to Your Activity > Transfers
Click on the work you just transferred
See "Unauthorized - the page you have tried to access is private" message
Actual behavior (include screenshots if available)
Sirenia docker image (Hyrax 5.0.1)
Acceptance Criteria/Expected Behavior
[ ] If a user transfers their work and the recipient grants them permission to retain access, the original depositor should still be able to see the works in the Dashboard > Works section
Rationale (for feature request only)
Provide the rationale or user story that describes "why" this issue should be addressed. Especially if this is a new feature or significant change to the existing implementation.
Work transfers should continue to function as expected across all versions of Hyrax.
Related work
Link to related issues or prior related work here.
Descriptive summary
In Sirenia, if a user transfers their work, and the receiving user accepts the transfer and selects the option to allow the original depositor to retain access, the access is not granted.
Steps to reproduce the behavior in User Interface (UI)
See also QA testing steps for W_1.14
Actual behavior (include screenshots if available)
Sirenia docker image (Hyrax 5.0.1)
Acceptance Criteria/Expected Behavior
Rationale (for feature request only)
Provide the rationale or user story that describes "why" this issue should be addressed. Especially if this is a new feature or significant change to the existing implementation.
Work transfers should continue to function as expected across all versions of Hyrax.
Related work
Link to related issues or prior related work here.