Conversation
* feat(teams): add update POC functionality with API integration * feat(teams): invalidate tasks query on POC update for improved data consistency * fix(teams): update API endpoint for POC update and adjust role change condition in team members component * refactor(teams): rename updateTeamPoc to updateTeam and extend parameters for improved flexibility
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![korbit-ai[bot]](https://avatars.githubusercontent.com/in/322216?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review by Korbit AI
Korbit automatically attempts to detect when you fix issues in new commits.
| Category | Issue | Status |
|---|---|---|
 |
Unfiltered data spreading in API request ▹ view | |
 |
Cannot clear POC assignment due to falsy value filtering ▹ view |
Files scanned
| File Path | Reviewed |
|---|---|
| src/api/teams/teams.type.ts | ✅ |
| src/api/teams/teams.api.ts | ✅ |
| src/components/teams/team-members.tsx | ✅ |
Explore our documentation to understand the languages and file types we support and the files we ignore.
Check out our docs on how you can make Korbit work best for you and your team.
2 participants
Date: 18 Oct 2025
Developer Name: @AnujChhikara
Issue Ticket Number
PRs going in Sync
Description
Documentation Updated?
Under Feature Flag
Database Changes
Breaking Changes
Development Tested?
Screenshots
Staging Proof
Screen.Recording.2025-10-18.at.10.50.16.PM.mov
Description by Korbit AI
What change is being made?
Add support for updating a team's POC (and other basic fields) via a new UpdateTeamParams type, a corresponding updateTeam API method, and UI flow to appoint a member as POC with success/error notifications and cache invalidations.
Why are these changes being made?
Enable selecting a new Point of Contact for a team and reflect changes in the UI and cache; streamline team updates via a single PATCH endpoint and keep frontend data in sync.