issue
Stores information about reported issues, including details on bugs, enhancements, or other reported problems.
Columns
| Name | Type | References | Description |
| assigned | String | The user or team assigned to resolve the issue. This indicates responsibility for addressing and closing the issue. | |
| autoname | Boolean | Indicates whether the issue is automatically named based on predefined rules or requires manual naming. | |
| buildbroken | String | The build version in which the issue was first identified as a problem or defect, tracking when a regression or bug was introduced. | |
| buildfixed | String | The build version in which the issue was resolved. Provides insight into when a bug was fixed and in which release it was addressed. | |
| buildtarget | String | The intended build version in which the issue is expected to be fixed, which helps in planning and tracking issue resolution. | |
| createddate | Datetime | The timestamp indicating when the issue was first logged, which is useful for tracking the age and time to resolution of issues. | |
| customform | String | The specific form used for capturing the issue details, categorizing issues based on different reporting templates. | |
| datereleased | String | The date when the issue fix was officially released as part of a build or version. | |
| emailassignee | Boolean | Indicates whether an email notification should be sent to the assigned user when the issue is updated, keeping stakeholders informed. | |
| emailcells | String | A list of specific email addresses or distribution lists notified about changes to the issue, ensuring relevant parties stay updated. | |
| emailemployees | String | Comma-separated list of employee email addresses notified about issue updates, ensuring key personnel are informed. | |
| externalabstract | String | A high-level summary of the issue meant for external stakeholders or customers, providing a non-technical description of the problem. | |
| externaldetails | String | A detailed explanation of the issue for external stakeholders, including impact and any relevant background information. | |
| externalid | String | A unique identifier for the issue in external systems, facilitating integration with third-party tracking tools or customer support portals. | |
| isreviewed | Boolean | Indicates whether the issue has been reviewed for accuracy, completeness, and validity, which helps in issue triage and prioritization. | |
| isshowstopper | Boolean | The issue is identified as a critical blocker that must be resolved before release or deployment to ensure further progress. | |
| issueabstract | String | A brief summary of the issue, including key details such as symptoms, affected areas, and impact, which is useful for quick reference. | |
| issuenumber | String | A unique identifier assigned to the issue within the system is used for tracking and referencing specific issues. | |
| issuestatus | String | The current status of the issue which indicates the stage of resolution, such as Open, In Progress, Resolved, or Closed. | |
| issuetags | String | A comma-separated list of keywords or labels assigned to the issue for categorization and easy searchability. | |
| issuetype | String | The classification of the issue, such as Bug, Enhancement, Feature Request, or Task, which helps in managing different types of issues. | |
| item | String | The specific product, module, or component affected by the issue, which helps in pinpointing the source of the problem. | |
| lastmodifieddate | Datetime | The timestamp of the last update to the issue record, which is useful for tracking recent changes and updates. | |
| module | String | The software module or functional area where the issue occurs, categorizing and assigning issues to the right team. | |
| newdetails | String | Additional details about the issue that have been recently updated or discovered, providing more context for resolution. | |
| priority | String | The urgency level of the issue, typically ranging from Low to Critical, prioritizing resolution efforts. | |
| product | String | The specific product or service related to the issue, filtering issues by product category. | |
| productteam | String | The team responsible for the affected product or feature, directing issues to the right group for resolution. | |
| reportedby | String | The user or entity that initially reported the issue, providing accountability and contact information for follow-ups. | |
| reproduce | String | Steps to reproduce the issue, including environment details and any necessary configurations essential for debugging and resolution. | |
| reviewer | String | The individual or team responsible for reviewing the issue before it is marked as resolved or closed, ensuring quality control. | |
| severity | String | The impact level of the issue, often categorized as Minor, Major, or Critical, assessing risk and prioritization. | |
| source | String | The origin of the issue report, such as Customer Feedback, Internal Testing, or Automated Monitoring, helps in tracking issue sources. | |
| versionbroken | String | The software version where the issue was first identified as a problem, which is useful for regression analysis. | |
| versionfixed | String | The software version where the issue was resolved helps to track when fixes are deployed. | |
| versiontarget | String | The software version targeted for fixing the issue. Helps align issue resolution with release planning. |