-
Notifications
You must be signed in to change notification settings - Fork 4
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
TP2000-1476 Edit capability for blocking periods #1313
TP2000-1476 Edit capability for blocking periods #1313
Conversation
@@ -1242,6 +1248,77 @@ def get_queryset(self): | |||
return QuotaSuspension.objects.filter(pk=self.deleted_suspension) | |||
|
|||
|
|||
class QuotaBlockingUpdateMixin(TrackedModelDetailMixin): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not essential, but if my refactoring of the quotas space PR is released first, you could move these into their own file with the other QuotaBlocking model views.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment which is entirely dependent on whether this goes out before my PR or not, otherwise LGTM :)
TP2000-1476 Edit capability for blocking periods
Why
User’s can create a blocking periods for quotas, but they can’t edit existing periods. We should implement that journey using the create form as a template.
What
This PR:
List view
Edit
Confirm update
Delete
Confirm delete