Add owner reassignment support to persons/deals/leads/organizations update commands
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 64/100
Research direction
Start by locating the persons, deals, leads, and organizations update command entry points and inspect how their existing options map to Pipedrive updates. Add the owner identifier option consistently across those commands, then run each command's help and update tests or checks to verify owner reassignment; the optional bulk commands are separate scope.
Written by the indexing model from the issue text.
Description
Problem
The current pipedrive persons update command (and likely deals/leads/organizations update) does not expose an --owner or --owner-id flag.
This makes it impossible to reassign records via the CLI when team members depart, change roles, or when bulk ownership cleanup is needed. Today, the only workaround is to go into the Pipedrive web UI and reassign records one-by-one, which doesn't scale when a former employee leaves behind dozens or hundreds of records.
Reproduction
pipedrive persons update --help
Current options:
--name--email--phone--org-id--address--custom-field
No --owner / --owner-id flag.
Proposed Solution
Add --owner-id <user-id> (or --owner <user-id>) flag to the following update commands:
pipedrive persons updatepipedrive deals updatepipedrive leads updatepipedrive organizations update
The Pipedrive API supports updating owner_id on all of these resources, so this should be a thin wrapper.
Bonus: Bulk reassignment
A pipedrive persons reassign --from-owner <user-id> --to-owner <user-id> (and equivalent for deals/leads/orgs) would be very useful for handling team-member departures. Could be implemented as a convenience command that lists + iterates the update endpoint.
Use Case
Team-member offboarding: when someone leaves, all of their open deals, leads, persons, and organizations need to be reassigned to a new owner so they show up in the right rep's daily queues. Currently a manual, error-prone process.
- Dominant language
- C#
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Aaronontheweb/pipedrive-cli
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Aaronontheweb/pipedrive-cli#185 ·
All issues in Aaronontheweb/pipedrive-cli
Similar issues
-
.NET bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
RayWangQvQ/BiliBiliToolPro#1144 ·
Maintainers usually reply within 1 day
-
area-System.Numerics.Tensors untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/runtime#134691 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
microsoft/DataFactory.MCP#121 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
unoplatform/uno.templates#2277 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/fluentui-blazor#5344 · 1 comment ·
Maintainers usually reply within 1 day