Custom Bug Fields

Customize Bug Tracking Around Your Workflow

Zunoy Custom Fields help dev and QA teams capture the exact details they need across bug reports, status changes, closure records, tags, and knowledge base articles. Add structured fields to your bug tracking workflow without forcing every team into the same process.

Start Customizing Fields

Free to start

No credit card required

Visual Bug Reporting

Multi-channel tracking

Full context from day one.

OVERVIEW

Built Around What Your Team Actually Tracks

Every team tracks bugs differently. QA teams may need test environment, build version, device type, or reproduction status. Developers may need affected module, linked PR, root cause, or regression risk. Product teams may care about customer impact, release blockers, or priority reason.With Zunoy Custom Fields, teams can add structured data to the places where bug context matters most, so reports are easier to triage, filter, resolve, and document.

Priority & Ownership

Track bug priority, status, severity, and ownership

Linked Issues

Connect linked bugs, sub-bugs, blockers, and duplicates

Saved Views

Use saved tabs and custom filters for faster reviews

Attachments & Activity

Keep comments, files, screenshots, and activity attached

Bug Lifecycle

Move every issue through a clear bug lifecycle

Workflow Views

Add Custom Fields Across the Bug Lifecycle

Every team tracks bugs differently. Zunoy works as a custom fields bug tracker that lets teams adapt fields, statuses, tags, and closure records without forcing every project into the same rigid process.

1

Bug Creation Form

Add fields to capture key details when a bug is first reported, such as affected module, build version, environment, customer impact, browser, device, or release.

2

Bug Closure and Resolution

Capture resolution details when a bug is closed, like root cause, fix version, verified-by, and regression risk, so closure records stay complete and auditable.

3

Status Transitions

Add fields that only appear at certain workflow stages, like a QA sign-off before Done or a rejection reason when a bug is declined.

4

Custom Tag Schemas

Define reusable tag sets per project so tagging stays consistent across teams instead of every reporter inventing their own labels.

5

Knowledge Base Articles

Link resolved bugs to knowledge base articles automatically, so recurring issues point straight to an existing fix or workaround.

CORE CAPABILITIES

Flexible Field Types for Bug Tracking

Choose the right field type based on the kind of information your team needs to collect.

Text Fields

Use short or long text fields for summaries, notes, environment details, reproduction comments, or resolution explanations.

Number Fields

Capture integers or decimal values such as version numbers, error counts, affected users, or effort estimates.

Date and DateTime

Track release dates, retest dates, due dates, deployment windows, or when an issue was first observed.

Dropdowns

Use single-select or multi-select dropdowns for components, platforms, modules, customers, test stages, or issue categories.

Checkboxes

Add simple yes/no fields for flags like regression tested, customer reported, hotfix required, or release blocker.

User Lists

Select one or multiple users for reviewers, QA owners, escalation contacts, or stakeholders.

URL and Link Fields

Attach links to pull requests, logs, dashboards, release notes, customer tickets, or external references.

Rich Text

Add formatted notes, tables, checklists, technical details, or longer resolution documentation.

User Lists

Select one or multiple users for reviewers, QA owners, escalation contacts, or stakeholders.

CORE CAPABILITIES

Required Fields

Make important fields mandatory so bug reports and closure records do not miss critical information.

Make Sure Nothing Critical Gets Skipped

Mark fields as mandatory so bug reports and closure records can't be saved without the details your team actually needs — severity, steps to reproduce, or root cause.

Turn fields on or off per project so a mobile QA project and a client support project don't share the same rigid form.

Define dropdown options, tags, or severity scales once and reuse them across every project instead of recreating the same list twice.

Surface a field only at the right stage of the bug lifecycle — root cause at closure, verification notes only after a fix is marked resolved.

Filter, sort, and group bugs by any custom field — module, customer tier, or affected browser — the same way you would with built-in fields.

Capture root cause, fix summary, and verification details in structured fields so closed bugs stay useful instead of just disappearing.

HOW IT WORKS

Create Once. Use Across Your Bug Workflow.

Once a custom field is created, it can appear across the bug tracking workflow wherever that information is useful.

Create a Custom Field

Choose the field name, type, options, and where it should appear in your workflow.

Add It to Bug Forms

Use the field in bug create or edit forms so reporters and teams capture the right context from the start.

Show It in Views

Display custom fields in Table view as columns, on Kanban cards as metadata, or in Card view as visible bug details.

Use It in Records

Carry key fields into knowledge base forms for root cause notes, fix summaries, verification, or prevention.

Create a Custom Field

Choose the field name, type, options, and where it should appear in your workflow.

Add It to Bug Forms

Use the field in bug create or edit forms so reporters and teams capture the right context from the start.

Show It in Views

Display custom fields in Table view as columns, on Kanban cards as metadata, or in Card view as visible bug details.

Use It in Records

Carry key fields into knowledge base forms for root cause notes, fix summaries, verification, or prevention.

Create a Custom Field

Choose the field name, type, options, and where it should appear in your workflow.

Add It to Bug Forms

Use the field in bug create or edit forms so reporters and teams capture the right context from the start.

Show It in Views

Display custom fields in Table view as columns, on Kanban cards as metadata, or in Card view as visible bug details.

Use It in Records

Carry key fields into knowledge base forms for root cause notes, fix summaries, verification, or prevention.

Create a Custom Field

Choose the field name, type, options, and where it should appear in your workflow.

Add It to Bug Forms

Use the field in bug create or edit forms so reporters and teams capture the right context from the start.

Show It in Views

Display custom fields in Table view as columns, on Kanban cards as metadata, or in Card view as visible bug details.

Use It in Records

Carry key fields into knowledge base forms for root cause notes, fix summaries, verification, or prevention.

Create a Custom Field

Choose the field name, type, options, and where it should appear in your workflow.

Add It to Bug Forms

Use the field in bug create or edit forms so reporters and teams capture the right context from the start.

Show It in Views

Display custom fields in Table view as columns, on Kanban cards as metadata, or in Card view as visible bug details.

Use It in Records

Carry key fields into knowledge base forms for root cause notes, fix summaries, verification, or prevention.

Analytics usage should be added only if confirmed in the product.

KEY BENEFITS

Why Custom Fields Matter in Bug Tracking

Once a custom field is created, it can appear across the bug tracking workflow wherever that information is useful.

Track

Cleaner Bug Reports

Capture the right details upfront so developers do not waste time asking for missing context.

Workspace

Faster QA Triage

Sort and review bugs by environment, build, platform, component, severity, customer impact, or release stage.

Team

Better Developer Handoffs

Give engineers structured information like affected module, reproduction status, linked PR, logs, and ownership.

Roles

Stronger Closure Process

Make sure every closed bug includes root cause, fix summary, QA verification, and prevention notes.

Permission

Consistent Team Workflows

Standardize how different teams report, update, and close bugs without turning the tracker into a rigid system.

FAQs

The things Developers actually ask.

What is a maintenance window?

A maintenance window is a scheduled period where monitoring checks pause during planned updates or fixes, preventing false downtime alerts.

Can I control which services are included?

Yes. You choose which monitors pause during the maintenance window, while unaffected services continue to run normally.

Can I notify customers in advance?

Yes. If you choose to make maintenance public, it can be shown on your status page so customers know what’s planned.

What if my work finishes earlier than planned?

You can end the maintenance window anytime. Checks restart instantly, and your status page updates accordingly.

Get started

Build Bug Reports Around Your Process

Use Zunoy Custom Fields to capture better bug context, standardize QA workflows, improve developer handoffs, and create cleaner resolution records.

Setup in seconds

Capture full bug context

Assign clear ownership

Timesheet included

Free tier available

Launch Your Bug Tracker
See Zunoy’s Whole Ecosystem >

Ask a question about Zunoy's products, pricing, or docs.

⌘K