The list of team names that are associated with this bug record. Each name identifies a team with access permissions for viewing or managing the record.

The identifier (Id) of the team set that controls access to this bug record. The team set determines which users or groups can view and update the record.

The Id of the user who is assigned to resolve or manage this bug. This field is used for ownership and accountability tracking.

The name of the user who is assigned to this bug record. This field provides a readable reference for the Assigned_User_Id field.

The visible reference number that is used to track and identify the bug. This number is typically displayed to users and included in defect communications.

The total number of business hours that are required to resolve this issue. This field supports service-level reporting and performance analysis.

A record of comments that are associated with this bug. This field supports collaboration and provides historical context for troubleshooting.

The unique Id of the user who created this bug record. This field supports auditing and origin tracking.

The name of the user who created this bug record. This field provides a readable reference for the Created_By field.

The date and time when this bug record was created in the system. This field supports lifecycle auditing and historical tracking.

The date and time when this bug record was most recently modified. This field enables users to identify when updates occur.

A Boolean field that returns a value of 'true' when the bug record is marked for deletion. It returns a value of 'false' when the record remains active. This field supports soft-delete workflows and record recovery.

A full descriptive explanation of the bug, including context, symptoms, and relevant supporting information. This field supports thorough documentation and troubleshooting.

The release version in which this bug is corrected. This field provides traceability for patch deployment and regression management.

The name of the software release that corresponds to the value in the Fixed_In_Release field. This field provides a readable reference for reporting and communication.

The date and time by which follow-up action should occur for this bug. This field supports workflow, reminders, and escalation timing.

A Boolean field that returns a value of 'true' when the current user is following this bug to receive updates. It returns a value of 'false' when the user is not subscribed.

The software release in which this bug first appears. This field helps identify regression sources and release-based defect patterns.

The total number of calendar hours that are required to resolve this issue. This field differs from the Business_Hours_to_Resolution field by including non-business time in the calculation.

The Id for this bug record. This field ensures that the record can be referenced reliably across related modules and processes.

A Boolean field that returns a value of 'true' when the bug is escalated to a higher priority or support tier. It returns a value of 'false' when no escalation is currently active.

The list of fields that are locked from modification for this bug. This field ensures that key data remains consistent after review or approval.

The name of the user who most recently modified this bug record. This field provides a readable reference for the Modified_User_Id field.

The Id of the user who most recently modified this bug record. This field supports audit tracking of update responsibility.

A Boolean field that returns a value of 'true' when the current user marks this bug record as a favorite. It returns a value of 'false' when the record is not marked as a favorite.

The short descriptive title of the bug. This field is used in lists, dashboards, and search results for quick identification.

A Boolean field that returns a value of 'true' when the bug is awaiting processing or system action. It returns a value of 'false' when no pending system operation exists.

A Boolean field that returns a value of 'true' when this bug is visible to portal users. It returns a value of 'false' when the record is restricted to internal users.

The priority rating of this issue, which is used to determine troubleshooting urgency and resource allocation.

The functional area or product category in which the bug is discovered. Example categories include 'Accounts', 'Contacts', or 'Leads'. This field supports pattern analysis and ownership routing.

The name of the release that is associated with this bug. This field provides a readable reference for release-based tracking and reporting.

A description of how the issue is resolved. This field can indicate changes, fixes, or determinations that are made during resolution.

The date and time when the bug is resolved. This field supports trend analysis and resolution time reporting.

The source through which the bug is reported (for example, 'web submission', 'internal entry', or 'email-based creation'). This field helps identify the origin of the issue.

The unique Id of the related source record, if it is applicable. This field is used when the bug is linked to an external or integrated system.

Additional metadata that is associated with the bug source. This field can contain contextual attributes that support reporting or integration tracing.

The classification of the source entity for the bug (for example, 'user', 'external system', or 'automated process'). This field is used to interpret the value in the Source_Id and Source_Meta fields.

The current status of the bug (for example, 'New', 'In Progress', or 'Resolved). This field supports workflow routing and progress tracking.

The synchronization key that links this bug record to external systems or replication processes. This field ensures consistent record identity across integrations.

A tag or label that is associated with this bug for categorization and search filtering. This field helps group issues for analysis and review.

The number of teams that have access to this bug record. This value is derived from the associated team set and is used in access management reporting.

The Id of the primary team that is assigned to this bug. The team assignment determines initial visibility and responsibility.

The name of the primary team that is associated with this bug. This field provides a readable reference for the Team_Id field.

The Id of the team set that controls access to this bug record. A team set can include multiple teams that share access permissions.

The classification of the issue (for example, 'defect' or 'enhancement request'). This field supports filtering and reporting by issue type.

The follow-up deadline that is displayed in the widget-based user interface. This field provides a quick reference for time-sensitive actions.

A free-form text log that records investigative steps, troubleshooting actions, and resolution activities for the bug. This field supports collaboration and historical review.