Message ID | 1441803554-31677-8-git-send-email-stephen.finucane@intel.com |
---|---|
State | Superseded |
Headers | show |
diff --git a/patchwork/forms.py b/patchwork/forms.py index 0327958..a553234 100644 --- a/patchwork/forms.py +++ b/patchwork/forms.py @@ -89,10 +89,7 @@ class DeleteBundleForm(forms.Form): class DelegateField(forms.ModelChoiceField): def __init__(self, project, *args, **kwargs): - queryset = User.objects.filter(profile__in = \ - UserProfile.objects \ - .filter(maintainer_projects = project) \ - .values('pk').query) + queryset = User.objects super(DelegateField, self).__init__(queryset, *args, **kwargs)
Currently, Patchwork only allows to delegate patches to developers who are registered as "maintainers" of the project in Patchwork. This is a bit annoying as "maintainers" in the Patchwork sense have the power to change the state of *any* patch. It would be helpful to delegate the handling of a patch to a certain developer (who is neither the submitter of the patch nor a maintainer of the project). This request is documented here: https://lists.ozlabs.org/pipermail/patchwork/2015-July/001351.html Implement this pattern. Signed-off-by: Stephen Finucane <stephen.finucane@intel.com> --- patchwork/forms.py | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)