Implement the Raise Dispute submission and route to the dispute review page

[Benjtalkshow]

The sidebar CTA at components/bounty-detail/bounty-detail-sidebar-cta.tsx shows a disabled "Raise a Dispute (Coming Soon)" button to eligible users. We have the dispute review page at app/dispute/[disputeId]/page.tsx and the GraphQL operations at lib/graphql/operations/admin-dispute.graphql, but no path to actually file a dispute from a bounty.

We need to enable the button, collect the reason and description, and route the user to the dispute review flow.

What to do

Add a useRaiseDispute mutation in hooks/use-bounty-application.ts accepting bountyId, reason (from DisputeReasonEnum), and description. On success it should return the new dispute ID and invalidate the bounty detail query.

Restore the dispute AlertDialog in bounty-detail-sidebar-cta.tsx:

• Drop the disabled prop on the trigger button so the dialog can open
• Wire the form (reason Select + description Textarea) through the new mutation
• On success, close the dialog, show a success toast, and redirect to /dispute/{newDisputeId}

The useCanRaiseDispute hook already gates the button visibility. No change needed there.

Acceptance criteria

• Eligible users (creator or participant on a bounty in IN_PROGRESS or UNDER_REVIEW) see an active Raise Dispute button
• Clicking it opens the existing AlertDialog with reason and description fields
• Submitting redirects to the dispute detail page
• Submitting with an empty reason or description keeps the dialog open and shows inline validation

Files

• components/bounty-detail/bounty-detail-sidebar-cta.tsx
• hooks/use-bounty-application.ts
• lib/graphql/operations/admin-dispute.graphql

[linear]

BOU-228

[coderabbitai]

🔗 Related PRs

#111 - Feat: implementation logic for single claim model [merged]
#116 - feat: Migrate useBounty detail hook to GraphQL [merged]
#117 - feat: add frontend hooks for submission mutations [merged]
#170 - Feature: Bounty Cancellation and Refund Flow [merged]
#201 - Feat/Dispute Resolution Workflow for Bounties [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[Nuel-ship-it]

@Nuel-ship-it has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to get assigned to this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Nuel-ship-it to this issue.

[od-hunter]

@od-hunter has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi can i be assigned this issue please? I've gone through the description and I'm up for the task. Kindly assign me please.

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

[drips-wave]

Congratulations, @od-hunter! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @od-hunter: 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 🌊

[Ishant5436]

Fixed in earlier commits