Dataset Viewer
Auto-converted to Parquet Duplicate
Instruction
stringclasses
1 value
Input
stringlengths
82
415
Output
stringclasses
10 values
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0006317 Short_Description: Dfs Namespace Share Not Accessible Persistent Long_Description: Seth Acosta cannot access DFS Namespace due to share not accessible. The issue started today. The user followed standard troubleshooting steps and the issue persisted. This is blocking work. Contact email seth.acosta@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0023607 Short_Description: Page Issue On Page still Long_Description: Team event is tomorrow. Something here is not working though. still
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0009080 Short_Description: Power Bi Gateway Page Error On Save Web Client Long_Description: Morgan Collins cannot access Power BI Gateway due to page error on save. The issue started today. The user followed standard troubleshooting steps and the issue persisted. This is blocking work. Contact email morgan.collins@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0013912 Short_Description: Salesforce Integration Failing During Sync Long_Description: Melissa Lee cannot access Salesforce due to integration failing. The issue started yesterday. The user restarted the application and the device with no improvement. This is blocking work. Contact email melissa.lee@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0014281 Short_Description: Cisco Cucm No Audio On Calls Web Client Long_Description: Steven Trujillo cannot access Cisco CUCM due to no audio on calls. The issue started this morning. The user restarted the application and the device with no improvement. This is blocking work. Contact email steven.trujillo@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0007004 Short_Description: Windows File Server Share Not Accessible Persistent Long_Description: Brandon Dillon cannot access Windows File Server due to share not accessible. The issue started about an hour ago. The user waited and retried and the problem continued. The required action cannot be completed. Contact email brandon.dillon@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0005180 Short_Description: Qualys Policy Not Applied New Long_Description: Erica Terry cannot access Qualys due to policy not applied. The issue started earlier today. The user followed standard troubleshooting steps and the issue persisted. This is causing repeated interruptions. Contact email erica.terry@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0012889 Short_Description: Looker Studio Cannot Submit Form Yesterday Service Long_Description: Colin Silva cannot access Looker Studio due to cannot submit form. The issue started about an hour ago. The user cleared cache and cookies and tried again with the same result. The required action cannot be completed. Contact email colin.silva@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0002776 Short_Description: Cisco Anyconnect Vpn Tunnel Will Not Establish Client Long_Description: Jeremy Carlson cannot access Cisco AnyConnect due to vpn tunnel will not establish. The issue started yesterday. The user restarted the application and the device with no improvement. This is delaying tasks. Contact email jeremy.carlson@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0008929 Short_Description: Aws Alb Http 500 On Page Service Long_Description: Robert Hill cannot access AWS ALB due to http 500 on page. The issue started earlier today. The user followed standard troubleshooting steps and the issue persisted. This is delaying tasks. Contact email robert.hill@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0021164 Short_Description: Urgent still Long_Description: It fails sometimes and sometimes not. Kindly resolve. still
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0002897 Short_Description: Kubernetes Runner Offline Long_Description: Stephanie Campbell cannot access Kubernetes due to runner offline. The issue started today. The user followed standard troubleshooting steps and the issue persisted. This is blocking work. Contact email stephanie.campbell@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0006124 Short_Description: Jenkins Controller Build Timeout During Login Long_Description: Jasmine Butler cannot access Jenkins Controller due to build timeout. The issue started about an hour ago. The user waited and retried and the problem continued. This is causing repeated interruptions. Contact email jasmine.butler@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0019131 Short_Description: Problem random Long_Description: Contact me at admin at mail. Issue happens on submit. random
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0002124 Short_Description: Workday Profile Update Error Portal Long_Description: Jennifer Gardner cannot access Workday due to profile update error. The issue started yesterday. The user tested on wireless and wired and the behavior remained the same. This is causing repeated interruptions. Contact email jennifer.gardner@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0013582 Short_Description: Mongo Atlas Connection Refused During Upload Long_Description: Scott Marks cannot access Mongo Atlas due to connection refused. The issue started earlier today. The user restarted the application and the device with no improvement. The required action cannot be completed. Contact email scott.marks@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0020923 Short_Description: App Keeps Failing more Long_Description: Unhandled error status page bad request timeout maybe. more
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information; Unclear technical jargon without context
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0020876 Short_Description: Network Problem Portal Since Yesterday Long_Description: Cannot continue due to an error. No message is shown. repeat
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0005970 Short_Description: Dbt Job Failed Overnight Client Long_Description: Julian Garza cannot access dbt due to job failed overnight. The issue started today. The user waited and retried and the problem continued. This is causing repeated interruptions. Contact email julian.garza@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0006360 Short_Description: Oracle Db Database Authentication Error This Morning Long_Description: Corey Lin cannot access Oracle DB due to database authentication error. The issue started this morning. The user tested on wireless and wired and the behavior remained the same. This is delaying tasks. Contact email corey.lin@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0007297 Short_Description: Microsoft Defender Policy Not Applied Web Client Long_Description: Debra Palmer cannot access Microsoft Defender due to policy not applied. The issue started earlier today. The user followed standard troubleshooting steps and the issue persisted. This is delaying tasks. Contact email debra.palmer@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0008077 Short_Description: Mongodb Backup Failed Recurring Long_Description: Michael Barnett cannot access MongoDB due to backup failed. The issue started this morning. The user cleared cache and cookies and tried again with the same result. This is causing repeated interruptions. Contact email michael.barnett@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0006116 Short_Description: Zoom Phone Number Assignment Failed Desktop Client Long_Description: Jonathan Barton cannot access Zoom Phone due to number assignment failed. The issue started about an hour ago. The user tested on wireless and wired and the behavior remained the same. This is causing repeated interruptions. Contact email jonathan.barton@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0001901 Short_Description: Dbt Cloud Webhook Signature Invalid Observed Long_Description: Scott Hill cannot access dbt Cloud due to webhook signature invalid. The issue started yesterday. The user restarted the application and the device with no improvement. The required action cannot be completed. Contact email scott.hill@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0011856 Short_Description: Jira Cannot Submit Form After Update Long_Description: Barbara Patton cannot access Jira due to cannot submit form. The issue started earlier today. The user followed standard troubleshooting steps and the issue persisted. The required action cannot be completed. Contact email barbara.patton@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0019078 Short_Description: Unable To Proceed With Dashboard more Long_Description: Please fix. more
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0008996 Short_Description: Google Workspace Client Stuck On Loading Ongoing Long_Description: Karen Wells cannot access Google Workspace due to client stuck on loading. The issue started about an hour ago. The user restarted the application and the device with no improvement. This is causing repeated interruptions. Contact email karen.wells@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0012104 Short_Description: Cisco Cucm Voicemail Not Working Consistent Long_Description: Diana Hughes cannot access Cisco CUCM due to voicemail not working. The issue started today. The user cleared cache and cookies and tried again with the same result. The required action cannot be completed. Contact email diana.hughes@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0016591 Short_Description: Login Issue Account Randomly Long_Description: Pipeline crash execution rollback handler unknown state. more
Bad Incident No system or application identified; No user identity or contact information; Unclear technical jargon without context
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0000511 Short_Description: Nexus Repository Deployment Rollback Observed Long_Description: Melissa Taylor cannot access Nexus Repository due to deployment rollback. The issue started about an hour ago. The user followed standard troubleshooting steps and the issue persisted. The required action cannot be completed. Contact email melissa.taylor@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0014632 Short_Description: Successfactors Approval Delayed Ongoing Long_Description: Travis Mills cannot access SuccessFactors due to approval delayed. The issue started about an hour ago. The user waited and retried and the problem continued. This is delaying tasks. Contact email travis.mills@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0021843 Short_Description: Not Working Tool Sometimes ongoing Long_Description: Please reset the cafeteria coffee machine account. ongoing
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0019837 Short_Description: Error Seen again Long_Description: I liked the new office wallpaper. Login might be failing. again
Bad Incident Content not related to an IT incident; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0012300 Short_Description: Github Enterprise Artifact Not Found Consistent Long_Description: Ronald Brooks cannot access GitHub Enterprise due to artifact not found. The issue started earlier today. The user cleared cache and cookies and tried again with the same result. This is delaying tasks. Contact email ronald.brooks@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0009625 Short_Description: Splunk Policy Not Applied Recurring Long_Description: Patrick Flores cannot access Splunk due to policy not applied. The issue started today. The user cleared cache and cookies and tried again with the same result. This is blocking work. Contact email patrick.flores@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0022702 Short_Description: Unable To Proceed On Client repeat Long_Description: The page does not load however it loads after some time and also not. repeat
Bad Incident Contradictory statements; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0001582 Short_Description: Slow Queries In Elasticsearch Long_Description: Kimberly Adams cannot access Elasticsearch due to slow queries. The issue started about an hour ago. The user followed standard troubleshooting steps and the issue persisted. This is blocking work. Contact email kimberly.adams@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0002332 Short_Description: Gateway Timeout In Aws Cloudfront Long_Description: Tiffany Christensen cannot access AWS CloudFront due to gateway timeout. The issue started about an hour ago. The user waited and retried and the problem continued. This is causing repeated interruptions. Contact email tiffany.christensen@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0023942 Short_Description: Issue random Long_Description: Open close reopen and still the same. Tried everything. random
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0017816 Short_Description: Need Help On Tool more Long_Description: Operation cannot be completed at this time. more
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0004248 Short_Description: Postgresql Replica Lag Yesterday Long_Description: Brandon Turner cannot access PostgreSQL due to replica lag. The issue started earlier today. The user restarted the application and the device with no improvement. The required action cannot be completed. Contact email brandon.turner@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0007137 Short_Description: Genesys Number Assignment Failed During Upload Long_Description: Charles Rogers cannot access Genesys due to number assignment failed. The issue started about an hour ago. The user tested on wireless and wired and the behavior remained the same. This is causing repeated interruptions. Contact email charles.rogers@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0017361 Short_Description: Need Help With Tool Long_Description: Clicked submit then refresh then back then forward and it failed. random
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0013830 Short_Description: Akamai Kona Origin Unreachable During Login Long_Description: Brandy Watkins cannot access Akamai Kona due to origin unreachable. The issue started today. The user cleared cache and cookies and tried again with the same result. This is delaying tasks. Contact email brandy.watkins@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0007489 Short_Description: Windows Desktop Driver Missing Client Long_Description: Nicole Boyle cannot access Windows desktop due to driver missing. The issue started today. The user cleared cache and cookies and tried again with the same result. This is delaying tasks. Contact email nicole.boyle@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0004371 Short_Description: Pki Agent Not Reporting Observed Long_Description: Debra Hall cannot access PKI due to agent not reporting. The issue started today. The user followed standard troubleshooting steps and the issue persisted. This is delaying tasks. Contact email debra.hall@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0023542 Short_Description: Page Issue Since Yesterday ongoing Long_Description: Authentication exception with stack overflow null pointer thread pool. ongoing
Bad Incident No system or application identified; No user identity or contact information; Unclear technical jargon without context
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0020974 Short_Description: Issue With Form ongoing Long_Description: Pipeline crash execution rollback handler unknown state. ongoing
Bad Incident No system or application identified; No user identity or contact information; Unclear technical jargon without context
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0000727 Short_Description: Datadog Policy Not Applied Client Long_Description: Bradley Cooper cannot access Datadog due to policy not applied. The issue started yesterday. The user cleared cache and cookies and tried again with the same result. This is causing repeated interruptions. Contact email bradley.cooper@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0018437 Short_Description: Please Fix Website Today Long_Description: Please reset the cafeteria coffee machine account. still
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0003229 Short_Description: Macos Laptop Unexpected Blue Screen Portal Long_Description: Laura Briggs cannot access macOS laptop due to unexpected blue screen. The issue started earlier today. The user waited and retried and the problem continued. This is delaying tasks. Contact email laura.briggs@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0022376 Short_Description: Support Needed With Dashboard random Long_Description: na na na issue details will be added later. random
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0009282 Short_Description: Elasticsearch Replica Lag Persistent Long_Description: Randy Watts cannot access Elasticsearch due to replica lag. The issue started this morning. The user cleared cache and cookies and tried again with the same result. This is delaying tasks. Contact email randy.watts@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0003706 Short_Description: Power Bi Gateway Cannot Submit Form Portal Long_Description: Louis Moore cannot access Power BI Gateway due to cannot submit form. The issue started this morning. The user followed standard troubleshooting steps and the issue persisted. This is delaying tasks. Contact email louis.moore@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0022345 Short_Description: Help Needed Often more Long_Description: General error occurs while doing work. Please check. more
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0002755 Short_Description: Nexus Iq Pipeline Failing Yesterday Long_Description: Sandra Todd cannot access Nexus IQ due to pipeline failing. The issue started earlier today. The user cleared cache and cookies and tried again with the same result. This is delaying tasks. Contact email sandra.todd@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0015360 Short_Description: Form Not Working Application After Update Long_Description: Form submit returns an error without code. I tried clearing cache and rebooting. Still blocked. ongoing
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0015812 Short_Description: Not Working random Long_Description: Pipeline crash execution rollback handler unknown state. random
Bad Incident No system or application identified; No user identity or contact information; Unclear technical jargon without context
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0019926 Short_Description: Please Fix Portal Today Long_Description: Something broken reach me later. Login breaks. repeat
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0014649 Short_Description: Jenkins Deployment Rollback Since Morning Long_Description: Valerie Baxter cannot access Jenkins due to deployment rollback. The issue started yesterday. The user waited and retried and the problem continued. This is causing repeated interruptions. Contact email valerie.baxter@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0021414 Short_Description: Request Page Today Long_Description: Client error code something something system failure. again
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0018380 Short_Description: Something Went Wrong With Profile again Long_Description: Open close reopen and still the same. Tried everything. again
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0017722 Short_Description: Urgent more Long_Description: Form submit returns an error without code. I tried clearing cache and rebooting. Still blocked. more
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0022151 Short_Description: Network Problem With System random Long_Description: Team event is tomorrow. Something here is not working though. random
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0014342 Short_Description: Radius Radius Authentication Failing Yesterday Long_Description: Jeremiah Walters cannot access RADIUS due to radius authentication failing. The issue started today. The user followed standard troubleshooting steps and the issue persisted. This is delaying tasks. Contact email jeremiah.walters@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0020408 Short_Description: App Keeps Failing repeat Long_Description: Unable to proceed past the sign in screen. No specific error. Started today after normal use. repeat
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0002889 Short_Description: Elasticsearch Too Many Connections Portal Long_Description: Amy Foster cannot access Elasticsearch due to too many connections. The issue started this morning. The user restarted the application and the device with no improvement. This is blocking work. Contact email amy.foster@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0019294 Short_Description: Please Fix With Website ongoing Long_Description: Operation cannot be completed at this time. ongoing
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0015769 Short_Description: Problem With Service Long_Description: Unable to proceed past the sign in screen. No specific error. Started today after normal use. ongoing
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0003010 Short_Description: Nexus Iq Build Timeout Consistent Long_Description: Lindsay Smith cannot access Nexus IQ due to build timeout. The issue started this morning. The user tested on wireless and wired and the behavior remained the same. This is blocking work. Contact email lindsay.smith@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0007677 Short_Description: F5 Big Ip Origin Unreachable Persistent Long_Description: Cory Perez cannot access F5 BIG IP due to origin unreachable. The issue started yesterday. The user tested on wireless and wired and the behavior remained the same. The required action cannot be completed. Contact email cory.perez@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0018677 Short_Description: Login Issue Today random Long_Description: tbd to be updated cannot proceed now. random
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information; Placeholder or noise text
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0011851 Short_Description: Redis Cache Connection Refused Mobile App Long_Description: Samuel Mason cannot access Redis Cache due to connection refused. The issue started about an hour ago. The user restarted the application and the device with no improvement. This is delaying tasks. Contact email samuel.mason@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0007988 Short_Description: Looker Studio Access Request Pending Intermittent Long_Description: Lisa Larson cannot access Looker Studio due to access request pending. The issue started this morning. The user followed standard troubleshooting steps and the issue persisted. This is blocking work. Contact email lisa.larson@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0018723 Short_Description: Form Not Working On Tool random Long_Description: It fails sometimes and sometimes not. Kindly resolve. random
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0005741 Short_Description: Nfs Share File Sync Conflicts Desktop Client Long_Description: Karen Castaneda cannot access NFS Share due to file sync conflicts. The issue started about an hour ago. The user tested on wireless and wired and the behavior remained the same. The required action cannot be completed. Contact email karen.castaneda@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0017368 Short_Description: Access Issue On Portal ongoing Long_Description: Please reset the cafeteria coffee machine account. ongoing
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0012165 Short_Description: Corporate Wi Fi Radius Authentication Failing Observed Long_Description: Andrew Allen cannot access corporate Wi Fi due to radius authentication failing. The issue started earlier today. The user followed standard troubleshooting steps and the issue persisted. The required action cannot be completed. Contact email andrew.allen@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0020160 Short_Description: Form Not Working ongoing Long_Description: Open close reopen and still the same. Tried everything. ongoing
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0000824 Short_Description: Akamai Gateway Timeout Long_Description: Priscilla Jackson cannot access Akamai due to gateway timeout. The issue started about an hour ago. The user followed standard troubleshooting steps and the issue persisted. This is blocking work. Contact email priscilla.jackson@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0011210 Short_Description: Artifactory Runner Offline During Upload Long_Description: Jon Williams cannot access Artifactory due to runner offline. The issue started yesterday. The user waited and retried and the problem continued. This is causing repeated interruptions. Contact email jon.williams@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0012852 Short_Description: Sharepoint Client Stuck On Loading Ongoing Long_Description: Aaron Black cannot access SharePoint due to client stuck on loading. The issue started today. The user cleared cache and cookies and tried again with the same result. This is causing repeated interruptions. Contact email aaron.black@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0016179 Short_Description: Email Issue With Website ongoing Long_Description: Authentication exception with stack overflow null pointer thread pool. ongoing
Bad Incident No system or application identified; No user identity or contact information; Unclear technical jargon without context
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0012694 Short_Description: Bitlocker Print Queue Stuck Yesterday Long_Description: Heather Velasquez cannot access BitLocker due to print queue stuck. The issue started yesterday. The user tested on wireless and wired and the behavior remained the same. The required action cannot be completed. Contact email heather.velasquez@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0021610 Short_Description: Access Issue Form Sometimes Long_Description: na na na issue details will be added later. still
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0009206 Short_Description: Github Actions Webhook Signature Invalid During Meeting Long_Description: Kyle Carey cannot access GitHub Actions due to webhook signature invalid. The issue started this morning. The user cleared cache and cookies and tried again with the same result. The required action cannot be completed. Contact email kyle.carey@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0004304 Short_Description: Postgresql Replica Lag Long_Description: Amy Stevens cannot access PostgreSQL due to replica lag. The issue started earlier today. The user followed standard troubleshooting steps and the issue persisted. This is delaying tasks. Contact email amy.stevens@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0017663 Short_Description: Support Needed Profile still Long_Description: na na na issue details will be added later. still
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0020875 Short_Description: Email Issue On Account ongoing Long_Description: File upload fails around halfway every time. Retried on another browser with the same result. ongoing
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0020148 Short_Description: Issue On Account again Long_Description: Clicked submit then refresh then back then forward and it failed. again
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0024205 Short_Description: Something Went Wrong still Long_Description: Open close reopen and still the same. Tried everything. still
Bad Incident No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0011925 Short_Description: Zoom Phone Voicemail Not Working During Meeting Long_Description: Natalie Patel cannot access Zoom Phone due to voicemail not working. The issue started today. The user followed standard troubleshooting steps and the issue persisted. This is blocking work. Contact email natalie.patel@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0016655 Short_Description: Unable To Proceed On Account repeat Long_Description: Please fix. repeat
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0008723 Short_Description: Azure Blob Storage Restore Request Desktop Client Long_Description: Amber Tran cannot access Azure Blob Storage due to restore request. The issue started earlier today. The user cleared cache and cookies and tried again with the same result. This is causing repeated interruptions. Contact email amber.tran@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0015993 Short_Description: Error Seen On Page Long_Description: Issue persists. again
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0014229 Short_Description: Dbt Query Timeout Recurring Long_Description: Heather King cannot access dbt due to query timeout. The issue started earlier today. The user cleared cache and cookies and tried again with the same result. The required action cannot be completed. Contact email heather.king@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0011856 Short_Description: Zoom Phone Pstn Unavailable During Upload Long_Description: Samantha Hicks cannot access Zoom Phone due to pstn unavailable. The issue started about an hour ago. The user waited and retried and the problem continued. This is causing repeated interruptions. Contact email samantha.hicks@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0007647 Short_Description: Jenkins Webhook Signature Invalid Web Client Long_Description: Philip Wiley cannot access Jenkins due to webhook signature invalid. The issue started yesterday. The user cleared cache and cookies and tried again with the same result. This is delaying tasks. Contact email philip.wiley@acme.example.
Good Incident Complete identity system reason and contact provided
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0023177 Short_Description: Need Help more Long_Description: Please fix. more
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
Classify the incident. Respond with exactly two lines: Line 1: Good Incident or Bad Incident Line 2: A concise reason. If Bad Incident, include 'Needed: ...' listing missing items.
Incident_Number: INC0023942 Short_Description: Problem On Page more Long_Description: Issue seen. Use my phone maybe. Need help. more
Bad Incident Description too short or vague; No system or application identified; No user identity or contact information
End of preview. Expand in Data Studio
README.md exists but content is empty.
Downloads last month
9