A method, device and computer equipment for processing problem sheet data

The life cycle of automatic acquisition and screening of problem orders through the code module solves the problem of time-consuming acquisition of problem orders in the existing technology, realizes automatic processing, reduces labor costs and improves work efficiency.

CN111767040BActive Publication Date: 2024-11-19BEIJING SIWEI ZHILIAN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010626852.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-07-01
Publication Date
2024-11-19
Estimated Expiration
2040-07-01

AI Technical Summary

Technical Problem

In the prior art, the acquisition and processing of problem list data takes a long time, resulting in high labor costs and low work efficiency.

Method used

Obtain the life cycle of the problem sheet through the code module, filter and import the target file, and use pre-configured program code to automatically process it, avoid manual operation.

Benefits of technology

It realizes automated processing, reduces labor costs, improves work efficiency, ensures the correctness of exporting data and saves time costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111767040B_ABST
    Figure CN111767040B_ABST
Patent Text Reader

Abstract

The present invention discloses a method, device and computer equipment for processing problem sheet data, wherein the method comprises: a code module obtains the life cycle corresponding to each problem sheet, the code module is a pre-configured program code; the code module reads the pre-divided life cycle intervals from the configuration file, wherein different life cycle intervals are used to distinguish problem sheets of different life cycles; the code module uses the life cycle interval as a screening condition to screen each problem sheet to obtain a problem sheet set corresponding to each life cycle interval; the code module imports the problem sheet set corresponding to each life cycle interval into a target file respectively. By implementing the present invention, there is no need for manual operation, and the tediousness of regular repeated operations is avoided, thereby saving time costs, reducing labor costs, and improving work efficiency, while ensuring the correctness of the export of the problem sheet set.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device and computer equipment for processing problem sheet data. Background Art

[0002] During data or system testing, testing problems are inevitable. Problems found during testing are usually recorded using issue tickets, and then the issue ticket data is sent to the relevant test manager. However, obtaining issue ticket data requires manual access to the jira issue ticket statistics platform, deleting redundant content in the issue ticket data, and then sending the file to the designated manager. For example, export issue ticket data from 3-6 days ago, issue ticket data from 7-14 days ago, and issue ticket data from 15 days ago, delete redundant columns that do not need to be counted in the exported Excel template, and send the file to the designated manager via email. Since obtaining issue ticket data requires long-term execution, obtaining issue ticket data through manual operations is time-consuming, which not only increases labor costs but also reduces work efficiency. Summary of the invention

[0003] Therefore, the technical problem to be solved by the present invention is to overcome the defects of the prior art that the generation of problem ticket data is time-consuming, resulting in high labor costs and low work efficiency, thereby providing a method, device and computer equipment for processing problem ticket data.

[0004] According to the first aspect, an embodiment of the present invention provides a method for processing problem ticket data, including: a code module obtains the life cycle corresponding to each problem ticket, the code module is a pre-configured program code; the code module reads pre-divided life cycle intervals from a configuration file, wherein different life cycle intervals are used to distinguish problem tickets with different life cycles; the code module uses the life cycle interval as a screening condition to screen each problem ticket to obtain a set of problem tickets corresponding to each life cycle interval; the code module imports the set of problem tickets corresponding to each life cycle interval into a target file respectively.

[0005] In combination with the first aspect, in a first implementation of the first aspect, a form corresponding to each life cycle interval is provided in the target file, and the code module imports the problem ticket sets corresponding to each life cycle interval into the target file respectively, including: importing the problem ticket sets corresponding to each life cycle interval into the corresponding forms in turn, and obtaining the target file with the imported form data.

[0006] In combination with the first implementation of the first aspect, in the second implementation of the first aspect, the problem ticket set corresponding to each life cycle interval is imported into its corresponding form in sequence, including: determining whether the problem ticket set corresponding to each life cycle interval is an empty set; when the problem ticket set is not an empty set, importing it into the corresponding form; when the problem ticket set is an empty set, deleting the form corresponding to the life cycle interval in which the problem ticket set is an empty set.

[0007] In combination with the first aspect, in a third implementation of the first aspect, before the code module obtains the life cycle corresponding to each problem ticket, it also includes: running a pre-configured script file, in which the startup command of the code module is configured; executing the startup command in the script file to start the code module; the code module logs in to the system used to store problem ticket data.

[0008] In combination with the first aspect, in a fourth implementation of the first aspect, after the code module imports the problem ticket sets corresponding to each life cycle interval into the target file respectively, it also includes: the code module obtains the address list contained in the storage directory corresponding to the target file; the code module sends the target file to the corresponding target user in the address list based on the address list.

[0009] In combination with the first implementation of the first aspect, in the fifth implementation of the first aspect, the problem ticket sets corresponding to each life cycle interval are imported into their corresponding forms in sequence to obtain the target file for importing form data, including: matching the problem tickets in the problem ticket set using a pre-set target field, wherein the target field is a characteristic field of the problem tickets that do not need to be processed; deleting the matched problem tickets from the problem set to obtain a set of problem tickets after matching; and importing the set of problem tickets after matching into the form of the target file.

[0010] According to the second aspect, an embodiment of the present invention provides a device for processing problem ticket data, including: an acquisition module for acquiring the life cycle corresponding to each problem ticket; a reading module for reading pre-divided life cycle intervals from a configuration file, wherein different life cycle intervals are used to distinguish problem tickets of different life cycles; a screening module for using the life cycle interval as a screening condition to screen each problem ticket to obtain a problem ticket set corresponding to each life cycle interval; and an import module for importing the problem ticket set corresponding to each life cycle interval into a target file, respectively.

[0011] In combination with the second aspect, in the first implementation of the second aspect, a form corresponding to each life cycle interval is set in the target file, and the import module includes: an import sub-module, which is used to import the problem ticket set corresponding to each life cycle interval into its corresponding form in turn to obtain the target file of the imported form data.

[0012] According to the third aspect, an embodiment of the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for processing problem ticket data described in the first aspect or any implementation method of the first aspect by executing the computer instructions.

[0013] According to the fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the method for processing problem ticket data described in the first aspect or any implementation method of the first aspect.

[0014] The technical solution of the present invention has the following advantages:

[0015] The method, device and computer equipment for processing problem ticket data provided by the present invention obtain the life cycle corresponding to each problem ticket through a code module, use the life cycle as a screening condition, screen each problem ticket, obtain a problem ticket set corresponding to each life cycle interval, and import the problem ticket set into a target file. The code module is a pre-set program code. Since it is generated by the program, it does not need to be manually acquired or sent manually, thereby reducing labor costs and ensuring the correctness of the exported problem ticket set. Since the problem ticket data needs to be exported regularly and the export operation is the same each time, exporting the problem ticket data through the code module avoids the tediousness of regular repeated operations, thereby saving time costs and improving work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0017] Figure 1 is a flowchart of a method for processing problem sheet data in an embodiment of the present invention;

[0018] Figure 2 Another flow chart of the method for processing problem ticket data in an embodiment of the present invention;

[0019] Figure 3 Another flow chart of the method for processing problem sheet data in an embodiment of the present invention;

[0020] Figure 4 It is a principle block diagram of a device for processing problem sheet data in an embodiment of the present invention;

[0021] Figure 5 Schematic diagram of the structure of a computer device in an embodiment of the present invention. DETAILED DESCRIPTION

[0022] The technical solution of the present invention will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0023] In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicating the orientation or positional relationship, are based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first", "second", and "third" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance.

[0024] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, it can also be the internal connection of two components, it can be a wireless connection, or it can be a wired connection. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0025] In addition, the technical features involved in the different embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0026] Example 1

[0027] This embodiment provides a method for processing problem ticket data, which is applied to a problem ticket system and automatically counts the problem ticket data to generate a problem ticket set, such as Figure 1 As shown, the following steps are included:

[0028] S11, the code module obtains the life cycle corresponding to each problem ticket, and the code module is a pre-configured program code.

[0029] For example, a problem ticket is a record of problems found during the system version testing process. Testers usually need to extract problem tickets regularly, and problem tickets can be counted using an Excel statistical template. The life cycle is the unprocessed time of the problem ticket, and different problem tickets correspond to their own life cycles. The code module is a pre-configured program code, and the code module can be set in the problem ticket system to automatically obtain the life cycle of each problem ticket.

[0030] S12, the code module reads the pre-divided life cycle intervals from the configuration file, where different life cycle intervals are used to distinguish problem tickets of different life cycles.

[0031] Exemplarily, the problem ticket system includes multiple problem ticket data, and the corresponding life cycle of each problem ticket data can be obtained through the configuration file. For example, the corresponding life cycle of problem ticket data 1 is 3 days, the corresponding life cycle of problem ticket data 2 is 5 days, and the corresponding life cycle of problem ticket data 3 is 9 days, etc. The life cycle interval is the unprocessed time interval of the problem ticket. Problem tickets with different life cycles are distinguished according to the pre-divided life cycle intervals. For example, the life cycle interval can be 3-6 days, 7-14 days, or 15 days, and this application does not limit this.

[0032] S13, the code module uses the life cycle interval as a screening condition to screen each problem ticket and obtain a set of problem tickets corresponding to each life cycle interval.

[0033] Exemplarily, the life cycle interval is used as the filtering condition for the problem ticket data, and the problem tickets with different life cycles are filtered according to the life cycle of the acquired problem tickets. For example, the unprocessed problem ticket data from 3-6 days ago are counted and used as data set 1, the unprocessed problem ticket data from 7-14 days ago are counted and used as data set 2, and the unprocessed problem ticket data from 15 days ago are counted and used as data set 3.

[0034] S14, the code module imports the problem ticket sets corresponding to each life cycle interval into the target file respectively.

[0035] Exemplarily, the target file is a set of problem tickets corresponding to different life cycle intervals. The problem ticket data corresponding to different life cycle intervals are collected, and the problem ticket sets corresponding to different life cycles are imported into the sheet page corresponding to the Excel statistical template to generate the target file.

[0036] The method for processing problem ticket data provided by the present invention obtains the life cycle corresponding to each problem ticket through a code module, uses the life cycle as a screening condition, screens each problem ticket, obtains a problem ticket set corresponding to each life cycle interval, and imports the problem ticket set into a target file. The code module is a pre-set program code. Since it is generated by the program, it does not need to be manually acquired or manually sent, thereby reducing labor costs and ensuring the correctness of the exported problem ticket set. Since the problem ticket data needs to be exported regularly and the export operation is the same each time, the problem ticket data is exported through the code module, which avoids the tediousness of regular repeated operations, thereby saving time costs and improving work efficiency.

[0037] As an optional implementation, a form corresponding to each life cycle interval is set in the target file, and the above step S14 includes: importing the problem ticket set corresponding to each life cycle interval into its corresponding form in turn to obtain the target file of the imported form data.

[0038] For example, the form is a sheet page of an Excel statistics template, and different forms correspond to different life cycle intervals. The forms corresponding to different life cycle intervals are stored in the target file. For example, for a form corresponding to a life cycle interval of 3-6 days, the unprocessed problem ticket data from 3-6 days ago is imported into the form corresponding to the life cycle interval of 3-6 days, and a target file corresponding to the life cycle interval of 3-6 days is generated.

[0039] As an optional implementation, the step of sequentially importing the problem ticket sets corresponding to each life cycle interval into the corresponding form includes:

[0040] First, determine whether the problem ticket set corresponding to each life cycle interval is an empty set.

[0041] For example, different lifecycle intervals correspond to different problem ticket sets, and the problem ticket set may contain problem tickets whose problem ticket data is an empty set. It is meaningless to collect problem tickets whose problem ticket data is an empty set, and it will also occupy extra sheet pages. Therefore, when collecting problem tickets, it is necessary to determine whether the problem ticket set is an empty set.

[0042] Secondly, when the problem ticket set is not an empty set, it is imported into the corresponding form; when the problem ticket set is an empty set, the form corresponding to the life cycle interval in which the problem ticket set is an empty set is deleted.

[0043] Exemplarily, by judging whether the problem ticket set is an empty set, if it is determined that the problem ticket set does not contain problem ticket data of an empty set, the problem ticket data of the non-empty set is imported into the form of the corresponding life cycle interval of the problem ticket data; if it is determined that the problem ticket set contains problem ticket data of an empty set, the problem ticket data of the empty set is deleted from the form of the corresponding life cycle interval to avoid meaningless problem ticket data in the set.

[0044] As an optional implementation, the step of sequentially importing the problem ticket sets corresponding to each life cycle interval into the corresponding form to obtain the target file for importing the form data includes:

[0045] First, the problem tickets in the problem ticket set are matched using a preset target field, wherein the target field is a characteristic field of the problem tickets that do not need to be processed.

[0046] Exemplarily, the problem ticket can be matched according to a preset target field, wherein the target field can be a marking field corresponding to whether the problem ticket is an empty set, and the number "1" can represent a non-empty set, and the number "0" can represent an empty set. When the number in the marking field is "0", it means that the problem ticket is a problem ticket that does not need to be processed. The empty set problem ticket is matched by identifying the number in the marking field to determine the problem ticket that does not need to be processed.

[0047] Optionally, the target field may also include a timestamp corresponding to the unprocessed time. When the problem ticket data is generated, the timestamp may be added to the problem ticket data, and the code module may determine the unprocessed time of the problem ticket based on the timestamp.

[0048] Secondly, the matched problem tickets are deleted from the problem set to obtain a set of matched problem tickets.

[0049] Exemplarily, after matching the problem tickets that do not need to be processed according to the tag field, the problem tickets that do not need to be processed can be deleted from the problem ticket set, thereby ensuring that the acquired problem ticket set does not contain problem tickets with empty problem ticket data.

[0050] Again, import the matched and processed problem ticket set into the form of the target file.

[0051] Exemplarily, since the target file contains forms with different life cycles, after deleting the problem tickets that do not need to be processed from the problem ticket set, a set of matched problem tickets is obtained, that is, a set of all non-empty problem tickets. The matched non-empty problem ticket sets are imported into the forms corresponding to their respective life cycle intervals in turn, and the target file forms containing different life cycle intervals can be obtained.

[0052] As an optional implementation, Figure 2As shown, before step S11, the method for processing the problem sheet data further includes:

[0053] S100, running a pre-configured script file, in which a startup command of a code module is configured.

[0054] For example, the script file can be a bat script, in which a Java code startup command corresponding to the startup code module is configured, and the bat script file is started and executed regularly through the schtasks command in the dos interface of the windows system. This application does not limit the script file and the code startup command, and those skilled in the art can determine it according to actual needs.

[0055] S101, execute the startup command in the script file to start the code module.

[0056] Exemplarily, due to the code startup command for starting the code module configured in the bat script file, after starting the bat script file, the Java code startup command configured in the script file can be started by running the bat script file, thereby completing the startup of the code module.

[0057] S102, the code module logs into the system for storing problem ticket data.

[0058] For example, when the code module is started, it first logs into the jira problem ticket system, where the jira problem ticket system stores a variety of problem ticket data. After the code module successfully logs in, it can read the life cycle conditions of the jira problem ticket in the configuration file, that is, the filter conditions of the jira problem ticket. The problem tickets in the problem ticket collection are filtered by reading the filter conditions.

[0059] As an optional implementation, Figure 3 As shown, after step S14, the method for processing the problem sheet data further includes:

[0060] S15, the code module obtains the address list contained in the storage directory corresponding to the target file.

[0061] Exemplarily, the code module can be written in Java language. By executing the code module, the problem ticket data can be counted, and the non-empty set of legacy problem ticket data can be counted in an Excel sheet page to generate an Excel form of the legacy problem ticket data. The generated Excel form is then stored, and the storage directory of the Excel form contains a corresponding address list, wherein the address list can be a customized recipient mailbox list, and different recipients can be set as needed. By reading the configuration file, the recipient mailbox list contained in the storage directory can be obtained.

[0062] S16, the code module sends the target file to the corresponding target user in the address list according to the address list.

[0063] Exemplarily, the target user is the email recipient, that is, the designated person in charge of the legacy issue. The code module can search for the target user corresponding to the excel form according to the obtained mailbox list, and send the generated excel form as an email attachment to the designated recipient.

[0064] Compared with the life cycle of each issue ticket, log in to the Jira system, count the issue ticket information according to specific query conditions, then export it to Excel, manually delete some unnecessary columns in the Excel file, and finally send the Excel file to the relevant responsible person via email. Since this function needs to be done once a week, it takes about half an hour each time, and it is usually a long-term task for system projects.

[0065] Take a simple calculation as an example. If statistics are collected once a week, each time takes 0.5 hours. There are about 52 weeks in a year. Excluding two 7-day holidays, there are still 50 weeks that need statistics. The annual manpower time cost saved is 0.5*50=25 hours. The processing method based on the problem ticket data supports custom projects, which can meet the needs of multiple projects in the company to perform problem ticket statistics at the same time. Assuming that 10 projects in the company need to do problem ticket statistics, the time cost required is 10*25=250 hours. This method can realize automatic statistics without manual operation, which can save 250 hours of manpower time cost.

[0066] Example 2

[0067] This embodiment provides a problem ticket data processing device, which is applied to a problem ticket system and automatically counts the problem ticket data to generate a problem ticket set, such as Figure 4 As shown, including:

[0068] The acquisition module 21 is used to acquire the life cycle corresponding to each problem ticket. For details, please refer to the relevant description of the corresponding step S11 of the above method embodiment, which will not be repeated here.

[0069] The reading module 22 is used to read the pre-divided life cycle intervals from the configuration file, wherein different life cycle intervals are used to distinguish problem tickets of different life cycles. For details, please refer to the relevant description of the corresponding step S12 of the above method embodiment, which will not be repeated here.

[0070] The screening module 23 is used to screen each problem ticket using the life cycle interval as a screening condition to obtain a problem ticket set corresponding to each life cycle interval. For details, please refer to the relevant description of step S13 in the above method embodiment, which will not be repeated here.

[0071] The import module 24 is used to import the problem ticket sets corresponding to each life cycle interval into the target file. For details, please refer to the relevant description of step S14 in the above method embodiment, which will not be repeated here.

[0072] The present embodiment provides a device for processing problem ticket data, which obtains the life cycle corresponding to each problem ticket, uses the life cycle as a screening condition, screens each problem ticket, obtains a problem ticket set corresponding to each life cycle interval, and imports the problem ticket set into a target file. Among them, the acquisition module, reading module, screening module and import module in the device are pre-set program codes. Since they are generated by the program, there is no need for manual acquisition or manual sending, thus reducing labor costs and ensuring the correctness of the exported problem ticket set. Since problem ticket data needs to be exported regularly and the export operation is the same each time, the problem ticket data is exported by the problem ticket data processing device, which avoids the tediousness of regular repeated operations, thereby saving time costs and improving work efficiency.

[0073] As an optional implementation, a form corresponding to each life cycle interval is provided in the target file, and the above-mentioned import module includes:

[0074] The import submodule is used to import the problem sheet set corresponding to each life cycle interval into its corresponding form in turn to obtain the target file of the imported form data. For details, please refer to the relevant description of the corresponding part of the above method embodiment, which will not be repeated here.

[0075] As an optional implementation, the above-mentioned import submodule includes:

[0076] The judgment subunit is used to judge whether the problem ticket set corresponding to each life cycle interval is an empty set. For details, please refer to the relevant description of the corresponding part of the above method embodiment, which will not be repeated here.

[0077] The first import subunit is used to import the problem sheet set into the corresponding form when the problem sheet set is not an empty set. For details, please refer to the relevant description of the corresponding part of the above method embodiment, which will not be repeated here.

[0078] The deletion subunit deletes the form corresponding to the life cycle interval in which the problem ticket set is an empty set when the problem ticket set is an empty set. For details, please refer to the relevant description of the corresponding part of the above method embodiment, which will not be repeated here.

[0079] As an optional implementation, the above-mentioned import submodule further includes:

[0080] The matching subunit is used to match the problem tickets in the problem ticket set using the preset target field, wherein the target field is a characteristic field of the problem ticket that does not need to be processed. For details, please refer to the relevant description of the corresponding part of the above method embodiment, which will not be repeated here.

[0081] The deletion subunit is used to delete the matched problem sheet from the problem set to obtain a problem sheet set after matching. For details, please refer to the relevant description of the corresponding part of the above method embodiment, which will not be repeated here.

[0082] The second import subunit is used to import the problem sheet set after matching into the form of the target file. For details, please refer to the relevant description of the corresponding part of the above method embodiment, which will not be repeated here.

[0083] As an optional implementation, before obtaining module 21, the method further includes:

[0084] The running module is used to run a pre-configured script file, in which a startup command is configured. For details, please refer to the relevant description of step S100 in the above method embodiment, which will not be repeated here.

[0085] The execution module is used to execute the startup command in the script file. For details, please refer to the relevant description of the corresponding step S101 in the above method embodiment, which will not be repeated here.

[0086] The login module is used to log in to the system for storing the problem ticket data. For details, please refer to the relevant description of the corresponding step S102 of the above method embodiment, which will not be repeated here.

[0087] As an optional implementation, after the module 24 is imported, the following is further included:

[0088] The address acquisition module is used to acquire the address list contained in the storage directory corresponding to the target file. For details, please refer to the relevant description of step S15 in the above method embodiment, which will not be repeated here.

[0089] The sending module is used to send the target file to the corresponding target user in the address list according to the address list. For details, please refer to the relevant description of step S16 in the above method embodiment, which will not be repeated here.

[0090] Example 3

[0091] This embodiment provides a computer device, such as Figure 5 As shown, the device includes a processor 31 and a memory 32, wherein the processor 31 and the memory 32 can be connected via a bus or other means. Figure 5 The example of connecting through bus is taken in the following.

[0092] The processor 31 may be a central processing unit (CPU). The processor 31 may also be other general-purpose processors, digital signal processors (DSP), graphics processors (GPU), embedded neural network processors (NPU), or other dedicated deep learning coprocessors, application specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips.

[0093] The memory 32 is a non-transitory computer-readable storage medium that can be used to store non-transitory software programs, non-transitory computer executable programs and modules, such as program instructions / modules corresponding to the method for processing problem ticket data in the embodiment of the present invention (e.g. Figure 4 The processor 31 executes various functional applications and data processing of the processor by running the non-transient software programs, instructions and modules stored in the memory 32, that is, implements the problem ticket data processing method in the above method embodiment.

[0094] The memory 32 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function; the data storage area may store data created by the processor 31, etc. In addition, the memory 32 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some embodiments, the memory 32 may optionally include a memory remotely arranged relative to the processor 31, and these remote memories may be connected to the processor 31 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0095] The one or more modules are stored in the memory 32 and when executed by the processor 31, perform the following steps: Figure 1-Figure 3 The method for processing problem ticket data in the illustrated embodiment.

[0096] The life cycle corresponding to each problem ticket is obtained through the code module, and each problem ticket is screened using the life cycle as the screening condition to obtain the problem ticket set corresponding to each life cycle interval, and the problem ticket set is imported into the target file. Among them, the code module is a pre-set program code. Since it is generated by the program, it does not require manual operation to obtain or send manually, thus reducing labor costs and ensuring the correctness of the exported problem ticket set. Since the problem ticket data needs to be exported regularly and the export operation is the same each time, exporting the problem ticket data through the code module avoids the tediousness of regular repeated operations, thereby saving time costs and improving work efficiency.

[0097] For details of the above computer equipment, please refer to Figures 1 to 4 The corresponding descriptions and effects in the embodiments shown in the figure are understood and will not be repeated here. For technical details not described in detail in this embodiment, please refer to Figures 1 to 4 Related description of the illustrated embodiment.

[0098] The embodiment of the present invention also provides a non-transitory computer storage medium, which stores computer executable instructions, and the computer executable instructions can execute the method for processing the problem ticket data in any of the above method embodiments. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory (Flash Memory), a hard disk (HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above types of memory.

[0099] Obviously, the above embodiments are merely examples for the purpose of clear explanation, and are not intended to limit the implementation methods. For those skilled in the art, other different forms of changes or modifications can be made based on the above description. It is not necessary and impossible to list all the implementation methods here. The obvious changes or modifications derived therefrom are still within the scope of protection of the invention.

Claims

1. A method for processing problem ticket data, It is characterized in that Applied to the problem ticket system, including: The code module obtains the life cycle corresponding to each problem ticket, and the code module is a pre-configured program code; wherein the code module is set in the problem ticket system to automatically obtain the life cycle of each problem ticket; The code module reads pre-divided life cycle intervals from a configuration file, wherein different life cycle intervals are used to distinguish problem tickets of different life cycles; wherein the problem ticket system includes a plurality of problem ticket data, and the life cycle corresponding to each of the problem ticket data is obtained through the configuration file; The code module uses the life cycle interval as a screening condition to screen each problem ticket and obtain a set of problem tickets corresponding to each life cycle interval; wherein the life cycle interval is a filtering condition for problem ticket data, and problem tickets of different life cycles are screened according to the life cycle of the obtained problem ticket; The code module imports the problem ticket sets corresponding to each life cycle interval into the target file respectively; The target file is provided with a form corresponding to each life cycle interval, and the code module imports the problem ticket set corresponding to each life cycle interval into the target file respectively, including: The problem sheet set corresponding to each life cycle interval is imported into its corresponding form in turn to obtain the target file for importing form data.

2. The method according to claim 1, It is characterized in that The step of sequentially importing the problem ticket sets corresponding to each life cycle interval into the corresponding form includes: Determine whether the problem ticket set corresponding to each life cycle interval is an empty set; When the problem set is not an empty set, import it into the corresponding form; When the problem ticket set is an empty set, the form corresponding to the life cycle interval in which the problem ticket set is an empty set is deleted.

3. The method according to claim 1, It is characterized in that Before the code module obtains the life cycle corresponding to each problem ticket, it also includes: Running a pre-configured script file, wherein the script file is configured with a startup command of the code module; Execute the startup command in the script file to start the code module; The code module logs into a system for storing problem ticket data.

4. The method according to claim 1, It is characterized in that After the code module imports the problem ticket sets corresponding to each life cycle interval into the target file respectively, it also includes: The code module obtains an address list contained in a storage directory corresponding to the target file; The code module sends the target file to the corresponding target user in the address list according to the address list.

5. The method according to claim 1, It is characterized in that The step of sequentially importing the problem ticket sets corresponding to each life cycle interval into the corresponding form to obtain the target file for importing the form data includes: Matching the problem tickets in the problem ticket set using a preset target field, wherein the target field is a characteristic field of the problem tickets that do not need to be processed; Deleting the matched problem tickets from the problem set to obtain a set of matched problem tickets; The problem ticket set after matching is imported into the form of the target file.

6. A device for processing problem sheet data, It is characterized in that include: An acquisition module, used to acquire the life cycle corresponding to each problem ticket; wherein the code module is set in the problem ticket system to automatically acquire the life cycle of each problem ticket; A reading module, used to read pre-divided life cycle intervals from a configuration file, wherein different life cycle intervals are used to distinguish problem tickets of different life cycles; wherein the problem ticket system includes a plurality of problem ticket data, and the life cycle corresponding to each of the problem ticket data is obtained through the configuration file; A screening module is used to use the life cycle interval as a screening condition to screen each problem ticket and obtain a set of problem tickets corresponding to each life cycle interval; wherein the life cycle interval is a filtering condition for problem ticket data, and problem tickets of different life cycles are screened according to the life cycle of the obtained problem ticket; The import module is used to import the problem ticket sets corresponding to each life cycle interval into the target file respectively; The target file is provided with a form corresponding to each life cycle interval, and the import module includes: The import submodule is used to import the problem ticket set corresponding to each life cycle interval into its corresponding form in turn to obtain the target file of the imported form data.

7. A computer device, It is characterized in that include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for processing problem ticket data described in any one of claims 1-5 by executing the computer instructions.

8. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the method for processing problem ticket data according to any one of claims 1-5.