Jira Custom Fields That Actually Help

Every Jira instance I've inherited has had too many custom fields. Someone added a "Business Value" dropdown three years ago that nobody fills in. There's a "Risk Level" field with options nobody agreed on. Fields accumulate like sediment.

When I took over our Jira configuration, I stripped it back to essentials and added exactly five custom fields that earn their place.

The five fields worth keeping

1. Blocker Reason (text field). When a ticket moves to Blocked status, this field is required. Forces engineers to articulate what's blocking them, not just flag the status. It also gives me a queryable history of blockers for pattern analysis.

2. Dependency Link (linked issue). Jira has built-in issue links, but we created a specific "blocked by / blocks" link type with a custom filter. I have a dashboard showing all active dependency chains. When a dependency gets delayed, I see the downstream impact instantly.

3. Customer Impact (dropdown: High/Medium/Low/None). This drives our prioritization. When the backlog has 40 tickets, this field lets us sort by what actually matters to users, not just what's technically interesting.

4. Time in Status (calculated field). Auto-calculated time spent in each status. This feeds our cycle time analysis without requiring engineers to log time manually. Engineers hate time tracking. Automated status duration tracking gives me the same data without the friction.

5. Deploy Date (date field). When was this actually shipped to production? Not when it was marked Done — when it reached users. The gap between Done and Deployed is often where delivery hides.

What I removed

Story point fields on bug tickets. Priority fields that duplicated Customer Impact. A "Sprint Goal Alignment" dropdown nobody understood. Three different "Type" classifications. Every field that was filled in less than 50% of the time.

Jira should make decisions easier, not data entry longer. Every field should answer a question someone actually asks.