Bug #3525

[API] Users should have manage permission on their own repositories

Added by Tom Clegg about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Tom Clegg
Category:
-
Target version:
2014-08-27 Sprint
Start date:
08/08/2014
Due date:
% Done:

100%

Estimated time:
(Total: 2.00 h)
Story points:
0.5

Subtasks

Task #3526: Review 3525-manage-own-repoResolvedTom Clegg

Task #3530: Migrate existing repo permissions to can_manageResolvedTom Clegg

Associated revisions

Revision 0cae143d
Added by Tom Clegg about 5 years ago

Merge branch '3525-manage-own-repo' refs #3525

Revision 0850fa67 (diff)
Added by Tom Clegg about 5 years ago

Update tests and user setup methods. refs #3525

Revision 71ed41b8 (diff)
Added by Tom Clegg about 5 years ago

Fix repositories.get_all_permissions to report manage, write, and read. refs #3525

History

#1 Updated by Tom Clegg about 5 years ago

  • Status changed from New to In Progress

#2 Updated by Peter Amstutz about 5 years ago

Nice easy patch, but what about a migration that will fix permissions for existing users?

#3 Updated by Peter Amstutz about 5 years ago

  • Assigned To set to Tom Clegg

#4 Updated by Tom Clegg about 5 years ago

Peter Amstutz wrote:

Nice easy patch, but what about a migration that will fix permissions for existing users?

I think in our case changing all can_write repo permissions to can_manage would do what we want, but making a migration do that automatically seems hazardous. Perhaps better in this case to just do it manually?

#5 Updated by Tom Clegg about 5 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF