Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Knowledge Gaps: the + KB button does not pre-select the ticket on the KB page

Offen
#365 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@NathanTarbert arbeitet bereits daran.

Seit 12.10.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

bug

Summary

The + KB button on each row of the Knowledge Gaps page links to /kb?sourceTicket=<id>, but the KB page never reads that parameter. The click just opens the KB page with nothing selected, so the "jump straight to the KB with this ticket pre-selected" promise on the page and in the docs is not delivered.

Where

  • Link: app/(dashboard)/knowledge-gaps/page.tsx (the href={/kb?sourceTicket=${gap.id}} on each gap row).
  • Consumer that should read it: app/(dashboard)/kb/page.tsx (no sourceTicket handling today).
  • Docs that describe the behavior: content/docs/product/knowledge-gaps.mdx ("A + KB button to jump directly to the Knowledge Base with the ticket pre-selected").

Expected behavior

Opening the link should take the reviewer somewhere they can turn that gap into an article without hunting for the ticket.

Options

  1. Prefill into the review flow (recommended once the review queue is merged, see #362). Create or open a review item for that ticket and land on /kb?tab=review with it focused, so the reviewer edits the question and answer and approves. This reuses the existing approval path and its safeguards.
  2. Prefill a standalone add-article form (depends on the "Add context" follow-up).
  3. Change the button to link to the ticket page where the existing Promote to KB action lives, and update the docs to match.

Acceptance criteria

  • Clicking + KB on a gap leads to a place where that gap's question is ready to edit and publish
  • The KB page handles a missing, malformed, or other-org sourceTicket value without error and without revealing another org's data
  • knowledge-gaps.mdx describes what the button actually does
  • Test coverage for the parameter handling
Vorherrschende Sprache
TypeScript
Sterne
16
Forks
2
Ø Merge
7 Std. 22 Min.
Gemergte PRs (30 T.)
150

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus answerLoops/answerLoops

Alle Issues in answerLoops/answerLoops

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.