Assessing a Jira Issue for Relevance

Determine whether a Jira issue still applies to the current codebase. Fetch the ticket, locate the specific code path it describes, compare current behavior against the ticket's description, and return a verdict with evidence.

Workflow

Step 1: Fetch the Ticket and Its Context

Use get_issue with expand: ["renderedFields", "names"]. Extract:

• The specific problem or task: Read beyond the summary. The description, acceptance criteria, and replication steps are more precise. For bugs: what is the actual broken behavior and what is expected? For tasks: what specific code change is required?
• Technical identifiers: Method names, class names, file paths, API endpoint routes, UI strings that appear in source, config keys, feature flag names — anything named in the ticket that can be searched in code. Note these explicitly before moving on.
• Filed date: Used to scope git log searches.
• Repo scope evidence: Gather what the ticket says about where the code lives, and note how strong that evidence is. Do not settle on a repo here — Step 2 decides.
  • Strong: a literal repo name, a github.com/bitwarden/<repo> URL, or a linked PR/commit.
  • Weaker: team field, component labels, language or platform keywords, file paths in the description.

Also note these staleness signals from the ticket fields before moving on: