US20190362291A1 - Generating and publishing a problem ticket - Google Patents
Generating and publishing a problem ticket Download PDFInfo
- Publication number
- US20190362291A1 US20190362291A1 US15/989,346 US201815989346A US2019362291A1 US 20190362291 A1 US20190362291 A1 US 20190362291A1 US 201815989346 A US201815989346 A US 201815989346A US 2019362291 A1 US2019362291 A1 US 2019362291A1
- Authority
- US
- United States
- Prior art keywords
- ticket
- problem ticket
- user
- computer
- additional information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
- G06Q10/063112—Skill-based matching of a person or a group to a task
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/77—Software metrics
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N3/00—Computing arrangements based on biological models
- G06N3/02—Neural networks
- G06N3/08—Learning methods
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0635—Risk analysis of enterprise or organisation activities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0769—Readable error formats, e.g. cross-platform generic formats, human understandable formats
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N3/00—Computing arrangements based on biological models
- G06N3/02—Neural networks
- G06N3/04—Architecture, e.g. interconnection topology
- G06N3/045—Combinations of networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
- G06Q10/063114—Status monitoring or status determination for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06316—Sequencing of tasks or work
Definitions
- the present invention relates in general to generating and publishing a problem ticket to allow users to collaboratively resolve a problem. More specifically, the present invention can relate to a system that enables users to generate and publish a problem ticket that describes a problem that is encountered by the users in the course of developing software, for example.
- a team of users can work together to conceive, describe, design, program, and test one or more software components.
- a user can encounter a technical problem that requires the attention of another qualified user to resolve.
- the user that encounters the problem can generate a report such as, for example, a problem ticket to describe the characteristics of the problem and the circumstances surrounding the problem.
- the qualified user can attempt to reproduce the problem so that the problem can be resolved.
- a computer-implemented method includes generating, by a processor of a problem-tracking system, a problem ticket.
- the problem ticket describes a problem encountered by a first user, and the problem ticket is assigned to at least one qualified user to resolve.
- the method also includes receiving additional information relating to the problem from at least one second user.
- the method also includes storing the received additional information in association with the problem ticket. The receiving and the storing of the additional information occurs while the problem ticket is waiting to be resolved by the at least one qualified user.
- the method also includes providing the stored received additional information and the problem ticket to the at least one qualified user.
- a computer system includes a memory.
- the computer system can also include a processor system communicatively coupled to the memory.
- the processor system is configured to perform a method including generating a problem ticket.
- the problem ticket describes a problem encountered by a first user, and the problem ticket is assigned to at least one qualified user to resolve.
- the method also includes receiving additional information relating to the problem from at least one second user.
- the method also includes storing the received additional information in association with the problem ticket. The receiving and the storing of the additional information occurs while the problem ticket is waiting to be resolved by the at least one qualified user.
- the method also includes providing the stored received additional information and the problem ticket to the at least one qualified user.
- a computer program product includes a computer-readable storage medium having program instructions embodied therewith.
- the program instructions are readable by a processor system of a problem-tracking system to cause the processor system to generate a problem ticket.
- the problem ticket describes a problem encountered by a first user, and the problem ticket is assigned to at least one qualified user to resolve.
- the processor system can also be caused to receive additional information relating to the problem from at least one second user.
- the processor system can also be caused to store the received additional information in association with the problem ticket. The receiving and the storing of the additional information occurs while the problem ticket is waiting to be resolved by the at least one qualified user.
- the processor system can also be caused to provide the stored received additional information and the problem ticket to the at least one qualified user.
- FIG. 1 illustrates a process for generating and publishing a problem ticket in accordance with one or more embodiments of the invention
- FIG. 2 depicts a flowchart of a method in accordance with one or more embodiments of the invention
- FIG. 3 depicts a high-level block diagram of a computer system, which can be used to implement one or more embodiments of the invention.
- FIG. 4 depicts a computer program product, in accordance with an embodiment of the invention.
- compositions comprising, “comprising,” “includes,” “including,” “has,” “having,” “contains” or “containing,” or any other variation thereof, are intended to cover a non-exclusive inclusion.
- a composition, a mixture, process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but can include other elements not expressly listed or inherent to such composition, mixture, process, method, article, or apparatus.
- connection can include an indirect “connection” and a direct “connection.”
- One or more embodiments are directed to generating and publishing a problem ticket to resolve a problem. After the problem ticket is generated, at least one specific qualified team member can be assigned to resolve the problem. While the generated problem ticket is waiting to be addressed by the qualified team member, the problem ticket can be published on an interface that allows other team members to collaboratively provide additional/supplemental information that can possibly assist the qualified team member in solving the problem. As such, different team members who work on a project together can use a system of one or more embodiments to track and resolve problems which arise in the course of completing the project. For example, in one embodiment of the present invention, a software development team can track and resolve problems which arise in the course of developing software.
- the user can report the problem by generating an indication of the problem. For example, the user can generate a problem ticket, where the problem ticket describes the presence of the problem and describes characteristics of the problem.
- the problem tickets can be ordered within a queue, and each problem ticket can be assigned to one or more qualified users to resolve. Each problem ticket then remains within the queue until the qualified team member is able to resolve the problem that is associated with each problem ticket.
- the problem ticket when a problem ticket is awaiting to be resolved by the qualified user, the problem ticket is merely waiting to be addressed by the qualified user, and thus the problem ticket does not progress toward resolution during this time.
- the conventional approaches do not use this waiting time in a productive manner that progresses the problem ticket toward resolution.
- users can inadvertently submit incomplete information when generating the problem ticket. For example, the information that is submitted by the user may not be sufficient for resolving the problem of the ticket. Further, the system of the conventional approaches can possibly prompt the user to submit details that are not relevant to resolving the problem of the problem ticket.
- the problem tickets that are generated by the conventional approaches generally await to be serviced by the assigned qualified user, without progressing toward resolution during this waiting time.
- the problem tickets of the conventional approaches typically include insufficient or irrelevant information for solving the problem of the problem ticket.
- the qualified user that is assigned to solve the problem ticket receives and reviews the insufficient and irrelevant information that is included with the problem ticket, the qualified user can then become frustrated when attempting to resolve the problem that is associated with the problem ticket.
- one or more embodiments can enable users to provide additional/supplemental information that is to be included with a problem ticket while the problem ticket is waiting to be resolved by the qualified user.
- additional/supplemental information that can be useful to the qualified user who is ultimately assigned to solve the problem of the ticket.
- the qualified user can refer to the supplemental information to resolve the problem of the problem ticket.
- a team of users can work together to develop a software application.
- a problem arises, and the problem produces an error code relating to a database that is used by the software application.
- a user can then generate a problem ticket that describes the problem and that describes the associated error code.
- a different user such as, for example, a database expert can review the problem ticket and the database expert can possibly submit some supplementary information relating to the error code.
- the qualified user who is assigned to resolve the problem ticket
- reviews the problem ticket the qualified user can also review the supplementary information relating to the error code.
- a user can use the system of one or more embodiments to generate a problem ticket.
- the user submits information that describes the problem.
- the user who generates the problem ticket can include information in the form of textual information or in the form of captured imagery information.
- the captured imagery information can be in the form of pictures or video.
- the pictures or video can correspond to a screenshot of the encountered problem.
- the user who generates the problem ticket can capture and submit information to be included with the problem ticket by using the user's mobile device.
- the problem ticket can be assigned to at least one qualified user to resolve the problem.
- the system can also publish the problem ticket to a platform that is accessible by other users.
- the other users can collaboratively contribute information to the published problem ticket.
- the problem ticket can be fit into one or more categories/tags that exist on the platform, as discussed in more detail below.
- the categories/tags that are associated with a problem ticket can initially be submitted by the user who generated the problem ticket.
- other users can also assign categories/tags to the problem ticket, and a cognitive system of one or more embodiments can also assign categories/tags to the problem ticket.
- the platform upon which the problem ticket is published can be organized in accordance with different categories and/or different tags, which can correspond to the different categories/tags that are assigned to the problem tickets.
- the platform can be organized around different technical categories/tags that relate to different programming languages, different entity names, different operating systems, different error types, different application types, different functions, different ways to utilize memory, etc.
- the categories/tags that are used by the platform can correspond to categories/tags that that are used by other social media platforms, online project hosting wikis, blogs, forums, and other technical websites. Therefore, a user who seeks to help resolve problem tickets that are published on the platform can be directed to categories/tags that correspond to the user's areas of expertise, and thus the user can contribute information relating to problem tickets that are within the user's area of expertise.
- the different users can assign different categories and/or tags to the published problem ticket. Although these users can be users who are unable to resolve the problem themselves, they can still provide information that can be helpful to the qualified user who is assigned to ultimately resolve the problem.
- the system of one or more embodiments can include automated tools that assign categories and/or tags to the problem ticket. For example, if one or more users have submitted imagery to be included with the problem ticket, an automated cognitive tool can categorize the submitted imagery via pattern matching and/or machine learning.
- the automated cognitive tool can be implemented as a convolutional neural network, for example. Therefore, the submitted imagery can enable the problem ticket to be associated with one or more categories by the system of one or more embodiments.
- One or more embodiments can also perform optical character recognition on the submitted imagery to determine categories, tags, and/or keywords, for example.
- One or more embodiments can also determine keywords based on textual information that has been submitted for the problem ticket. These keywords can then be associated with the problem ticket.
- the submitted textual information can also be configured to be searchable by other users.
- the system of one or more embodiments can compare the imagery submitted with a problem ticket against other imagery that may be able to help provide resolution or additional context to the problem. Specifically, one or more embodiments can determine similarities between the imagery submitted with the problem ticket and other imagery that may be able to help provide resolution/context. For example, if the imagery of a problem ticket matches a previous image that was previously published on the platform, then one or more embodiments can determine whether the previous image was associated with any categories/tags, and these possible categories/tags of the previous image can also be assigned to the current problem ticket.
- the problem ticket can be analyzed using cognitive tools to extract any other textual clues or image context that are present within the problem ticket. The extracted textual clues and/or image context can then be provided to users in order to help the users to identify key elements within the problem ticket.
- the system of one or more embodiments can also use cognitive functionality to leverage machine-learning and/or pattern-matching abilities. By leveraging these abilities, one or more embodiments can also automate certain aspects of submitting information for the ticket. For example, by analyzing information that has been included with the problem ticket, one or more embodiments can determine information such as, but not limited to, an operating system that the user is using, the relevant software that the user is using, a relevant program version of the software that is being utilized, an error code that has been encountered, etc. Such determined information can also be automatically included with the problem ticket. As such, one or more embodiments can allow a user to avoid the process of entering certain data, where the user can consider the data-entry process of such data to be a tedious process.
- One or more embodiments can use Application Program Interfaces (APIs) and/or web services to extract entity names from the information that is included with the problem ticket. These extracted entity names can be used to categorize/tag the problem ticket when publishing the problem ticket upon the above-described platform.
- APIs Application Program Interfaces
- One or more embodiments can extract entity names from Uniform Resource Locators (URLs), from Hypertext Markup Language (HTML) files, and from textual content.
- URLs Uniform Resource Locators
- HTML Hypertext Markup Language
- One or more embodiments can extract meta-data from the information that is included with the problem ticket. The extracted meta-data can be in Extensible Markup Language (XML) and/or JavaScript Object Notation (JSON) formats.
- XML Extensible Markup Language
- JSON JavaScript Object Notation
- the system of one or more embodiments can compare the extracted information against an aggregation of information that corresponds to previous error messages and previous searches.
- the system can compare the locations, the inputs, the position, and any other fields between the information extracted from the problem ticket and the aggregation of information that corresponds to previous error messages/searches. For example, if aspects of the extracted information match aspects of the aggregated information, then one or more embodiments can determine categories/tags of the aggregated information, and these categories/tags of the aggregated information can also be assigned to the current problem ticket.
- the information that is included with a problem ticket can also be used to help route a request regarding the problem ticket to users who may be able to provide additional supplemental information to include with the problem ticket. For example, if information of a current problem ticket is determined to be similar to information of another problem ticket that was previously solved by a previously qualified individual, the system can request input from the previously qualified individual.
- problem tickets can be time consuming and complex to resolve.
- the process of resolving the problems relating to the problem tickets generally requires accurate, unambiguous communication, and access to different sets of knowledge and experiences.
- one or more embodiments of the invention can automate and enhance much of the data entry process of problem solving.
- One or more embodiments can allow users to easily add potentially helpful input during the time when the problem ticket is awaiting the qualified user to address the problem.
- FIG. 1 illustrates a process for generating and publishing a problem ticket in accordance with one or more embodiments of the invention.
- a user of the system can encounter a problem and can thus generate a problem ticket.
- the user can submit information to fill some required fields of the problem ticket.
- one or more embodiments can autofill some required fields of the problem ticket.
- the problem ticket can extract information from the ticket data at 103 .
- the problem ticket can enter a queue to await a qualified user to resolve the problem.
- supplementary information can be added to the problem ticket while the problem ticket is awaiting resolution by the qualified user.
- one or more embodiments can analyze textual or imagery content that has been included with the problem ticket.
- the textual/imagery content can be analyzed by automated cognitive systems that can perform optical character recognition or other analysis techniques.
- one or more embodiments can determine keywords, tags, categories, contextual information, entity names, error codes, etc., that can be helpful to the qualified user.
- keywords, tags, categories, etc. can be stored in conjunction with the problem ticket, and can also be stored as aggregated information that is accessible to the system at 111 or at 110 .
- one or more embodiments can route or categorize the problem ticket.
- one or more embodiments can publish the problem ticket to an interface under one or more technical categories that can be reviewed by other users.
- Information relating to the problem ticket can also be compared against historical data 110 to determine if any other user has previously resolved a problem that is similar to the problem described by the problem ticket.
- different users can provide additional supplementary information that can be included with the problem ticket.
- the queued problem ticket can finally reach the qualified user, and the qualified user can review the additional supplementary information and any other information that has been stored with the problem ticket. The qualified user can use such information to resolve the problem.
- FIG. 2 depicts a flowchart of a method in accordance with one or more embodiments of the invention.
- the method of FIG. 2 can be performed by a controller of a problem-tracking system that is configured to generate and publish a problem ticket.
- the method includes, at block 210 , generating, by a processor of a problem-tracking system, a problem ticket.
- the problem ticket describes a problem encountered by a first user, and the problem ticket is assigned to at least one qualified user to resolve.
- the method also includes, at block 220 , receiving additional information relating to the problem from at least one second user.
- the method also includes, at block 230 , storing the received additional information in association with the problem ticket. The receiving and the storing of the additional information occurs while the problem ticket is waiting to be resolved by the at least one qualified user.
- the method also includes, at 240 , providing the stored received additional information and the problem ticket to the at least one qualified user.
- FIG. 3 depicts a high-level block diagram of a computer system 300 , which can be used to implement one or more embodiments of the invention.
- Computer system 300 can be a part of an overall problem-tracking system.
- Computer system 300 can be used to implement hardware components of systems capable of performing methods described herein.
- computer system 300 includes a communication path 326 , which connects computer system 300 to additional systems (not depicted) and can include one or more wide area networks (WANs) and/or local area networks (LANs) such as the Internet, intranet(s), and/or wireless communication network(s).
- WANs wide area networks
- LANs local area networks
- Computer system 300 and additional system are in communication via communication path 326 , e.g., to communicate data between them.
- Computer system 300 includes one or more processors, such as processor 302 .
- Processor 302 is connected to a communication infrastructure 304 (e.g., a communications bus, cross-over bar, or network).
- Computer system 300 can include a display interface 306 that forwards graphics, textual content, and other data from communication infrastructure 304 (or from a frame buffer not shown) for display on a display unit 308 .
- Computer system 300 also includes a main memory 310 , preferably random access memory (RAM), and can also include a secondary memory 312 .
- Secondary memory 312 can include, for example, a hard disk drive 314 and/or a removable storage drive 316 , representing, for example, a floppy disk drive, a magnetic tape drive, or an optical disc drive.
- Hard disk drive 314 can be in the form of a solid state drive (SSD), a traditional magnetic disk drive, or a hybrid of the two. There also can be more than one hard disk drive 314 contained within secondary memory 312 .
- Removable storage drive 316 reads from and/or writes to a removable storage unit 318 in a manner well known to those having ordinary skill in the art.
- Removable storage unit 318 represents, for example, a floppy disk, a compact disc, a magnetic tape, or an optical disc, etc. which is read by and written to by removable storage drive 316 .
- removable storage unit 318 includes a computer-readable medium having stored therein computer software and/or data.
- secondary memory 312 can include other similar means for allowing computer programs or other instructions to be loaded into the computer system.
- Such means can include, for example, a removable storage unit 320 and an interface 322 .
- Examples of such means can include a program package and package interface (such as that found in video game devices), a removable memory chip (such as an EPROM, secure digital card (SD card), compact flash card (CF card), universal serial bus (USB) memory, or PROM) and associated socket, and other removable storage units 320 and interfaces 322 which allow software and data to be transferred from the removable storage unit 320 to computer system 300 .
- a program package and package interface such as that found in video game devices
- a removable memory chip such as an EPROM, secure digital card (SD card), compact flash card (CF card), universal serial bus (USB) memory, or PROM
- PROM universal serial bus
- Computer system 300 can also include a communications interface 324 .
- Communications interface 324 allows software and data to be transferred between the computer system and external devices.
- Examples of communications interface 324 can include a modem, a network interface (such as an Ethernet card), a communications port, or a PC card slot and card, a universal serial bus port (USB), and the like.
- Software and data transferred via communications interface 324 are in the form of signals that can be, for example, electronic, electromagnetic, optical, or other signals capable of being received by communications interface 324 . These signals are provided to communications interface 324 via a communication path (i.e., channel) 326 .
- Communication path 326 carries signals and can be implemented using wire or cable, fiber optics, a phone line, a cellular phone link, an RF link, and/or other communications channels.
- computer program medium In the present description, the terms “computer program medium,” “computer usable medium,” and “computer-readable medium” are used to refer to media such as main memory 310 and secondary memory 312 , removable storage drive 316 , and a hard disk installed in hard disk drive 314 .
- Computer programs also called computer control logic
- Such computer programs when run, enable the computer system to perform the features discussed herein.
- the computer programs when run, enable processor 302 to perform the features of the computer system. Accordingly, such computer programs represent controllers of the computer system.
- FIG. 4 depicts a computer program product 400 , in accordance with an embodiment of the invention.
- Computer program product 400 includes a computer-readable storage medium 402 and program instructions 404 .
- the present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration
- the computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention
- the computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device.
- the computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
- a non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing.
- RAM random access memory
- ROM read-only memory
- EPROM or Flash memory erasable programmable read-only memory
- SRAM static random access memory
- CD-ROM compact disc read-only memory
- DVD digital versatile disk
- memory stick a floppy disk
- a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon
- a computer readable storage medium is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
- Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
- the network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.
- a network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
- Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages.
- the computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
- the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
- electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instruction by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
- These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
- the computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
- each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s).
- the functions noted in the blocks may occur out of the order noted in the Figures.
- two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
Abstract
Description
- The present invention relates in general to generating and publishing a problem ticket to allow users to collaboratively resolve a problem. More specifically, the present invention can relate to a system that enables users to generate and publish a problem ticket that describes a problem that is encountered by the users in the course of developing software, for example.
- When developing software, a team of users can work together to conceive, describe, design, program, and test one or more software components. During the development process, a user can encounter a technical problem that requires the attention of another qualified user to resolve. The user that encounters the problem can generate a report such as, for example, a problem ticket to describe the characteristics of the problem and the circumstances surrounding the problem. By referring to the information that is included with the problem ticket, the qualified user can attempt to reproduce the problem so that the problem can be resolved.
- A computer-implemented method according to one or more embodiments of the invention includes generating, by a processor of a problem-tracking system, a problem ticket. The problem ticket describes a problem encountered by a first user, and the problem ticket is assigned to at least one qualified user to resolve. The method also includes receiving additional information relating to the problem from at least one second user. The method also includes storing the received additional information in association with the problem ticket. The receiving and the storing of the additional information occurs while the problem ticket is waiting to be resolved by the at least one qualified user. The method also includes providing the stored received additional information and the problem ticket to the at least one qualified user.
- A computer system according to one or more embodiments of the invention includes a memory. The computer system can also include a processor system communicatively coupled to the memory. The processor system is configured to perform a method including generating a problem ticket. The problem ticket describes a problem encountered by a first user, and the problem ticket is assigned to at least one qualified user to resolve. The method also includes receiving additional information relating to the problem from at least one second user. The method also includes storing the received additional information in association with the problem ticket. The receiving and the storing of the additional information occurs while the problem ticket is waiting to be resolved by the at least one qualified user. The method also includes providing the stored received additional information and the problem ticket to the at least one qualified user.
- A computer program product according to one or more embodiments of the invention includes a computer-readable storage medium having program instructions embodied therewith. The program instructions are readable by a processor system of a problem-tracking system to cause the processor system to generate a problem ticket. The problem ticket describes a problem encountered by a first user, and the problem ticket is assigned to at least one qualified user to resolve. The processor system can also be caused to receive additional information relating to the problem from at least one second user. The processor system can also be caused to store the received additional information in association with the problem ticket. The receiving and the storing of the additional information occurs while the problem ticket is waiting to be resolved by the at least one qualified user. The processor system can also be caused to provide the stored received additional information and the problem ticket to the at least one qualified user.
- The subject matter of one or more embodiments is particularly pointed out and distinctly defined in the claims at the conclusion of the specification. The foregoing and other features and advantages are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
-
FIG. 1 illustrates a process for generating and publishing a problem ticket in accordance with one or more embodiments of the invention; -
FIG. 2 depicts a flowchart of a method in accordance with one or more embodiments of the invention; -
FIG. 3 depicts a high-level block diagram of a computer system, which can be used to implement one or more embodiments of the invention; and -
FIG. 4 depicts a computer program product, in accordance with an embodiment of the invention. - Various embodiments of the invention are described herein with reference to the related drawings. Alternative embodiments of the invention can be devised without departing from the scope of this invention. References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described can include a particular feature, structure, or characteristic, but every embodiment may or may not include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments of the invention whether or not explicitly described.
- Additionally, although this disclosure includes a detailed description of a computing device configuration, implementation of the teachings recited herein are not limited to a particular type or configuration of computing device(s). Rather, embodiments of the present disclosure are capable of being implemented in conjunction with any other type or configuration of wireless or non-wireless computing devices and/or computing environments, now known or later developed.
- The following definitions and abbreviations are to be used for the interpretation of the claims and the specification. As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” “contains” or “containing,” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a composition, a mixture, process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but can include other elements not expressly listed or inherent to such composition, mixture, process, method, article, or apparatus.
- Additionally, the term “exemplary” is used herein to mean “serving as an example, instance or illustration.” Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments of the invention or designs. The terms “at least one” and “one or more” are understood to include any integer number greater than or equal to one, i.e. one, two, three, four, etc. The terms “a plurality” are understood to include any integer number greater than or equal to two, i.e. two, three, four, five, etc. The term “connection” can include an indirect “connection” and a direct “connection.”
- For the sake of brevity, conventional techniques related to computer processing systems and computing models may or may not be described in detail herein. Moreover, it is understood that the various tasks and process steps described herein can be incorporated into a more comprehensive procedure, process or system having additional steps or functionality not described in detail herein.
- One or more embodiments are directed to generating and publishing a problem ticket to resolve a problem. After the problem ticket is generated, at least one specific qualified team member can be assigned to resolve the problem. While the generated problem ticket is waiting to be addressed by the qualified team member, the problem ticket can be published on an interface that allows other team members to collaboratively provide additional/supplemental information that can possibly assist the qualified team member in solving the problem. As such, different team members who work on a project together can use a system of one or more embodiments to track and resolve problems which arise in the course of completing the project. For example, in one embodiment of the present invention, a software development team can track and resolve problems which arise in the course of developing software.
- With a problem-tracking system of the conventional approaches, if a user encounters a problem, the user can report the problem by generating an indication of the problem. For example, the user can generate a problem ticket, where the problem ticket describes the presence of the problem and describes characteristics of the problem.
- If multiple problem tickets have been generated by the users of the system, then the problem tickets can be ordered within a queue, and each problem ticket can be assigned to one or more qualified users to resolve. Each problem ticket then remains within the queue until the qualified team member is able to resolve the problem that is associated with each problem ticket.
- With the conventional approaches, when a problem ticket is awaiting to be resolved by the qualified user, the problem ticket is merely waiting to be addressed by the qualified user, and thus the problem ticket does not progress toward resolution during this time. The conventional approaches do not use this waiting time in a productive manner that progresses the problem ticket toward resolution. Additionally, with the conventional approaches, users can inadvertently submit incomplete information when generating the problem ticket. For example, the information that is submitted by the user may not be sufficient for resolving the problem of the ticket. Further, the system of the conventional approaches can possibly prompt the user to submit details that are not relevant to resolving the problem of the problem ticket.
- In view of the shortcomings described above, the problem tickets that are generated by the conventional approaches generally await to be serviced by the assigned qualified user, without progressing toward resolution during this waiting time. Further, the problem tickets of the conventional approaches typically include insufficient or irrelevant information for solving the problem of the problem ticket. When the qualified user that is assigned to solve the problem ticket receives and reviews the insufficient and irrelevant information that is included with the problem ticket, the qualified user can then become frustrated when attempting to resolve the problem that is associated with the problem ticket.
- In contrast to the conventional approaches, one or more embodiments can enable users to provide additional/supplemental information that is to be included with a problem ticket while the problem ticket is waiting to be resolved by the qualified user. With one or more embodiments, while the problem ticket is waiting within a queue to be addressed by a qualified user, other users can easily submit/input additional/supplemental information that can be useful to the qualified user who is ultimately assigned to solve the problem of the ticket. Once the qualified user is able to review the supplementary information, the qualified user can refer to the supplemental information to resolve the problem of the problem ticket.
- As described above, with one example embodiment, a team of users can work together to develop a software application. During the course of development, suppose that a problem arises, and the problem produces an error code relating to a database that is used by the software application. Upon determining that the problem has occurred, a user can then generate a problem ticket that describes the problem and that describes the associated error code. While the problem ticket is awaiting the qualified user to address the problem, a different user such as, for example, a database expert can review the problem ticket and the database expert can possibly submit some supplementary information relating to the error code. Once the qualified user (who is assigned to resolve the problem ticket) reviews the problem ticket, the qualified user can also review the supplementary information relating to the error code.
- As described above, a user can use the system of one or more embodiments to generate a problem ticket. When generating the problem ticket, the user submits information that describes the problem. With one or more embodiments, the user who generates the problem ticket can include information in the form of textual information or in the form of captured imagery information. The captured imagery information can be in the form of pictures or video. For example, the pictures or video can correspond to a screenshot of the encountered problem. With one or more embodiments of the present invention, the user who generates the problem ticket can capture and submit information to be included with the problem ticket by using the user's mobile device. As described above, when the problem ticket is generated, the problem ticket can be assigned to at least one qualified user to resolve the problem.
- With one or more embodiments, while the problem ticket is waiting to be resolved by the qualified user, the system can also publish the problem ticket to a platform that is accessible by other users. As such, the other users can collaboratively contribute information to the published problem ticket. When the problem ticket is published to the platform, the problem ticket can be fit into one or more categories/tags that exist on the platform, as discussed in more detail below. The categories/tags that are associated with a problem ticket can initially be submitted by the user who generated the problem ticket. However, as described in more detail below, other users can also assign categories/tags to the problem ticket, and a cognitive system of one or more embodiments can also assign categories/tags to the problem ticket.
- The platform upon which the problem ticket is published can be organized in accordance with different categories and/or different tags, which can correspond to the different categories/tags that are assigned to the problem tickets. For example, the platform can be organized around different technical categories/tags that relate to different programming languages, different entity names, different operating systems, different error types, different application types, different functions, different ways to utilize memory, etc. The categories/tags that are used by the platform can correspond to categories/tags that that are used by other social media platforms, online project hosting wikis, blogs, forums, and other technical websites. Therefore, a user who seeks to help resolve problem tickets that are published on the platform can be directed to categories/tags that correspond to the user's areas of expertise, and thus the user can contribute information relating to problem tickets that are within the user's area of expertise.
- With one or more embodiments, the different users can assign different categories and/or tags to the published problem ticket. Although these users can be users who are unable to resolve the problem themselves, they can still provide information that can be helpful to the qualified user who is assigned to ultimately resolve the problem.
- The system of one or more embodiments can include automated tools that assign categories and/or tags to the problem ticket. For example, if one or more users have submitted imagery to be included with the problem ticket, an automated cognitive tool can categorize the submitted imagery via pattern matching and/or machine learning. The automated cognitive tool can be implemented as a convolutional neural network, for example. Therefore, the submitted imagery can enable the problem ticket to be associated with one or more categories by the system of one or more embodiments. One or more embodiments can also perform optical character recognition on the submitted imagery to determine categories, tags, and/or keywords, for example. One or more embodiments can also determine keywords based on textual information that has been submitted for the problem ticket. These keywords can then be associated with the problem ticket. The submitted textual information can also be configured to be searchable by other users.
- The system of one or more embodiments can compare the imagery submitted with a problem ticket against other imagery that may be able to help provide resolution or additional context to the problem. Specifically, one or more embodiments can determine similarities between the imagery submitted with the problem ticket and other imagery that may be able to help provide resolution/context. For example, if the imagery of a problem ticket matches a previous image that was previously published on the platform, then one or more embodiments can determine whether the previous image was associated with any categories/tags, and these possible categories/tags of the previous image can also be assigned to the current problem ticket. The problem ticket can be analyzed using cognitive tools to extract any other textual clues or image context that are present within the problem ticket. The extracted textual clues and/or image context can then be provided to users in order to help the users to identify key elements within the problem ticket.
- The system of one or more embodiments can also use cognitive functionality to leverage machine-learning and/or pattern-matching abilities. By leveraging these abilities, one or more embodiments can also automate certain aspects of submitting information for the ticket. For example, by analyzing information that has been included with the problem ticket, one or more embodiments can determine information such as, but not limited to, an operating system that the user is using, the relevant software that the user is using, a relevant program version of the software that is being utilized, an error code that has been encountered, etc. Such determined information can also be automatically included with the problem ticket. As such, one or more embodiments can allow a user to avoid the process of entering certain data, where the user can consider the data-entry process of such data to be a tedious process.
- One or more embodiments can use Application Program Interfaces (APIs) and/or web services to extract entity names from the information that is included with the problem ticket. These extracted entity names can be used to categorize/tag the problem ticket when publishing the problem ticket upon the above-described platform. One or more embodiments can extract entity names from Uniform Resource Locators (URLs), from Hypertext Markup Language (HTML) files, and from textual content. One or more embodiments can extract meta-data from the information that is included with the problem ticket. The extracted meta-data can be in Extensible Markup Language (XML) and/or JavaScript Object Notation (JSON) formats.
- Once meta-data is extracted from the information that is included with the problem ticket, the system of one or more embodiments can compare the extracted information against an aggregation of information that corresponds to previous error messages and previous searches. The system can compare the locations, the inputs, the position, and any other fields between the information extracted from the problem ticket and the aggregation of information that corresponds to previous error messages/searches. For example, if aspects of the extracted information match aspects of the aggregated information, then one or more embodiments can determine categories/tags of the aggregated information, and these categories/tags of the aggregated information can also be assigned to the current problem ticket.
- The information that is included with a problem ticket can also be used to help route a request regarding the problem ticket to users who may be able to provide additional supplemental information to include with the problem ticket. For example, if information of a current problem ticket is determined to be similar to information of another problem ticket that was previously solved by a previously qualified individual, the system can request input from the previously qualified individual.
- As described above, problem tickets can be time consuming and complex to resolve. The process of resolving the problems relating to the problem tickets generally requires accurate, unambiguous communication, and access to different sets of knowledge and experiences. As such, one or more embodiments of the invention can automate and enhance much of the data entry process of problem solving. One or more embodiments can allow users to easily add potentially helpful input during the time when the problem ticket is awaiting the qualified user to address the problem.
-
FIG. 1 illustrates a process for generating and publishing a problem ticket in accordance with one or more embodiments of the invention. At 101, a user of the system can encounter a problem and can thus generate a problem ticket. Upon generating the problem ticket, at 102, the user can submit information to fill some required fields of the problem ticket. However, as discussed above, one or more embodiments can autofill some required fields of the problem ticket. Once the problem ticket is generated, one or more embodiments can extract information from the ticket data at 103. Also, once the problem ticket is generated, at 104, the problem ticket can enter a queue to await a qualified user to resolve the problem. At 105, supplementary information can be added to the problem ticket while the problem ticket is awaiting resolution by the qualified user. For example, at 107, one or more embodiments can analyze textual or imagery content that has been included with the problem ticket. As described above, the textual/imagery content can be analyzed by automated cognitive systems that can perform optical character recognition or other analysis techniques. By analyzing the textual/imagery content, one or more embodiments can determine keywords, tags, categories, contextual information, entity names, error codes, etc., that can be helpful to the qualified user. These keywords, tags, categories, etc., can be stored in conjunction with the problem ticket, and can also be stored as aggregated information that is accessible to the system at 111 or at 110. At 108, one or more embodiments can route or categorize the problem ticket. For example, as described above, one or more embodiments can publish the problem ticket to an interface under one or more technical categories that can be reviewed by other users. Information relating to the problem ticket can also be compared againsthistorical data 110 to determine if any other user has previously resolved a problem that is similar to the problem described by the problem ticket. At 109, different users can provide additional supplementary information that can be included with the problem ticket. At 106, the queued problem ticket can finally reach the qualified user, and the qualified user can review the additional supplementary information and any other information that has been stored with the problem ticket. The qualified user can use such information to resolve the problem. -
FIG. 2 depicts a flowchart of a method in accordance with one or more embodiments of the invention. The method ofFIG. 2 can be performed by a controller of a problem-tracking system that is configured to generate and publish a problem ticket. The method includes, atblock 210, generating, by a processor of a problem-tracking system, a problem ticket. The problem ticket describes a problem encountered by a first user, and the problem ticket is assigned to at least one qualified user to resolve. The method also includes, atblock 220, receiving additional information relating to the problem from at least one second user. The method also includes, atblock 230, storing the received additional information in association with the problem ticket. The receiving and the storing of the additional information occurs while the problem ticket is waiting to be resolved by the at least one qualified user. The method also includes, at 240, providing the stored received additional information and the problem ticket to the at least one qualified user. -
FIG. 3 depicts a high-level block diagram of acomputer system 300, which can be used to implement one or more embodiments of the invention.Computer system 300 can be a part of an overall problem-tracking system.Computer system 300 can be used to implement hardware components of systems capable of performing methods described herein. Although oneexemplary computer system 300 is shown,computer system 300 includes acommunication path 326, which connectscomputer system 300 to additional systems (not depicted) and can include one or more wide area networks (WANs) and/or local area networks (LANs) such as the Internet, intranet(s), and/or wireless communication network(s).Computer system 300 and additional system are in communication viacommunication path 326, e.g., to communicate data between them. -
Computer system 300 includes one or more processors, such asprocessor 302.Processor 302 is connected to a communication infrastructure 304 (e.g., a communications bus, cross-over bar, or network).Computer system 300 can include adisplay interface 306 that forwards graphics, textual content, and other data from communication infrastructure 304 (or from a frame buffer not shown) for display on adisplay unit 308.Computer system 300 also includes amain memory 310, preferably random access memory (RAM), and can also include asecondary memory 312.Secondary memory 312 can include, for example, ahard disk drive 314 and/or aremovable storage drive 316, representing, for example, a floppy disk drive, a magnetic tape drive, or an optical disc drive.Hard disk drive 314 can be in the form of a solid state drive (SSD), a traditional magnetic disk drive, or a hybrid of the two. There also can be more than onehard disk drive 314 contained withinsecondary memory 312.Removable storage drive 316 reads from and/or writes to aremovable storage unit 318 in a manner well known to those having ordinary skill in the art.Removable storage unit 318 represents, for example, a floppy disk, a compact disc, a magnetic tape, or an optical disc, etc. which is read by and written to byremovable storage drive 316. As will be appreciated,removable storage unit 318 includes a computer-readable medium having stored therein computer software and/or data. - In alternative embodiments of the invention,
secondary memory 312 can include other similar means for allowing computer programs or other instructions to be loaded into the computer system. Such means can include, for example, aremovable storage unit 320 and aninterface 322. Examples of such means can include a program package and package interface (such as that found in video game devices), a removable memory chip (such as an EPROM, secure digital card (SD card), compact flash card (CF card), universal serial bus (USB) memory, or PROM) and associated socket, and otherremovable storage units 320 andinterfaces 322 which allow software and data to be transferred from theremovable storage unit 320 tocomputer system 300. -
Computer system 300 can also include acommunications interface 324. Communications interface 324 allows software and data to be transferred between the computer system and external devices. Examples ofcommunications interface 324 can include a modem, a network interface (such as an Ethernet card), a communications port, or a PC card slot and card, a universal serial bus port (USB), and the like. Software and data transferred viacommunications interface 324 are in the form of signals that can be, for example, electronic, electromagnetic, optical, or other signals capable of being received bycommunications interface 324. These signals are provided tocommunications interface 324 via a communication path (i.e., channel) 326.Communication path 326 carries signals and can be implemented using wire or cable, fiber optics, a phone line, a cellular phone link, an RF link, and/or other communications channels. - In the present description, the terms “computer program medium,” “computer usable medium,” and “computer-readable medium” are used to refer to media such as
main memory 310 andsecondary memory 312,removable storage drive 316, and a hard disk installed inhard disk drive 314. Computer programs (also called computer control logic) are stored inmain memory 310 and/orsecondary memory 312. Computer programs also can be received viacommunications interface 324. Such computer programs, when run, enable the computer system to perform the features discussed herein. In particular, the computer programs, when run, enableprocessor 302 to perform the features of the computer system. Accordingly, such computer programs represent controllers of the computer system. Thus it can be seen from the foregoing detailed description that one or more embodiments of the invention provide technical benefits and advantages. - The terms “about,” “substantially,” “approximately,” and variations thereof, are intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application. For example, “about” can include a range of ±8% or 5%, or 2% of a given value.
-
FIG. 4 depicts acomputer program product 400, in accordance with an embodiment of the invention.Computer program product 400 includes a computer-readable storage medium 402 andprogram instructions 404. - The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
- The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
- Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
- Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments of the invention, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instruction by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
- Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
- These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
- The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
- The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
- The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments described herein.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/989,346 US10489728B1 (en) | 2018-05-25 | 2018-05-25 | Generating and publishing a problem ticket |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/989,346 US10489728B1 (en) | 2018-05-25 | 2018-05-25 | Generating and publishing a problem ticket |
Publications (2)
Publication Number | Publication Date |
---|---|
US10489728B1 US10489728B1 (en) | 2019-11-26 |
US20190362291A1 true US20190362291A1 (en) | 2019-11-28 |
Family
ID=68614715
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/989,346 Active US10489728B1 (en) | 2018-05-25 | 2018-05-25 | Generating and publishing a problem ticket |
Country Status (1)
Country | Link |
---|---|
US (1) | US10489728B1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3992876A1 (en) * | 2020-10-01 | 2022-05-04 | Accenture Global Solutions Limited | Integration navigator and intelligent monitoring for living systems |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11741194B2 (en) * | 2020-03-23 | 2023-08-29 | Cognizant Technology Solutions India Pvt. Ltd. | System and method for creating healing and automation tickets |
US11720480B2 (en) * | 2021-03-29 | 2023-08-08 | International Business Machines Corporation | Collaborative software event discourse decomposition |
Family Cites Families (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6260048B1 (en) * | 1998-10-27 | 2001-07-10 | Hewlett-Packard Company | Resolution of incidents which occur during the use of a product |
US6389426B1 (en) * | 1999-02-09 | 2002-05-14 | Worldcom, Inc. | Central trouble ticket database and system and method for managing same to facilitate ticketing, trending, and tracking processes |
US7225139B1 (en) * | 2000-06-27 | 2007-05-29 | Bellsouth Intellectual Property Corp | Trouble tracking system and method |
US8224683B2 (en) * | 2003-07-08 | 2012-07-17 | Hewlett-Packard Development Company, L.P. | Information technology service request level of service monitor |
US20050097396A1 (en) * | 2003-10-20 | 2005-05-05 | International Business Machines Corporation | System and method for root cause linking of trouble tickets |
US7493518B2 (en) * | 2005-11-15 | 2009-02-17 | International Business Machines Corporation | System and method of managing events on multiple problem ticketing system |
US9548883B2 (en) * | 2006-08-31 | 2017-01-17 | Microsoft Technology Licensing, Llc | Support incident routing |
US9483791B2 (en) * | 2007-03-02 | 2016-11-01 | Spiceworks, Inc. | Network software and hardware monitoring and marketplace |
US20090055684A1 (en) * | 2007-08-23 | 2009-02-26 | Jamjoom Hani T | Method and apparatus for efficient problem resolution via incrementally constructed causality model based on history data |
US8549028B1 (en) * | 2008-01-24 | 2013-10-01 | Case Global, Inc. | Incident tracking systems and methods |
US8532342B2 (en) * | 2008-02-12 | 2013-09-10 | Certusview Technologies, Llc | Electronic manifest of underground facility locate marks |
US9722890B2 (en) * | 2011-12-16 | 2017-08-01 | Sap Se | Integrated incident management for hybrid landscapes |
US9229800B2 (en) * | 2012-06-28 | 2016-01-05 | Microsoft Technology Licensing, Llc | Problem inference from support tickets |
US9317829B2 (en) * | 2012-11-08 | 2016-04-19 | International Business Machines Corporation | Diagnosing incidents for information technology service management |
US9003547B2 (en) * | 2012-12-11 | 2015-04-07 | International Business Machines Corporation | Using data analytics and crowdsourcing to determine roles for a computer system |
US20140244330A1 (en) * | 2013-02-22 | 2014-08-28 | Innovations 10.01, Llc | System and method for assessing and managing a facility |
US10824993B2 (en) * | 2013-03-15 | 2020-11-03 | Bmc Software, Inc. | Story-mode user interface |
WO2015147878A1 (en) * | 2014-03-28 | 2015-10-01 | Hewlett-Packard Development Company, L.P. | Systems and methods for providing an information technology interface |
US20150302337A1 (en) * | 2014-04-17 | 2015-10-22 | International Business Machines Corporation | Benchmarking accounts in application management service (ams) |
US9317380B2 (en) * | 2014-05-02 | 2016-04-19 | International Business Machines Corporation | Preserving management services with self-contained metadata through the disaster recovery life cycle |
US8903933B1 (en) * | 2014-07-21 | 2014-12-02 | ConnectWise Inc. | Systems and methods for prioritizing and servicing support tickets using a chat session |
US10380519B2 (en) * | 2015-03-26 | 2019-08-13 | Accenture Global Services Limited | Ticket solver system |
WO2017046549A1 (en) * | 2015-09-16 | 2017-03-23 | Computacenter Uk Ltd. | System and method for management of operational incidents by a facility support service |
US20170132557A1 (en) * | 2015-11-05 | 2017-05-11 | Wipro Limited | Methods and systems for evaluating an incident ticket |
EP3193265A1 (en) * | 2016-01-18 | 2017-07-19 | Wipro Limited | System and method for classifying and resolving software production incident tickets |
US10956826B2 (en) * | 2016-05-12 | 2021-03-23 | International Business Machines Corporation | Root cause analysis validation through inverse causation |
US10198732B2 (en) * | 2016-06-30 | 2019-02-05 | Ebay Inc. | Interactive error user interface |
US20180060786A1 (en) * | 2016-08-30 | 2018-03-01 | Wipro Limited | System and Method for Allocating Tickets |
US20180108022A1 (en) * | 2016-10-14 | 2018-04-19 | International Business Machines Corporation | Increasing Efficiency and Effectiveness of Support Engineers in Resolving Problem Tickets |
US20180211260A1 (en) * | 2017-01-25 | 2018-07-26 | Linkedin Corporation | Model-based routing and prioritization of customer support tickets |
US10175979B1 (en) * | 2017-01-27 | 2019-01-08 | Intuit Inc. | Defect ownership assignment system and predictive analysis for codebases |
US10558701B2 (en) * | 2017-02-08 | 2020-02-11 | International Business Machines Corporation | Method and system to recommend images in a social application |
US10380520B2 (en) * | 2017-03-13 | 2019-08-13 | Accenture Global Solutions Limited | Automated ticket resolution |
US20180315055A1 (en) * | 2017-05-01 | 2018-11-01 | International Business Machines Corporation | Blockchain For Issue/Defect Tracking System |
US20180335900A1 (en) * | 2017-05-22 | 2018-11-22 | Microsoft Technology Licensing, Llc | Dynamic support feedback for in-app help |
US20190004890A1 (en) * | 2017-06-30 | 2019-01-03 | Wipro Limited | Method and system for handling one or more issues in a computing environment |
-
2018
- 2018-05-25 US US15/989,346 patent/US10489728B1/en active Active
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3992876A1 (en) * | 2020-10-01 | 2022-05-04 | Accenture Global Solutions Limited | Integration navigator and intelligent monitoring for living systems |
Also Published As
Publication number | Publication date |
---|---|
US10489728B1 (en) | 2019-11-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11449379B2 (en) | Root cause and predictive analyses for technical issues of a computing environment | |
US11487539B2 (en) | Systems and methods for automating and monitoring software development operations | |
US9766868B2 (en) | Dynamic source code generation | |
US9619209B1 (en) | Dynamic source code generation | |
US20130103381A1 (en) | Systems and methods for enhancing machine translation post edit review processes | |
US10489728B1 (en) | Generating and publishing a problem ticket | |
US9733906B2 (en) | User interface area coverage | |
US20170371969A1 (en) | Identifying equivalent links on a page | |
US11645335B2 (en) | Generating solution keyword tag clouds based on support forum post analytics | |
US20160171104A1 (en) | Detecting multistep operations when interacting with web applications | |
US11055208B1 (en) | Systems and methods for automatically assessing and conforming software development modules to accessibility guidelines in real-time | |
US11176019B2 (en) | Automated breakpoint creation | |
US20170147474A1 (en) | Software testing coverage | |
US10324970B2 (en) | Feedback analysis for content improvement tasks | |
US9378115B2 (en) | Base line for code analysis | |
CN110110320B (en) | Automatic contract checking method, device, medium and electronic equipment | |
US10055276B2 (en) | Probabilistic detect identification | |
CN111325031A (en) | Resume parsing method and device | |
CN112988578A (en) | Automatic testing method and device | |
US20100305986A1 (en) | Using Service Exposure Criteria | |
US11853196B1 (en) | Artificial intelligence driven testing | |
CN110674491B (en) | Method and device for real-time evidence obtaining of android application and electronic equipment | |
CN110083807B (en) | Contract modification influence automatic prediction method, device, medium and electronic equipment | |
US10885019B2 (en) | Inter-reviewer conflict resolution | |
CN117453566A (en) | Code defect repairing method, device, electronic equipment and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SICONOLFI, PHILIP;DOLL, JACKY M.;BISTI, JEFFREY;SIGNING DATES FROM 20180514 TO 20180517;REEL/FRAME:045901/0981 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |