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

Reshare inner folder, recipients not visible by original sharer #12964

Closed
PVince81 opened this issue Dec 19, 2014 · 4 comments
Closed

Reshare inner folder, recipients not visible by original sharer #12964

PVince81 opened this issue Dec 19, 2014 · 4 comments

Comments

@PVince81
Copy link
Contributor

Steps to reproduce

  1. Create users "user1", "user2" and "user3"
  2. Login as "user1"
  3. Create a folder "test"
  4. Share "test" with "user2"
  5. Login as "user2"
  6. Create a subdir "test/sub"
  7. Share "test/sub" with "user3"
  8. Login as "user1" again
  9. Open share dropdown for "test/sub": "user3" is not visible, might be expected
  10. Try sharing with "user3"

Expected result

Not sure ?

Actual result

Error message that "test/sub" is already shared with "user3" even though it wasn't visible in the UI.
Could be a usability issue.

At step 9 the share to "user3" isn't visible because it was initiated by "user2", not "user1".
I guess this could be solved by making the reshares NOT a chain: #9058

@schiesbn @owncloud/designers

@PVince81 PVince81 changed the title [master] Reshare twice situation Reshare inner folder, recipients not visible by original sharer Dec 19, 2014
@jancborchardt
Copy link
Member

Yeah, I think we already had an issue for that somewhere but I can’t find or recall it at the moment. Something about that reshares should also show up in the list for everyone to see since everyone that folder is shared with is essentially part of a group and should be aware of everyone else.

@PVince81
Copy link
Contributor Author

@jancborchardt you probably mean #9058

@jancborchardt
Copy link
Member

@PVince81 yeah, should we close this in favor of that? Or did you mean something different?

@PVince81
Copy link
Contributor Author

Closing in favor of #9058

@lock lock bot locked as resolved and limited conversation to collaborators Aug 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants