Multiple Patch Delegates

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend, database

Research direction

Start by locating the current delegation ForeignKey and the related data migration path. Review the mailing-list proposal and the alternative key:value label approach before deciding how multiple delegates should be represented; done means existing delegation data is migrated and a patch can be delegated to more than one user.

Written by the indexing model from the issue text.

Description

enhancement

From Mailing List

Overview

Wouldn't it be useful to create a tagging system which allows to
associate an arbitrary list of tags to each patch. This could even
replace the delegation feature by adding special tags like
"delegate:" to delegate the patch to a certain user. This
would also have the benefit of allowing the delegation to more than one
user, by simply having several "delegate:" tags on the same
patch.

This should involve a basic migration from the current ForeignKey to a new ManyToMany key.

Dependencies

None.

Additional Work Items

N/A

Alternatives

We could utilize key:value labels, as suggested in the original mail.

Useful resources

N/A

Dominant language
Python
Stars
317
Forks
91
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getpatchwork/patchwork

All issues in getpatchwork/patchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.