Work order content cross-system mapping method and related equipment

Abstract

The embodiment of the invention provides a work order content cross-system mapping method and related equipment, and belongs to the technical field of software product testing. The method comprises the following steps: acquiring a product defect work order from a source work order system; performing target field extraction on the product defect work order to obtain a target field content set; according to the business defect type of the target field content set, determining a corresponding defect template and a defect mapping rule; according to a defect mapping rule, mapping the target field content set into a defect template of a target management system so as to create a work order in the target management system; and backfilling a work order link generated after the target management system creates the work order into the source work order system. According to the embodiment of the invention, the efficiency and accuracy of creating the work order in the target management system can be improved.

Description

Technical Field

[0001] This application relates to the field of software product testing technology, and in particular to a method and related equipment for cross-system mapping of work order content. Background Technology

[0002] In software testing, besides functional testing based on product requirements, handling customer feedback (i.e., "work orders") is another crucial task. This typically involves user issues received by customer service or operations systems, requiring testers to investigate. Currently, the workflow for handling user feedback work orders involves manually creating a new defect (bug) work order in a project management system like TAPD after reproducing and confirming the issue locally or in the test environment. After creating the defect in the TAPD system, it's necessary to return to the original customer work order system and manually fill in information such as the TAPD defect link to establish a connection. This "confirmation-creation-backfilling" process is entirely manual, prone to errors, and inefficient, further impacting the user experience. Summary of the Invention

[0003] The main objective of this application is to propose a method and related equipment for cross-system mapping of work order content, which aims to improve the efficiency and accuracy of creating work orders in the target management system.

[0004] To achieve the above objectives, one aspect of this application proposes a method for cross-system mapping of work order content, comprising the following steps: Retrieve product defect work orders from the source work order system; The target fields of the product defect work order are extracted to obtain a set of target field contents; Based on the business defect type of the target field content set, determine the corresponding defect template and defect mapping rules; According to the defect mapping rules, the target field content set is mapped to the defect template in the target management system to create a work order in the target management system; The work order link generated after the target management system creates a work order is then populated back into the source work order system.

[0005] In some embodiments, after the step of obtaining product defect work orders from the source work order system, the work order content cross-system mapping method further includes the following steps: The product defect work order is preprocessed to obtain a new product defect work order; the preprocessing operation includes removing abnormal characters and standardization operation.

[0006] In some embodiments, extracting target fields from the product defect work order to obtain a set of target field contents includes the following steps: The product defect work order, which is in the form of an array, is indexed at fixed positions in the fields to obtain the source field content. The source field content is mapped according to the target field format of the target management system to obtain the target field content set.

[0007] In some embodiments, the step of extracting target fields from the product defect work order to obtain a set of target field contents further includes the following steps: Based on the association information and content of the product defect work order, keyword matching of the business type is performed to obtain the content of the business type field; Add the content of the business type field to the target field content set.

[0008] In some embodiments, the business defect type of the target field content set is determined through the following steps: A three-level identification strategy is used to identify the business type of the target field content set to obtain the business type; the priority of the three-level identification strategy from high to low is the front-end transmission strategy, the work order name-based identification strategy, and the business keyword-based identification strategy. Defect type identification is performed on the target field content set to obtain the defect type; The business defect type is determined based on the business type and the defect type.

[0009] In some embodiments, the defect type identification of the target field content set to obtain the defect type includes the following steps: Extract the work order number field content from the target field content set; The defect type is obtained by mapping the content of the work order number field.

[0010] To achieve the above objectives, another aspect of this application proposes a cross-system mapping system for work order content, including: The data acquisition module is used to acquire product defect work orders from the source work order system; The field processing module is used to extract target fields from the product defect work order to obtain a set of target field contents. The template matching module is used to determine the corresponding defect template and defect mapping rules based on the business defect type of the target field content set; The mapping module is used to map the target field content set to the defect template in the target management system according to the defect mapping rules, so as to create a work order in the target management system; The backfill module is used to backfill the work order link generated after the target management system creates the work order into the source work order system.

[0011] To achieve the above objectives, another aspect of this application provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described method.

[0012] To achieve the above objectives, another aspect of the embodiments of this application proposes a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.

[0013] To achieve the above objectives, another aspect of the embodiments of this application proposes a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0014] The embodiments of this application include at least the following beneficial effects: This application provides a method, system, electronic device, storage medium, and program product for cross-system mapping of work order content. This solution first obtains product defect work orders from the source work order system, then extracts target fields from the product defect work orders to obtain a set of target field content. Next, based on the business defect type of the target field content set, it determines the corresponding defect template and defect mapping rules. According to the defect mapping rules, the set of target field content is mapped to the defect template in the target management system to create a work order in the target management system. Finally, the work order link generated after the work order is created in the target management system is backfilled into the source work order system. This application automatically creates standardized work orders in the target management system by mapping the target field content of product defect work orders in the source work order system to the target management system according to the defect template, thereby improving the efficiency and accuracy of work order creation in the target management system. Attached Figure Description

[0015] Figure 1 This is a flowchart of the cross-system mapping method for work order content provided in the embodiments of this application; Figure 2 This is a code illustration of indexing source field content at a fixed position, provided in an embodiment of this application. Figure 3 This is a code diagram illustrating the field mapping method provided in the embodiments of this application; Figure 4 This is a code diagram illustrating the work order business type identification process provided in the embodiments of this application; Figure 5 This is a code diagram illustrating the overall process of a work order across systems provided in an embodiment of this application; Figure 6 This is a code diagram illustrating the source field content of the product defect work order provided in this application embodiment; Figure 7This is a code diagram illustrating the target field mapping configuration provided in an embodiment of this application; Figure 8 This is a code diagram illustrating the mapping execution process provided in an embodiment of this application; Figure 9 This is a code diagram illustrating the content mapping process based on defect templates provided in an embodiment of this application; Figure 10 This is a code diagram illustrating the front-end delivery strategy logic provided in an embodiment of this application; Figure 11 This is a schematic diagram of the code for creating the association between the work order number field and the TAPD defect provided in the embodiments of this application; Figure 12 This is a schematic diagram of the code for querying the defect type of the work order provided in an embodiment of this application; Figure 13 This is a code diagram illustrating the overall process of cross-system mapping of education service work orders provided in the embodiments of this application; Figure 14 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0016] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit it. In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.

[0017] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0018] Before providing a detailed description of the embodiments of this application, some of the nouns and terms involved in the embodiments of this application will be explained first. The nouns and terms involved in the embodiments of this application are subject to the following interpretations.

[0019] TAPD (Tencent Agile Product Development) is a one-stop agile R&D collaboration and project management platform independently developed by Tencent. TAPD's core positioning is to provide solutions for the entire product development lifecycle, covering the complete process from product concept formation, requirements planning, iterative development, test management to build release and feedback collection. Specifically, the platform offers a wealth of functional modules, including Kanban boards, online documentation, agile requirements planning, iteration planning and tracking, task and time management, defect tracking management, and test plan and test case management, and supports flexible configuration and on-demand assembly.

[0020] Currently, the workflow for user feedback ticketing involves manually creating a new bug ticket in a project management system like TAPD after the issue is reproduced and confirmed locally or in a test environment. After creating the bug in TAPD, it's necessary to return to the original customer ticketing system and manually fill in information such as the TAPD bug link to establish the association. This "confirmation-creation-backfilling" process has the following problems: 1. Cumbersome process: After the work order is checked, information needs to be filled in manually (TAPD defect information, refilling the work order link) frequently, which is highly repetitive and time-consuming.

[0021] 2. Prone to errors and omissions: Manual data entry is prone to errors or omissions, affecting data accuracy and making it difficult to repair the software product.

[0022] 3. High pressure from multiple business lines: Testers responsible for multiple business lines are prone to confusion about the attribution of defects in work orders, resulting in management chaos.

[0023] 4. Inconvenient tracking of work order processing progress: Errors or omissions in information make it difficult to track the progress of work orders, resulting in low collaboration efficiency, delayed product fixes, and negatively impacting user experience.

[0024] In view of this, this application provides a method and related equipment for cross-system mapping of work order content. This solution maps the target field content in the product defect work order of the source work order system to the target management system according to a suitable defect template, thereby automatically creating business-divided and standardized work orders in the target management system, improving the efficiency and accuracy of creating work orders in the target management system.

[0025] The cross-system mapping method for work order content provided in this application relates to the field of software product testing technology. This method can be applied to terminals, servers, or software running on either a terminal or server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, or in-vehicle terminal, but is not limited to these. The server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The server can also be a node server in a blockchain network. The software can be an application implementing the cross-system mapping method for work order content, but is not limited to the above forms.

[0026] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics devices, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0027] Figure 1 This is an optional flowchart of the cross-system mapping method for work order content provided in the embodiments of this application. Figure 1 The method may include, but is not limited to, steps S101 to S105.

[0028] S101, retrieve product defect work orders from the source work order system; S102, Extract target fields from product defect work orders to obtain a set of target field contents; S103, determine the corresponding defect template and defect mapping rules based on the business defect type of the target field content set; S104. According to the defect mapping rules, map the target field content set to the defect template in the target management system to create a work order in the target management system. S105, populate the work order link generated after the target management system creates the work order back into the source work order system.

[0029] Steps S101 to S105 of this embodiment first obtain product defect work orders from the source work order system, then extract target fields from the product defect work orders to obtain a set of target field content, and then determine the corresponding defect template and defect mapping rules according to the business defect type of the target field content set. Based on the defect mapping rules, the target field content set is mapped to the defect template in the target management system to create a work order in the target management system. Finally, the work order link generated after the work order is created in the target management system is backfilled into the source work order system. This embodiment of the application automatically creates standardized work orders in the target management system by mapping the target field content of the product defect work orders in the source work order system to the target management system according to the defect template, thereby improving the efficiency and accuracy of work order creation in the target management system.

[0030] In step S101 of some embodiments, the source work order system refers to a system oriented towards users or customer service, where users or customer service personnel can report product problems, thereby generating a product defect work order. Generally, a product defect work order includes information such as the handler, the product service name, and a detailed description.

[0031] In step S102 of some embodiments, the target field refers to the field required to be converted to the target management system. For example, the order in the target management system needs to add fields such as handler, order number, business type and order priority. Therefore, it is necessary to process the product defect work order from the source work order system for the above target fields to obtain the target fields and their values ​​(i.e., target field content). Multiple target field contents form a target field content set.

[0032] In step S103 of some embodiments, the business defect type refers to the various order types defined in the target management system. By classifying the target field content set, the business defect type corresponding to the set of content can be obtained. Then, the corresponding defect template and defect mapping rule are selected according to the business defect type. The defect template defines the format of the work order in the target management system, and the defect mapping rule describes how to map the target field content set to the configuration items of the corresponding defect template.

[0033] In step S104 of some embodiments, after determining the corresponding defect template and defect mapping rules based on the business defect type of the target field content set, the target field content set is mapped to the defect template of the target management system using the defect mapping rules. Specifically, the content in the target field content set is extracted according to the instructions of the defect mapping rules and filled into the appropriate position in the defect template to form a defect work order, thereby realizing the creation of a work order in the target management system. In this embodiment, the target management system is a product project management system (such as the TAPD system) for developers or managers. It includes a product maintenance template, and the product maintenance module is used to display product defect work orders to remind developers to follow up on maintenance. This embodiment extracts the content from the source work order system and fills the corresponding defect model according to different business defect types, thereby automatically creating work orders in the target management system, improving the efficiency and accuracy of cross-system mapping of work orders. In addition, this application embodiment also divides product defect work orders into corresponding business defect types and creates work orders that conform to the format in the corresponding business workspace of the target management system, avoiding the problem of chaotic work order management in the target management system.

[0034] In step S105 of some embodiments, after creating a work order, the target management system simultaneously generates a work order link. The system in this embodiment further obtains this work order link and automatically populates it back into the corresponding product defect work order in the source work order system, so that users or customer service personnel can easily query the product maintenance progress in the target management system through the source work order system. According to some embodiments of this application, after step S101, the cross-system mapping method for work order content in this application may also include, but is not limited to, the following steps: S201, perform preprocessing operations on product defect work orders to obtain new product defect work orders; the preprocessing operations include removing abnormal characters and standardization operations.

[0035] In this embodiment, the description field of the product defect work order in the source work order system may contain a large number of HTML tags and special characters. Without data cleaning and formatting, subsequent defect creation will fail. Furthermore, the work order fields in the TAPD system have length limits and other formatting requirements. Therefore, certain preprocessing strategies are needed to preprocess the product defect work orders to obtain content that conforms to the TAPD system. The preprocessing operations in this embodiment may include, but are not limited to, data cleaning and standardization, as detailed below: Text cleaning operations include, but are not limited to, HTML tag cleaning, HTML entity decoding, whitespace character normalization, length control, and intelligent truncation; Type unification operation, that is, all fields are uniformly converted to the target type field; Mapping and transformation operation: This involves using a value mapping table established from the source work order system to the target management system to map the values ​​of the field contents. Exception handling: Provides default values ​​for cases of conversion failure or missing fields; Log operations: Record the conversion process to facilitate troubleshooting.

[0036] According to some embodiments of this application, step S102 may include, but is not limited to, the following steps: S301, perform fixed-position indexing on the fields of the product defect work order in array structure to obtain the source field content; S302, Map the source field content to the target field content according to the target field format of the target management system to obtain the target field content set.

[0037] In step S301 of some embodiments, the product defect orders obtained from the source work order system are complex and non-standard. Product defect orders are generally stored in array structure, but the data types are inconsistent and there are no specific field names. The same field may be a string, number or null value in different work orders. A large amount of content exists in a complex structure with multiple nested layers, making it difficult to extract the target field. Therefore, the embodiments of this application can use reverse engineering and data structure analysis to crack the data format, thereby extracting the required original field content. Specifically, a large number of work order data samples of different business types (such as education business, game business) and different states can be collected. By comparative analysis, the meaning of the fields at each position of the array can be identified, thereby obtaining the fixed position of certain source field content (i.e., the value of the source field). Subsequently, in the actual cross-system mapping process, the fixed position index of the field of the product defect work order in array structure is performed to obtain the source field content. For example, by using the array index position (such as form_data[0] is the work order ID and form_data[9] is the acceptor), by parsing the formData.data JSON string, the key-value pair of the field ID and value is extracted to obtain the source field content. The source field content is obtained by using the fixed position index of the source field content, such as Figure 2 As shown in the code.

[0038] In step S302 of some embodiments, after obtaining the source field content, it is necessary to map the source field content to the target field content of the target management system. For example, the work order of the target management system may have content such as TAPD user, order number, business type, priority, and order number. Embodiments of this application can provide multiple mapping methods to map the target field content from the extracted source field content. These mapping methods include, but are not limited to, fixed value mapping (such as priority), direct mapping (such as order number), query mapping based on source field content (such as TAPD user), calculation mapping based on source field content, or form mapping. The field mapping implementation in embodiments of this application can be achieved through BusinessFieldMappingService, supporting multiple mapping methods, such as... Figure 3 The code is shown below.

[0039] According to some embodiments of this application, step S102 may also include, but is not limited to, the following steps: S401, based on the associated information and content of the product defect work order, perform keyword matching of the business type to obtain the content of the business type field; S402, Add the business type field content to the target field content collection.

[0040] In this embodiment, the target fields required by the target management system generally also include business type fields. The identification of business type fields can be based on keyword matching. This embodiment employs a three-level progressive, step-down identification strategy, which can still identify the business type to the greatest extent possible even when information is incomplete or the format is inconsistent. Level 1: Exact Match (Most Accurate): Extract the two fields, flowTaskName (process task name) and currentTaskName (current task name), from the extra fields of the work order.

[0041] The two names are compared to the entire set of predefined business keywords for complete consistency. For example, if the value of flowTaskName is "Education Development Follow-up", and "Education Development Follow-up" is explicitly classified as "edu" (education) business in the system configuration, then the work order is directly determined to be an education business work order.

[0042] The first-level strategy utilizes the system's built-in, standardized process names for accurate and rapid identification.

[0043] Level 2: Fuzzy matching (error-tolerant processing): When no exact match is found, the system checks if the `flowTaskName` or `currentTaskName` contains keywords related to a specific business function. For example, if the task name is "Education - Emergency Online Issue Handling," while not exactly the same as "Education Development Follow-up," it contains the keyword "education," leading the system to determine it belongs to the "edu" business category. This second-level strategy can handle work orders with slightly different names but a clear core business focus, improving the system's fault tolerance and coverage.

[0044] Level 3: In-depth analysis (fallback plan): When both exact and fuzzy matching fail, a third-level strategy is activated, searching within the more detailed content area of ​​the work order—the formFields. FormFields are typically text strings containing a detailed problem description filled in by the user. Within this long text, all predefined business keywords are searched. For example, suppose a work order has a vague task name, "Technical Problem Handling," but its description (formFields) mentions "Our online store's payment page cannot be opened," containing the keyword "online store." The system would then determine that the work order belongs to the "mall" business category. This third-level strategy serves as a final fallback identification method, striving to extract business clues from the detailed content of the work order to avoid "unidentifiable" work orders. The work order business type identification process is as follows: Figure 4 The code is shown below.

[0045] Taking the education business as an example, the overall process of mapping product defect work orders from the source order system to the target management system is as follows: Figure 5 As shown in the code, it mainly includes three core logics: business mapping configuration, field mapping, and TAPD work order object creation. The source field content of the product defect work order is as follows: Figure 6 As shown in the code, the target field mapping configuration is as follows: Figure 7 As shown in the code, the mapping execution process is as follows: Figure 8 As shown in the code, the content mapping process based on the defect template is as follows: Figure 9 The code is shown below. During the field mapping process described above, fields are uniformly converted to string type to avoid type errors; reasonable default values ​​are provided for null values; and alternative fields are used when the primary field is missing.

[0046] According to some embodiments of this application, the business defect type of the target field content set can be determined by, but is not limited to, the following steps: S501 employs a three-level identification strategy to identify the business type of the target field content set and obtain the business type; the priority of the three-level identification strategy from high to low is the front-end transmission strategy, the work order name-based identification strategy, and the business keyword-based identification strategy. S502, perform defect type identification on the target field content set to obtain the defect type; S503, determine the business defect type based on the business type and defect type.

[0047] In this embodiment, the rules and fields for the defect template of each business are not consistent, and different expression methods may be required for different defect types. For example, the urgency of different defect types is different, and their work order expression methods are also different. That is, work orders of the same business but with different defect types need to use different defect templates. Based on this, this application embodiment identifies the business type and defect type, and then determines the corresponding defect template and the corresponding defect mapping rules based on the combination of business type and defect type.

[0048] For example, we can first sort out the workspace_id and work order defect template_id of the seven main business in the target management system, obtain the defect template list through the workspace, and then obtain all the contents of a specific template; then communicate with the testers of each business to configure mapping rules according to the specific defect template of the specific business; when creating a defect, submit it to the ordinary or emergency work order defect template according to the business type and judgment of the defect, so that testers no longer need to manually create work order defects, realize the automatic completion of the work order → defect → backfilling link, and avoid omissions and errors, improve efficiency and facilitate the tracking of work order processing progress.

[0049] Specifically, this application embodiment can employ a three-level identification strategy to determine the business type corresponding to the aforementioned target field content set. The priority of the three-level identification strategy, from high to low, is: front-end delivery strategy, work order name-based identification strategy, and business keyword-based identification strategy. The corresponding strategy is selected sequentially according to priority. If a higher-priority strategy cannot identify the business type, a lower-level strategy is then used to identify the business type. The front-end delivery strategy refers to using the business type specified by the front-end personnel. The logic of the front-end delivery strategy is as follows: Figure 10 The code is shown below. The work order name-based identification strategy matches business keywords using work order task names such as `flowTaskName` or `currentTaskName`, for example, the name "Education Test Follow-up" corresponds to the "edu" business. The business keyword-based identification strategy searches for business keywords in the `formFields` string. This embodiment uses a three-level identification strategy to improve the reliability of business identification.

[0050] According to some embodiments of this application, step S502 may include, but is not limited to, the following steps: S601, Extract the work order number field content from the target field content set; S602, perform defect type mapping on the work order number field to obtain the defect type.

[0051] In this embodiment, the TAPD system has custom fields corresponding to each defect type. When creating a product defect work order in the source work order system, the defect type of that product defect work order can be specified simultaneously. Based on the specified defect type, the system in this embodiment stores the order number of the work order as a value in the custom defect field. For example, the system establishes the association between the work order and the TAPD defect through the work order number field. Figure 11 The code shows that the work order ID is written to the `custom_field_two` field of the TAPD defect. When selecting a mapping template, the defect type of the work order is queried as follows: Figure 12 The code shows that it performs a reverse lookup using the custom_field_two field of the TAPD API.

[0052] According to some embodiments of this application, the overall process of processing a cross-system mapping of an education service work order is as follows: Figure 13 The code is shown below.

[0053] According to some embodiments of this application, step S105 may include, but is not limited to, the following steps: S701, Generate a backfill request based on the work order link generated after the work order is created in the target management system; S702, initiates a backfill request to the source work order system to backfill the work order link to the source work order system; controls the number of requests when initiating the backfill request and adopts a retry mechanism for failed requests.

[0054] In this embodiment, when creating a large number of defects in batches, backfilling the defect links into the corresponding work order system will fail. This is because the session / cookie has an expiration time after login, and currently, for privacy reasons, only one member account is usually configured. Multiple concurrent requests can lead to session conflicts, causing the backfilling process to easily fail. Therefore, the system in this embodiment can add a global semaphore to the backfilling requests to limit the number of concurrent requests and avoid login conflicts caused by excessive concurrent operations. For failed backfilling requests, a silent retry mechanism is used, asynchronously starting a retry task after a failure, without blocking the main process of creating defects. For the TAPD system, a debouncing mechanism can be added to prevent repeated clicks from sending multiple backfilling requests.

[0055] This application also provides a cross-system mapping system for work order content, including: The data acquisition module is used to acquire product defect work orders from the source work order system; The field processing module is used to extract target fields from product defect work orders and obtain a set of target field contents. The template matching module is used to determine the corresponding defect template and defect mapping rules based on the business defect type of the target field content set; The mapping module is used to map the target field content set to the defect template in the target management system according to the defect mapping rules, so as to create a work order in the target management system; The backfill module is used to backfill the work order link generated after the target management system creates a work order into the source work order system.

[0056] According to some embodiments of this application, the cross-system mapping system for work order content can be implemented using AI, and the specific design method is as follows: I. Consider the tools used for setup: An IDE (Integrated Development Environment) can be used, such as Cursor / VS Code; AI tools can be used, such as Augment.

[0057] II. Consider the system's technical architecture: The front-end is responsible for the visual management of work orders: The front-end of the system in this embodiment of the application has functions such as filtering work orders according to various query conditions, configuring templates, and submitting historical queries; The backend carries business logic: The system backend of this application embodiment has functions such as work order search, defect creation, field mapping, and concurrent processing; Database: Stores commit history; Based on the above technical approach, the front-end technology stack and back-end technology stack were selected.

[0058] III. Setup Process: 1. Preparations: (1) Compile a list of key API interfaces, including but not limited to the work order authentication interface, work order search interface, work order details interface, work order update interface (for backfilling), the create defect interface, get template list interface, and get custom field interface in the TAPD API interface.

[0059] (2) Organize information on business types, business identifiers, workspace information, such as information on e-commerce, education, mini-programs, website building, etc.

[0060] 2. Based on the above information, organize the AI ​​dialogue content to enable the AI ​​to generate system code. The system design of this embodiment can be divided into five stages of questioning, each stage having a "standard prompt," and specifying the output format and acceptance checklist, so that the AI's output can be directly implemented into the code: (1) During the project initialization phase, the question text is as follows: I need to build a work order to TAPD defect synchronization system. The core functionality is: 1. Work order query (multi-condition filtering); 2. Batch creation of TAPD defects (automatic field mapping); 3. Automatically fill in the link to the work order; 4. Submission history; 5. Template configuration management.

[0061] Technology stack: ... User: For daily use by test engineers; Objective: To improve work order processing efficiency and reduce manual operations.

[0062] Based on the above requirements, please help me design the overall architecture and development plan.

[0063] (2) During the API integration phase, the question text is as follows: I have two external APIs that I need to integrate: Work order system API: Login API: ... Search API: ... API details: ... API Update: ... TAPD API: Creating a defect API: ... Authentication API: ... Based on the information provided, design a reasonable API integration scheme and field mapping mechanism.

[0064] (3) During the front-end development phase, the question text is as follows: To develop the front-end, these pages are needed: 1. The work order query page includes conditional filtering, table display, and batch selection functions; 2. Submission history page, including operation records and status viewing functions; 3. Configure the management page, including field mapping configuration functionality; Technical requirements: ... Core features: batch operations, real-time feedback, responsive design; First, implement the complete code for the work order query page.

[0065] (4) During the backend development phase, the question text is as follows: Now, let's develop the backend service: 1. FastAPI framework, asynchronous processing; 2. Core API: ... 3. Business services: work order query, TAPD integration, field mapping, batch processing; 4. Database: SQLite, used to store commit history; Key features: Supports concurrent processing of work orders from multiple users across multiple business processes, with robust error handling; First, implement the core service for creating TAPD defects.

[0066] (5) During the deployment phase, the question text is as follows: Creating a Windows deployment plan: 1. One-click startup script (start-tapdit.bat); 2. Precisely stop the script (based on ports 8000 and 5173); 3. Health checks and error handling; 4. Performance optimization (asynchronous concurrency, connection pooling); Requirements: Simple and easy to use, suitable for non-technical personnel.

[0067] Mapping mechanism: Key information in a work order (title, description, business identifier) ​​will be automatically mapped to the TAPD defect field.

[0068] After a defect is successfully created, the defect link will call the work order update interface and populate the corresponding work order.

[0069] It supports custom mapping rules based on business needs, adapting to different project requirements.

[0070] In some embodiments, the system of this application specifically comprises: the system homepage displays entry points for work order query, template mapping, and submission history query; the work order query page allows filtering of accepted work orders based on business, acceptor, and time, and provides quick access to specific work orders and defect records; the queried work order data list displays an indicator of whether the work order needs to create a TAPD defect, allowing for the creation of defects individually or in batches, followed by calling the tapd API to create the defect to the corresponding work order defect template under the business, and the defect link will be populated back to the work order after successful creation; the template mapping page allows for the configuration of mapping rules for each business.

[0071] It is understood that the methods described in the above method embodiments are applicable to this system embodiment. The specific functions implemented in this system embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0072] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described method. This electronic device can be any smart terminal, including tablet computers, in-vehicle computers, etc.

[0073] It is understood that the content of the above method embodiments is applicable to this device embodiment. The specific functions implemented by this device embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0074] Please see Figure 14 , Figure 14 The hardware structure of an electronic device according to another embodiment is illustrated. The electronic device includes: The processor 901 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application. The memory 902 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 902 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 902 and is called and executed by the processor 901. The input / output interface 903 is used to implement information input and output; The communication interface 904 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). Bus 905 transmits information between various components of the device (e.g., processor 901, memory 902, input / output interface 903, and communication interface 904); The processor 901, memory 902, input / output interface 903, and communication interface 904 are connected to each other within the device via bus 905.

[0075] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.

[0076] It is understood that the content of the above method embodiments is applicable to this storage medium embodiment. The specific functions implemented in this storage medium embodiment are the same as those in the above method embodiments, and the beneficial effects achieved are also the same as those achieved in the above method embodiments.

[0077] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0078] It is understood that the content of the above method embodiments is applicable to the embodiments of this program product. The specific functions implemented by the embodiments of this program product are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0079] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0080] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0081] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0082] The system embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0083] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0084] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0085] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0086] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of modules described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0087] The modules described above as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0088] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0089] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0090] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A method for mapping work order content across systems, characterized in that, Includes the following steps: Retrieve product defect work orders from the source work order system; The target fields of the product defect work order are extracted to obtain a set of target field contents; Based on the business defect type of the target field content set, determine the corresponding defect template and defect mapping rules; According to the defect mapping rules, the target field content set is mapped to the defect template in the target management system to create a work order in the target management system; The work order link generated after the target management system creates a work order is then populated back into the source work order system.

2. The cross-system mapping method for work order content according to claim 1, characterized in that, Following the step of obtaining product defect work orders from the source work order system, the work order content cross-system mapping method further includes the following steps: The product defect work order is preprocessed to obtain a new product defect work order; the preprocessing operation includes removing abnormal characters and standardization operation.

3. The cross-system mapping method for work order content according to claim 1, characterized in that, The process of extracting target fields from the product defect work order to obtain a set of target field contents includes the following steps: The product defect work order, which is in the form of an array, is indexed at fixed positions in the fields to obtain the source field content. The source field content is mapped according to the target field format of the target management system to obtain the target field content set.

4. The cross-system mapping method for work order content according to claim 3, characterized in that, The process involves extracting target fields from the product defect work order to obtain a set of target field contents. The following steps are included: Based on the association information and content of the product defect work order, keyword matching of the business type is performed to obtain the content of the business type field; Add the content of the business type field to the target field content set.

5. The cross-system mapping method for work order content according to claim 1, characterized in that, The business defect type of the target field content set is determined through the following steps: A three-level identification strategy is used to identify the business type of the target field content set to obtain the business type; the priority of the three-level identification strategy from high to low is the front-end transmission strategy, the work order name-based identification strategy, and the business keyword-based identification strategy. Defect type identification is performed on the target field content set to obtain the defect type; The business defect type is determined based on the business type and the defect type.

6. The cross-system mapping method for work order content according to claim 5, characterized in that, The defect type identification of the target field content set to obtain the defect type includes the following steps: Extract the work order number field content from the target field content set; The defect type is obtained by mapping the content of the work order number field.

7. A cross-system mapping system for work order content, characterized in that, include: The data acquisition module is used to acquire product defect work orders from the source work order system; The field processing module is used to extract target fields from the product defect work order to obtain a set of target field contents. The template matching module is used to determine the corresponding defect template and defect mapping rules based on the business defect type of the target field content set; The mapping module is used to map the target field content set to the defect template in the target management system according to the defect mapping rules, so as to create a work order in the target management system; The backfill module is used to backfill the work order link generated after the target management system creates the work order into the source work order system.

8. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 6.

Images