Skip to content

Disputes: add the missing reassign route, withdraw (DELETE) route, resolution note and an admin listing #1492

Closed

Description

@mftee

dto/reassign-dispute.dto.ts exists (closing #1256 was recorded) but DisputeController has no reassign route and DisputeService has no reassign method. The frontend's withdraw button calls DELETE /disputes/:id, which does not exist. The admin UI collects a resolution text but the backend UpdateDisputeStatusDto only accepts status. Admins also cannot list all disputes, only their own via GET /disputes.

Where

  • backend/src/dispute/dispute.controller.ts
  • backend/src/dispute/dispute.service.ts
  • backend/src/dispute/dto/
  • frontend/app/[locale]/(protected)/disputes/[id]/page.tsx

Suggested fix
Add PATCH /disputes/:id/assignee, DELETE /disputes/:id (owner, while OPEN), a resolution field on status change, and GET /admin/disputes with filters; log each action in the access log.

Acceptance criteria

  • Each route has guards and tests
  • Withdrawal is limited to the filer while the dispute is open
  • Resolution text is stored and returned

Activity

  1. BigBen-7 commented on Oct 17, 2026

    @BigBen-7
    Contributor

    @BigBen-7 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello, I'd like to pick this issue up.

    I'm an experienced software engineer with a strong foundation in JavaScript/TypeScript, distributed systems, and API development. I care about code quality, test coverage, and clear communication in open source work.

    I've gone through the details of this issue and I'm confident I can deliver a clean, well-tested solution that fits the codebase.

    I'd love the opportunity to work on this — please consider assigning it to me.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @BigBen-7 to this issue.

  2. OffixialSydney commented on Oct 17, 2026

    @OffixialSydney

    @OffixialSydney has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello Maintainer, I’ve gone through the issue and its acceptance criteria carefully. I understand what needs to be implemented and am confident I can deliver a solution that aligns with the expected design.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @OffixialSydney to this issue.

  3. drips-wave commented on Oct 17, 2026

    @drips-wave

    Congratulations, @BigBen-7! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @BigBen-7: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  4. added a commit that references this issue on Oct 17, 2026
  5. grantfox-oss commented on Oct 17, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @BigBen-7's PR #1550 was approved and merged by @mftee.

    🏆 @BigBen-7: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,428 total points). Track your full progress on GrantFox.

    👏 Great work, @BigBen-7! Keep contributing to CodeGirlsInc.

  6. drips-wave commented on Oct 17, 2026

    @drips-wave

    This issue has been completed by @BigBen-7 as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @BigBen-7: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions