Production task pushing method and device, equipment and storage medium
By splitting and pushing production task orders to the collaboration space of the target development team, the problems of low efficiency and high error rate of manual recording were solved, and efficient and accurate production task pushing was achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- BANK OF CHINA
- Filing Date
- 2021-11-12
- Publication Date
- 2026-07-31
AI Technical Summary
In existing technologies, the method of manually recording production task orders by recorders is inefficient and prone to errors, especially when there are many development teams and production tasks, making it difficult to efficiently push production tasks.
The first device acquires the production task order, which is then broken down into sub-production task orders based on the product name. Based on the correspondence between the product and the development team, the target development team is determined, and the sub-production task orders are pushed to the collaboration space of the target development team using preset push rules, thus providing a collaborative environment.
It enables precise delivery of production tasks, improves the efficiency of developers and testers in obtaining production tasks, reduces the probability of errors, and optimizes the scheduling process of production tasks.
Smart Images
Figure CN113988698B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of artificial intelligence, and in particular to a method, apparatus, device and storage medium for pushing production tasks. Background Technology
[0002] Agile development refers to software development that focuses on customer needs and employs iterative and incremental methodologies. Agile development requires collaboration between process personnel and the development team. Process personnel can include managers and record keepers, while the development team can include product owners (POs), iteration masters (SMs), developers, and testers.
[0003] For example, product managers can obtain customer requirements and formulate production tasks based on them. Managers can obtain production tasks sent by product managers. The production task management system can obtain production tasks entered by managers and generate production task sheets, which may include one or more production tasks. Recorders can manually record production task sheets from the production task management system and send them to developers or testers. Developers can obtain the production task sheets sent by recorders and write program code in the iteration process management system based on the production tasks recorded in the sheets to generate the software product, which requires multiple version iterations. Testers can also obtain the production task sheets sent by recorders and write test cases in the iteration process management system based on the production tasks recorded in the sheets, using the test cases to test the software product. During the software product version iteration process or during testing, product managers, iteration managers, developers, and testers can also hold daily meetings to discuss problems that arise during version iteration or testing. After testing is completed, the tested software product can be released.
[0004] However, obtaining production tasks by manually recording production task sheets is inefficient, and manual recording is prone to errors when there are many development teams and production tasks. Summary of the Invention
[0005] This application provides a production task push method, apparatus, device, and storage medium, which can improve the efficiency of developers and testers in obtaining production tasks.
[0006] Firstly, this application provides a production task push method, which includes: a first device acquiring a production task order, the production task order including product names, with a one-to-one correspondence between product names and products, and a one-to-one correspondence between products and development teams. The first device splits the production task order into one or more sub-production task orders based on the product names in the production task order. For each sub-production task order, the first device determines the target development team corresponding to the sub-production task order based on the correspondence between products and development teams; the first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to a preset push rule, the collaboration space corresponding to the target development team being used to provide a working environment for the target development team.
[0007] In one possible implementation, the method further includes: for each sub-production task order, the first device determines the type of the sub-production task order based on whether it includes a version name, wherein the type includes either a first sub-production task order or a second sub-production task order, where the first sub-production task order includes a version name and the second sub-production task order does not. The first device then pushes the sub-production task order to the collaboration space corresponding to the target development team according to a preset push rule, including: the first device pushes the sub-production task order to the collaboration space corresponding to the target development team based on the type of the sub-production task order and the preset push rule.
[0008] In another possible implementation, the first sub-production task order also includes a first time. The method further includes: the first device determining the version plan corresponding to each first sub-production task order based on the first time and the version name. The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the type of sub-production task order and the preset push rules, including: when the sub-production task order is the first sub-production task order, the first device pushes the first sub-production task order and the version plan corresponding to the first sub-production task order to the collaboration space corresponding to the target development team according to the preset push rules.
[0009] In another possible implementation, the sub-production task order also includes a first time. The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to a preset push rule, including: the first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the first time and the preset push rule.
[0010] In another possible implementation, the first time includes the second time. The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the first time and the preset push rules, including: the first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the second time and the preset push rules.
[0011] In another possible implementation, the first time includes the third time. The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the first time and the preset push rules, including: the first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the third time and the preset push rules.
[0012] In another possible implementation, the method further includes: the first device sending a prompt message to the collaboration space corresponding to the target development team at a first time, the prompt message being used to remind the members of the target development team to complete the production task in a timely manner.
[0013] In another possible implementation, the first device is connected to the second device. The first device acquires the production task order, including receiving the production task order sent by the second device.
[0014] In another possible implementation, the first device is further used to record the record information corresponding to each sub-production task order. The method further includes: the first device receiving first information, which is sent by the second device when a sub-production task order exists in a first state; the first information corresponds one-to-one with the sub-production task order; the first information indicates that the sub-production task order corresponding to the first information exists in a first state, which includes a deletion state or a modification state; the first device responding to the first information by deleting the sub-production task order corresponding to the first information and the record information corresponding to that sub-production task order, or by saving the sub-production task order corresponding to the first information and the record information corresponding to that sub-production task order.
[0015] In the production task push method provided in this application, the first device can provide a collaboration space for the development team, and there is a corresponding relationship between the development team and the collaboration space. The first device can obtain production task orders, which can include product names, with a one-to-one correspondence between product names and products, and a one-to-one correspondence between products and development teams. The first device can split the production task order into one or more sub-production task orders. For each sub-production task order, the first device can determine the target development team corresponding to the sub-production task order based on the correspondence between products and development teams, and push the sub-production task order to the collaboration space corresponding to the target development team. Developers and testers can obtain production tasks based on the sub-production task orders pushed by the first device, eliminating the need for manual recording, improving the efficiency of developers and testers in obtaining production tasks, and reducing the probability of errors in the obtained production tasks.
[0016] Secondly, this application provides a production task push device, which is applied to a first device. The device includes a production task order acquisition module, a production task order splitting module, and a sub-production task order processing module. The production task order acquisition module acquires production task orders, which include product names, with a one-to-one correspondence between product names and products, and a one-to-one correspondence between products and development teams. The production task order splitting module splits the production task order into one or more sub-production task orders based on the product names in the production task order. The sub-production task order processing module, for each sub-production task order, determines the target development team corresponding to the sub-production task order based on the correspondence between products and development teams; and pushes the sub-production task order to the collaboration space corresponding to the target development team according to preset push rules. The collaboration space corresponding to the target development team provides a working environment for the target development team.
[0017] In one possible implementation, the device may further include a rule configuration module. The rule configuration module is used to obtain push rules.
[0018] In another possible implementation, the sub-production task processing module is further used to determine the type of each sub-production task based on whether it includes a version name. The type includes either a first sub-production task or a second sub-production task. The first sub-production task includes a version name, while the second sub-production task does not. Specifically, the sub-production task processing module is used to push the sub-production task to the corresponding collaboration space of the target development team based on its type and preset push rules.
[0019] In another possible implementation, the first sub-production task order also includes a first time. The sub-production task order processing module is further used to determine the version plan corresponding to each first sub-production task order based on the first time and the version name. Specifically, when the sub-production task order is the first sub-production task order, the sub-production task order processing module pushes the first sub-production task order and its corresponding version plan to the collaboration space corresponding to the target development team according to preset push rules.
[0020] In another possible implementation, the sub-production task order also includes a first-time event. The sub-production task order processing module is specifically used to push the sub-production task order to the collaboration space corresponding to the target development team based on the first-time event and preset push rules.
[0021] In another possible implementation, the first time includes the second time. The sub-production task processing module is specifically used to push the sub-production task to the collaboration space corresponding to the target development team according to the second time and preset push rules.
[0022] In another possible implementation, the first time includes the third time. The sub-production task processing module is specifically used to push the sub-production task to the collaboration space corresponding to the target development team according to the third time and the preset push rules.
[0023] In another possible implementation, the sub-production task processing module is also used to send a prompt message to the collaboration space corresponding to the target development team as soon as possible. The prompt message is used to remind the members of the target development team to complete the production task in a timely manner.
[0024] In another possible implementation, the first device is connected to the second device. The production task order acquisition module is specifically used to receive production task orders sent by the second device.
[0025] In another possible implementation, the device further includes a data monitoring and anomaly handling module. This module records the information corresponding to each sub-production task order; receives first information sent by a second device when a sub-production task order is in a first state; the first information corresponds one-to-one with each sub-production task order; and the first information indicates that the sub-production task order corresponding to the first information is in a first state, which may include a deletion state or a modification state. In response to the first information, the module deletes the sub-production task order corresponding to the first information and the corresponding record information, or saves the sub-production task order corresponding to the first information and the corresponding record information.
[0026] In another possible implementation, the device further includes a front-end management module. The front-end management module provides a visual list of sub-production task orders. This list can include one or more development teams, each corresponding to one or more sub-production task orders. Each sub-production task order can have its own corresponding status identifier, which can include a first identifier and a second identifier. The first identifier indicates that the production task corresponding to the sub-production task order has been completed, and the second identifier indicates that the production task corresponding to the sub-production task order has not been completed.
[0027] Thirdly, this application provides a computer program product that, when run on a computer, causes the computer to execute the steps of the related method described in the first aspect, so as to realize the production task push method described in the first aspect.
[0028] Fourthly, this application provides an electronic device comprising: a processor and a memory; the memory storing processor-executable instructions; when the processor is configured to execute the instructions, causing the electronic device to perform the method described in the first aspect above.
[0029] Fifthly, this application provides a computer-readable storage medium comprising: computer software instructions; when the computer software instructions are executed in an electronic device, they cause the electronic device to perform the method described in the first aspect above.
[0030] The beneficial effects of the second to fifth aspects mentioned above can be referred to the first aspect, and will not be repeated here. Attached Figure Description
[0031] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0032] Figure 1 A flowchart illustrating the agile development process;
[0033] Figure 2 A flowchart illustrating the production task push method provided in this application embodiment;
[0034] Figure 3 This is a schematic diagram of the connection relationship of the first device provided in an embodiment of this application;
[0035] Figure 4 Another flowchart illustrating the production task push method provided in this application embodiment;
[0036] Figure 5 This is another flowchart illustrating the production task push method provided in an embodiment of this application;
[0037] Figure 6 This is a schematic diagram of the composition of the production task push device provided in the embodiments of this application;
[0038] Figure 7 Another schematic diagram of the production task push device provided in the embodiments of this application;
[0039] Figure 8 Another schematic diagram of the production task push device provided in the embodiments of this application;
[0040] Figure 9 Another schematic diagram of the production task push device provided in the embodiments of this application;
[0041] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0042] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0043] It should be noted that in the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.
[0044] To facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish the same or similar items with essentially the same function and effect. Those skilled in the art can understand that the terms "first" and "second" are not intended to limit the quantity or execution order.
[0045] Agile development refers to software development that focuses on customer needs and employs iterative and incremental methodologies. Agile development requires collaboration between process engineers and the development team. Process engineers may include managers and record keepers, while the development team may include product managers, iteration managers, developers, and testers.
[0046] For example, Figure 1 A flowchart illustrating the agile development process. (Example) Figure 1As shown, product managers can obtain customer requirements and formulate production tasks based on them. Managers can obtain production tasks sent by product managers. The production task management system can obtain production tasks entered by managers and generate production task sheets, which may include one or more production tasks. Recorders can manually record production task sheets from the production task management system and send them to developers or testers. Developers can obtain the production task sheets sent by recorders and write program code in the iteration process management system based on the production tasks recorded in the sheets to generate the software product, which requires multiple version iterations. Testers can also obtain the production task sheets sent by recorders and write test cases in the iteration process management system based on the production tasks recorded in the sheets, using the test cases to test the software product. During the software product version iteration process or during testing, product managers, iteration managers, developers, and testers can hold daily meetings to discuss problems that arise during version iteration or testing. After testing is completed, the tested software product can be released.
[0047] However, obtaining production tasks by manually recording production task sheets is inefficient, and manual recording is prone to errors when there are many development teams and production tasks.
[0048] This application provides a method for pushing production tasks. This method obtains a production task order, which may include product names, each corresponding to a specific product and a specific development team. The production task order is then divided into one or more sub-production task orders based on the product names. For each sub-production task order: the target development team corresponding to the sub-production task order is determined based on the correspondence between the product and the development team; and the sub-production task order is pushed to the target development team according to a preset push rule. This method allows production tasks to be pushed to the development team in a timely and accurate manner.
[0049] In some embodiments, the iterative process management system can be deployed in a computing device such as a computer or server. The server can be a single server or a server cluster consisting of multiple servers. In some embodiments, the server cluster can also be a distributed cluster. This application does not limit the specific form of the entity executing the method.
[0050] The production task push method provided in this application will be described in detail below through specific embodiments.
[0051] Figure 2 This is a flowchart illustrating the production task push method provided in an embodiment of this application. Figure 2As shown, the method may include S201 to S204.
[0052] S201, The first equipment obtains the production task order.
[0053] As mentioned above, the iterative process management system can be distributed across devices with computing capabilities, such as computers and servers. The first device can be a device that includes the aforementioned iterative process management system. Production task sheets can include information such as project name, task batch, requirement number, key dates, product name, and workload. Project names can correspond one-to-one with projects. Product names can correspond one-to-one with products. A project can correspond to one or more products. Key dates can include the planned submission date for the functional test version and the planned submission date for the production version. Key dates can also be referred to as the first date.
[0054] In some possible embodiments, the production task management system described above can be distributed in a second device, that is, the second device may include the production task management system. The second device may include the first device, or the second device may not include the first device, that is, the production task management system and the iterative process management system may be distributed on the same server, or they may be distributed on different servers.
[0055] In one possible implementation, when the second device includes the first device, that is, when the production task management system and the iterative process management system are deployed on the same server, this server can be referred to as either the first device or the second device. The first device acquiring the production task order may include: the first device receiving production tasks input by the management personnel; and the first device generating a production task order based on the production tasks input by the management personnel.
[0056] In another possible implementation, when the second device does not include the first device, that is, when the production task management system and the iterative process management system are deployed on different servers, the second device can obtain the production tasks input by the management personnel; the second device generates a production task order based on the production tasks input by the management personnel; and the second device sends the production task order to the first device. Figure 3 This is a schematic diagram illustrating the connection relationship of the first device provided in an embodiment of this application. (See attached diagram.) Figure 3 As shown, the first device 310 and the second device 320 can be connected via a wired network or a wireless network. The first device acquiring the production task order may include: the first device 310 receiving the production task order sent by the second device 320.
[0057] The production task push method provided in this application embodiment can also connect the data link between the production task system and the iterative process management system, providing support for the accurate push of production tasks.
[0058] It should be noted that for the same product in the same project, the first device can obtain production task orders for that product at different times.
[0059] For example, the production task order obtained by the first device on November 1, 2021, can be as shown in Table 1 below. The production task order obtained by the first device on November 4, 2021, can be as shown in Table 2 below.
[0060] Table 1
[0061]
[0062] As shown in Table 1, the production task order obtained by the first equipment on November 1, 2021 may include items such as project name, product name, requirement number, key time, and workload.
[0063] The key time items can include the planned submission date for the functional test version and the planned submission date for the production version. The project name item can include project names such as "Project 1" and "Project 2". The product name can include product names such as "Product A", "Product B", and "Product C". The requirement number item can include requirement numbers such as "Requirement Number 1", "Requirement Number 2", and "Requirement Number 3". The planned submission date for the functional test version can include planned submission dates such as "Time Point 1", "Time Point 3", and "Time Point 5". The planned submission date for the production version can include planned submission dates such as "Time Point 2", "Time Point 4", and "Time Point 6". The workload item can include workloads such as "Workload 1", "Workload 2", and "Workload 3".
[0064] The project name "Project 1", product name "Product A", requirement number "Requirement Number 1", planned submission date for functional test version "Time Point 1", planned submission date for production version "Time Point 2", and workload "Workload 1" have a corresponding relationship. The project name "Project 1", product name "Product B", requirement number "Requirement Number 2", planned submission date for functional test version "Time Point 3", planned submission date for production version "Time Point 4", and workload "Workload 2" have a corresponding relationship. The project name "Project 2", product name "Product C", requirement number "Requirement Number 3", planned submission date for functional test version "Time Point 5", planned submission date for production version "Time Point 6", and workload "Workload 3" have a corresponding relationship.
[0065] Table 2
[0066]
[0067] As shown in Table 2, the production task order obtained by the first equipment on November 4, 2021 may include the product "Product A" and the corresponding project name "Project 1", requirement number "Requirement Number 4", planned submission time for functional test version "Time Point 1", planned submission time for production version "Time Point 2", and workload "Workload 1" from the production task order obtained by the first equipment on November 1, 2021. It may also include the product "Product D" not included in the production task order obtained by the first equipment on November 1, 2021, and the corresponding project name "Project 2", requirement number "Requirement Number 5", planned submission time for functional test version "Time Point 7", planned submission time for production version "Time Point 8", and workload "Workload 4".
[0068] S202. The first equipment splits the production task order into one or more sub-production task orders according to the product name in the production task order.
[0069] There is a correspondence between sub-production task orders and product names. For example, one or more sub-production task orders can correspond to one product name.
[0070] For example, assuming the production task order is as shown in Table 1 above, taking product A as an example, the first equipment can split the production task order into sub-production task orders corresponding to product A according to the product name, as shown in Table 3 below.
[0071] Table 3
[0072]
[0073] As shown in Table 3, splitting the production task order into sub-production task orders corresponding to product A can separate the project name "Project 1", requirement number "Requirement Number 1", planned submission time for functional test version "Time Point 1", planned submission time for production version "Time Point 2", and workload "Workload 1" corresponding to product A into separate sub-production task orders.
[0074] It should be noted that the above only introduces the sub-production task orders corresponding to one product in a single production task order. For other products in the same production task order, the same product in different production task orders, and other products in different production task orders, the same method as in Table 3 above can be used to split the production task order into sub-production task orders corresponding to the products.
[0075] S203. For each sub-production task order, the first equipment determines the target development team corresponding to the sub-production task order based on the correspondence between the product and the development team.
[0076] One development team can be associated with one or more products. The target development team can be any one of multiple development teams.
[0077] In some possible embodiments, prior to S203, the method may further include: the first device acquiring the correspondence between the product and the development team.
[0078] One possible implementation is as described above. Figure 3 In the connection relationship shown, the first device 310 can be connected to the second device 320. The first device acquiring the correspondence between products and development teams can include: the first device 310 receiving the correspondence between products and development teams sent by the second device 320. For example, the second device 320 can receive the correspondence between products and development teams input by an administrator and send the correspondence between products and development teams to the first device 310.
[0079] S204. The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the preset push rules.
[0080] As described above, the first device may include an iterative process management system. This system can provide a collaborative space for the development team, offering them a working environment. Each collaborative space corresponds one-to-one with a development team. That is, the collaborative space corresponding to the target development team can be used to provide them with a working environment. Push rules can be used to determine the push time for the first device to push sub-production task orders.
[0081] Optionally, prior to S204, the first device may also obtain push rules. For example, the first device may obtain push rules set by the administrator.
[0082] In one possible implementation, the first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to a preset push rule. This may include: for each sub-production task order, when the first device determines the target development team corresponding to the sub-production task order, the first device pushes the sub-production task order to the collaboration space corresponding to the target development team.
[0083] Figure 4 This is another flowchart illustrating the production task push method provided in an embodiment of this application. Figure 4As shown, taking the production task orders obtained by the first device as an example, including production task order M1 and production task order M2, where production task order M1 includes relevant information about product A and product B, and production task order M2 includes relevant information about product A and product C. Assuming that product A corresponds to development team 1, product B corresponds to development team 2, and product C corresponds to development team 3, the first device can split production task order M1 into sub-production task orders M1-product A and M1-product B, and production task order M2 into sub-production task orders M2-product A and M2-product C. Based on the correspondence between product A and development team 1, the first device can push sub-production task orders M1-product A and M2-product A to the collaboration space corresponding to development team 1. The collaboration space can also include an electronic Kanban board, which can be used to display the sub-production task orders. The first device can push sub-production task order M1 - Product B to the collaboration space corresponding to development team 2 based on product B, and display it on the electronic Kanban board in the collaboration space corresponding to development team 2. The first device can also push sub-production task order M2 - C to the collaboration space corresponding to development team 3 based on product C, and display it on the electronic Kanban board in the collaboration space corresponding to development team 3.
[0084] In the production task push method provided in this application embodiment, the first device can provide a collaboration space for the development team, and the development team and the collaboration space have a corresponding relationship. The first device can obtain a production task order, which may include a product name, with a one-to-one correspondence between the product name and the product, and a one-to-one correspondence between the product and the development team. The first device can split the production task order into one or more sub-production task orders, thereby realizing task segmentation. For each sub-production task order, the first device can determine the target development team corresponding to the sub-production task order based on the correspondence between the product and the development team, and push the sub-production task order to the collaboration space corresponding to the target development team according to a preset push rule. Through this periodic synchronous push mechanism, accurate push and data synchronization updates of sub-production task orders can be achieved. Developers and testers can obtain production tasks based on the sub-production task orders pushed by the first device without manual recording, which improves the efficiency of developers and testers in obtaining production tasks and reduces the probability of errors in the obtained production tasks, thus optimizing the production task scheduling process. In another possible implementation, the production task order may also include a version name, or the production task order may not include a version name. The sub-production task orders obtained by the first device from splitting a production task order may include a version name, or they may not include a version name. The method may further include: for each sub-production task order, the first device determines the type of the sub-production task order based on whether it includes a version name. The first device pushes the sub-production task orders to the collaboration space corresponding to the target development team according to preset push rules, which may include: for each sub-production task order, the first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the type of the sub-production task order and the preset push rules.
[0085] The types of sub-production task orders can include first sub-production task orders and second sub-production task orders, etc. First sub-production task orders can include sub-production task orders for development tasks. Second sub-production task orders can include sub-production task orders for testing tasks.
[0086] For example, when a sub-production task order includes a version name, the first device can determine that the sub-production task order is classified as a first sub-production task order. When a sub-production task order does not include a version name, the first device can determine that the sub-production task order is classified as a second sub-production task order.
[0087] For example, the preset push rules may include: pushing only the first sub-production task order on Mondays; pushing both the first and second sub-production task orders on Tuesdays, Wednesdays, and Thursdays; and pushing only the second sub-production task order on Fridays. The push rules can be preset by administrators in the first device, and this application embodiment does not limit the specific content of the push rules.
[0088] Optionally, as described above, the sub-production task order may include key times, such as the planned submission time for the functional test version and the planned submission time for the production version. The first sub-production task order may include a version name. For each sub-production task order, after the first device determines that the sub-production task order is the first sub-production task order, the first device can also generate a version plan based on the version name and key times in the first sub-production task order. The version plan and the first sub-production task order have a corresponding relationship. For example, the version plan can correspond one-to-one with the first sub-production task order. The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the type of sub-production task order and the preset push rules. This may include: when the sub-production task order is the first sub-production task order, the first device pushes the first sub-production task order and the version plan corresponding to the first sub-production task order to the collaboration space corresponding to the target development team according to the preset push rules.
[0089] The version plan may include the version name, the time of submission of the functional test version, the time of submission of the official version, the production launch time, the start date, the release date, and the release version number.
[0090] Optionally, when the first device splits a production task order into one or more sub-production task orders based on the product name in the production task order, it can also obtain the sub-production task order number for each sub-production task order, with a one-to-one correspondence between the sub-production task order number and the sub-production task order. The version plan may also include the sub-production task order number.
[0091] Optionally, before the first device generates a version plan based on the version name and key times in the first sub-production task order, the first device may also obtain the version name, the time of submission of the functional test version, the time of submission of the official version, the production launch time, the start date, the release date, and the release version number.
[0092] For example, the first device uses the version name in the first sub-production task order as the version name in the version plan. The first device uses the planned submission time for the functional test version in the first sub-production task order as the submission time for the functional test version in the version plan; or, the first device receives manually input submission time for the functional test version determined based on the planned submission time for the functional test version in the first sub-production task order. The first device receives manually input time information such as product launch time, production task start date, and product release date. The first device generates a release version number, etc., based on the version name in the first sub-production task order and a preset version number template.
[0093] For example, a version schedule can be shown in Table 4 below.
[0094] Table 4
[0095] Submission of feature test version time Time 1 Submission of official version time Time 2 Product launch time Time 3 Production task start date Time 4 Product release date Time 5 Release version number Version 1 Sub-production task order number Number 1
[0096] As shown in Table 4, the version plan may include the following items: version name, submission date for functional test version, submission date for official version, product launch date, production task start date, product release date, release version number, and sub-production task number. Specifically, the version name item may include "Version Name 1". The submission date for functional test version may include "Time 1". The submission date for official version may include "Time 2". The product launch date may include "Time 3". The production task start date may include "Time 4". The product release date may include "Time 5". The release version number may include "Version Number 1". The sub-production task number may include "Number 1", etc. There is a corresponding relationship between the version name "Version Name 1", the submission date for functional test version "Time 1", the submission date for official version "Time 2", the product launch date "Time 3", the production task start date "Time 4", the product release date "Time 5", the release version number "Version Number 1", and the sub-production task number "Number 1".
[0097] Figure 5 This is another flowchart illustrating the production task push method provided in this application embodiment. As shown in Figure 5, the above-described method also applies. Figure 4The production task orders obtained by the first device shown include production task order M1 and production task order M2. Production task order M1 includes relevant information for product A and product B, and production task order M2 includes relevant information for product A and product C. For example, product A corresponds to development team 1, product B corresponds to development team 2, and product C corresponds to development team 3. Assuming that sub-production task orders M1-product A, M2-product A, and M1-product B all include version names and key dates, while sub-production task order M2-product C does not include a version name, the first device can also generate version plans M1-A, M2-A, and M1-B corresponding to the sub-production task orders based on the version names and key dates in each of the sub-production task orders. The first device can push sub-production task order M1-Product A, its corresponding version plan M1-A, sub-production task order M2-Product A, and its corresponding version plan M2-A to the collaboration space corresponding to development team 1, and display them on the electronic Kanban board in the collaboration space of development team 1. The first device can also push sub-production task order M1-Product B, its corresponding version plan M1-B to the collaboration space corresponding to development team 2, and display them on the electronic Kanban board in the collaboration space of development team 2. Finally, the first device can push sub-production task order M2-Product C to the collaboration space corresponding to development team 3, and display it on the electronic Kanban board in the collaboration space of development team 3.
[0098] In the production task push method provided in this application embodiment, the first device can also classify sub-production task orders according to whether or not a version name is included. Sub-production task orders that include a version name are classified as first sub-production task orders, and sub-production task orders that do not include a version name are classified as second sub-production task orders. The first device can also automatically generate a version plan based on the version number and key time in the first sub-production task order, saving the development team time in formulating version plans and improving the overall development efficiency of the development team.
[0099] In another possible implementation, as described above, the sub-production task order may include key times. The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to preset push rules, which may include: the first device pushes the sub-production task order to the collaboration space corresponding to the target development team based on the key times and preset push rules.
[0100] Optionally, as mentioned above, the key time may include the planned submission time of the functional test version. The first device pushes the feature to the collaboration space corresponding to the target development team according to the key time and preset push rules, which may include: the first device pushes the feature to the collaboration space corresponding to the target development team according to the planned submission time of the functional test version and preset push rules.
[0101] As mentioned above, the key time can also be referred to as the first time. The planned submission time for the functional test version can also be referred to as the second time. The key time can include the planned submission time for the functional test version, that is, the first time can include the second time.
[0102] For example, push rules may include: push plans to submit feature test versions within a preset first time period, and push sub-production task orders to submit feature test versions after the preset first time period.
[0103] Optionally, as mentioned above, the key time may include the planned release date for the production version. The first device pushes the data to the collaboration space corresponding to the target development team according to the key time and preset push rules, which may include: the first device pushing the data to the collaboration space corresponding to the target development team according to the planned release date and preset push rules.
[0104] As mentioned above, the critical time can also be referred to as the first time. The planned release date for the production version can also be referred to as the third time. The critical time can include the planned release date for the production version, meaning that the first time can include the third time.
[0105] For example, push rules may include: pushing sub-production task orders whose planned submission time for production release is within a preset first time period, and those whose planned submission time for production release is after the preset first time period.
[0106] In the production task push method provided in this application embodiment, after the first device determines the target development team corresponding to the sub-production task order, it can also push the sub-production task order to the collaboration space corresponding to the target development team according to the preset push rules such as the sub-production task order type dimension, the planned submission time of the test function version dimension, and the planned submission time of the production version dimension. The push rules can be flexibly configured, which improves the user experience.
[0107] In some possible embodiments, after pushing the sub-production task order to the collaboration space corresponding to the target development team, the first device can also send a prompt message to the collaboration space corresponding to the target development team according to the critical time. The prompt message is used to remind the developers or testers in the target development team to complete the production task in a timely manner.
[0108] In one possible implementation, the first device sends a prompt message to the collaboration space corresponding to the target development team based on the critical time. This may include: the first device sending a prompt message to the collaboration space corresponding to the target development team at the critical time.
[0109] For example, taking November 5, 2021 as the key date, the first device can send a prompt message to the collaboration space corresponding to the target development team on November 5, 2021, to remind the developers or testers in the target development team to complete the production task in a timely manner.
[0110] In another possible implementation, the first device sends a reminder message to the collaboration space corresponding to the target development team based on the key time. This may include: the first device determining the reminder time based on the key time; and the first device sending the reminder message to the collaboration space corresponding to the target development team at the reminder time.
[0111] For example, taking November 5, 2021 as the key date, the first device can determine November 4, 2021, the day before the key date, as the reminder time, and send a reminder message to the collaboration space corresponding to the target development team on November 4, 2021, to remind the developers or testers in the target development team to complete the production task in a timely manner.
[0112] Optionally, for each sub-production task order, the first device can also record the corresponding record information. After pushing the sub-production task order to the collaboration space corresponding to the target development team, the first device can also receive first information sent by the second device, where the first information corresponds one-to-one with the sub-production task order; in response to the first information, the first device can delete the sub-production task order corresponding to the first information and the record information corresponding to the sub-production task order corresponding to the first information, or save the sub-production task order corresponding to the first information and the record information corresponding to the sub-production task order corresponding to the first information.
[0113] The first information can be used to indicate that the sub-production task order corresponding to the first information has a first state. The first state can include states such as deletion and modification.
[0114] For example, taking production task 1 split into sub-production task 1 and sub-production task 1 B as an example. The second device can receive deletion operations from the administrator on the relevant information of sub-production task 1 A within the production task 1 corresponding to sub-production task 1 A. In response to the administrator's deletion operation on the relevant information of sub-production task 1 A within the production task 1 corresponding to sub-production task 1 A, the second device deletes the relevant information of sub-production task 1 A within the production task 1 corresponding to sub-production task 1 A and sends first information to the first device, indicating that sub-production task 1 A is in a deletion state in the second device. The first device can receive deletion operations on sub-production task 1 A from the iteration manager. In response to the iteration manager's deletion operation on sub-production task 1 A, the first device can delete sub-production task 1 A and the corresponding record information.
[0115] In the production task push method provided in this application embodiment, the first device can also monitor the full-link data corresponding to the sub-production task order, automatically obtain abnormal data and process the abnormal data, so as to realize the failure transfer and fault tolerance processing of the sub-production task order.
[0116] Optionally, the first device may also provide a visual list of sub-production task orders. The visual list of sub-production task orders may include one or more development teams, each development team may correspond to one or more sub-production task orders, and each sub-production task order may have its own corresponding status identifier. The status identifier may include a first identifier and a second identifier. The first identifier is used to indicate that the production task corresponding to the sub-production task order has been completed, and the second identifier is used to indicate that the production task corresponding to the sub-production task order has not been completed.
[0117] For developers, "production task completed" means the software product's version name matches the version name in the sub-production task sheet; "production task incomplete" means the software product's version name differs from the version name in the sub-production task sheet. For testers, "production task completed" means the test results for the software product using test cases have been obtained; "production task incomplete" means no test results for the software product using test cases have been obtained. Test results for the software product using test cases can include pass and fail.
[0118] Optionally, the first identifier corresponding to the sub-production task order can be obtained by the first device.
[0119] In one possible implementation, the first device obtaining the first identifier corresponding to the sub-production task order may include: for each sub-production task order, the first device receiving the first identifier corresponding to the sub-production task order input by the developer or tester.
[0120] Optionally, a sub-production task order with a first identifier may include one or more. For each sub-production task order with a first identifier, the first device may obtain the version name or test result of the sub-production task order in the collaboration space. When the version name in the collaboration space is different from the version name in the sub-production task order, or when the test result in the collaboration space is empty, the first device may convert the first identifier corresponding to the sub-production task order into a second identifier.
[0121] In another possible implementation, the first device obtaining the first identifier corresponding to the sub-production task order may include: for each sub-production task order, the first device periodically obtaining the version name or test result of the sub-production task order in the collaboration space. For example, for each sub-production task order, the first device obtains the version name or test result of the sub-production task order in the collaboration space once every one day in the first period. When the version name in the collaboration space is the same as the version name in the sub-production task order, or when the test result in the collaboration space is not empty, the first device can mark the sub-production task order with the first identifier.
[0122] In the production task push method provided in this application embodiment, the first device can also provide a visual list to display the completion status of the production tasks corresponding to each sub-production task order. Simultaneously, it can also assign a status marker to each sub-production task order based on the completion status of the production tasks corresponding to it, thereby enabling functions such as automatic archiving and automatic cancellation of archiving of sub-production task orders.
[0123] In an exemplary embodiment, this application also provides a production task push device, which can be applied to the first device described above. Figure 6 This is a schematic diagram illustrating the composition of the production task pushing device provided in an embodiment of this application. Figure 6 As shown, the device may include a production task order acquisition module 601, a production task order splitting module 602, and a sub-production task order processing module 603. The production task order acquisition module 601 acquires production task orders, which include product names, with a one-to-one correspondence between product names and products, and a one-to-one correspondence between products and development teams. The production task order splitting module 602 splits the production task order into one or more sub-production task orders based on the product names in the production task order. The sub-production task order processing module 603, for each sub-production task order, determines the target development team corresponding to the sub-production task order based on the correspondence between products and development teams; and pushes the sub-production task order to the collaboration space corresponding to the target development team according to preset push rules. The collaboration space corresponding to the target development team is used to provide a working environment for the target development team.
[0124] In some possible embodiments, Figure 7This is a schematic diagram illustrating another component of the production task pushing device provided in an embodiment of this application. (See diagram below.) Figure 7 As shown, the device may further include a rule configuration module 604. The rule configuration module 604 is used to obtain push rules.
[0125] In other possible embodiments, the sub-production task processing module 603 is further configured to, for each sub-production task, determine its type based on whether it includes a version name. The type may be either a first sub-production task or a second sub-production task, where the first sub-production task includes a version name and the second sub-production task does not. Specifically, the sub-production task processing module 603 is configured to push the sub-production task to the collaboration space corresponding to the target development team based on its type and preset push rules.
[0126] In some other possible embodiments, the first sub-production task order also includes a first time. The sub-production task order processing module 603 is further configured to determine the version plan corresponding to each first sub-production task order based on the first time and the version name. Specifically, when the sub-production task order is the first sub-production task order, the sub-production task order processing module 603 is configured to push the first sub-production task order and the version plan corresponding to the first sub-production task order to the collaboration space corresponding to the target development team according to a preset push rule.
[0127] In some other possible embodiments, the sub-production task order also includes a first time. The sub-production task order processing module 603 is specifically used to push the sub-production task order to the collaboration space corresponding to the target development team according to the first time and preset push rules.
[0128] In some other possible embodiments, the first time includes the second time. The sub-production task processing module 603 is specifically used to push the sub-production task to the collaboration space corresponding to the target development team according to the second time and preset push rules.
[0129] In some other possible embodiments, the first time includes a third time. The sub-production task processing module 603 is specifically used to push the sub-production task to the collaboration space corresponding to the target development team according to the third time and preset push rules.
[0130] In some other possible embodiments, the sub-production task processing module 603 is also used to send a prompt message to the collaboration space corresponding to the target development team as soon as possible. The prompt message is used to remind the members of the target development team to complete the production task in a timely manner.
[0131] In some other possible embodiments, the first device is connected to the second device. The production task order acquisition module 601 is specifically used to receive production task orders sent by the second device.
[0132] In some other possible embodiments, Figure 8 This is another schematic diagram of the production task pushing device provided in the embodiments of this application. For example... Figure 8 As shown, the device also includes a data monitoring and anomaly handling module 605. The data monitoring and anomaly handling module 605 is used to record the record information corresponding to each sub-production task order; receive first information, which is sent by the second device when the sub-production task order has a first state; the first information corresponds one-to-one with the sub-production task order; the first information indicates that the sub-production task order corresponding to the first information has a first state, which includes a deletion state or a modification state; in response to the first information, delete the sub-production task order corresponding to the first information and the record information corresponding to the sub-production task order corresponding to the first information, or save the sub-production task order corresponding to the first information and the record information corresponding to the sub-production task order corresponding to the first information.
[0133] In some other possible embodiments, Figure 9 This is another schematic diagram of the production task pushing device provided in the embodiments of this application. For example... Figure 9 As shown, the device also includes a front-end management module 606. The front-end management module 606 provides a visual list of sub-production task orders. This list can include one or more development teams, each corresponding to one or more sub-production task orders. Each sub-production task order can have its own corresponding status identifier, which can include a first identifier and a second identifier. The first identifier indicates that the production task corresponding to the sub-production task order has been completed, and the second identifier indicates that the production task corresponding to the sub-production task order has not been completed.
[0134] In an exemplary embodiment, this application also provides a computer program product that, when run on a computer, causes the computer to execute the aforementioned related method steps to implement the production task push method in the above embodiments.
[0135] In an exemplary embodiment, this application also provides an electronic device, which may be the first device described in the above method embodiments. Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 10 As shown, the electronic device may include a processor 1001 and a memory 1002; the memory 1002 stores instructions executable by the processor 1001; when the processor 1001 is configured to execute instructions, the electronic device causes the electronic device to implement the method described in the foregoing method embodiments.
[0136] In an exemplary embodiment, this application also provides a computer-readable storage medium storing computer program instructions thereon; when the computer program instructions are executed by an electronic device, the electronic device causes the electronic device to perform the method described in the foregoing embodiments. The computer-readable storage medium may be a non-transitory computer-readable storage medium, such as a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device.
[0137] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A production task push method characterized by, The method includes: The first device acquires a production task order, which includes a product name, with each product name corresponding to a specific product and each product corresponding to a specific development team. The production task order includes: project name, task batch, requirement number, key time, product name, and workload. The key time includes the planned submission time for the functional test version and the planned submission time for the production version. The first device splits the production task order into one or more sub-production task orders based on the product name in the production task order; For each of the sub-production task orders, the first device determines the target development team corresponding to the sub-production task order based on the correspondence between the product and the development team; the first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to a preset push rule, and the collaboration space corresponding to the target development team is used to provide a working environment for the target development team. For each of the sub-production task orders, the first device obtains the type of the sub-production task order based on whether the sub-production task order includes a version name. The type includes a first sub-production task order or a second sub-production task order. The first sub-production task order includes the version name, while the second sub-production task order does not include the version name. The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to a preset push rule, including: The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the type of the sub-production task order and the preset push rules. The first sub-production task order also includes a first time, and the method further includes: The first device determines the version plan corresponding to each first sub-production task based on the first time and the version name; The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the type of the sub-production task order and the preset push rules, including: When the sub-production task is the first sub-production task, the first device pushes the first sub-production task and the version plan corresponding to the first sub-production task to the collaboration space corresponding to the target development team according to the preset push rules. The sub-production task order also includes the first time; The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to a preset push rule, including: The first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the first time and the preset push rules.
2. The method of claim 1, wherein, The method further includes: The first device sends a prompt message to the collaboration space corresponding to the target development team according to the first time, and the prompt message is used to remind the members of the target development team to complete the production task in a timely manner.
3. The method according to any of claims 1-2, characterized in that, The first device is connected to the second device; The first device acquires the production task order, including: The first device receives the production task order sent by the second device.
4. The method of claim 3, wherein, The first device is also used to record the record information corresponding to each of the sub-production task orders; The method further includes: The first device receives first information, which is sent by the second device when the sub-production task order has a first state. The first information corresponds one-to-one with the sub-production task order. The first information is used to indicate that the sub-production task order corresponding to the first information has a first state, which includes a deletion state or a modification state. In response to the first information, the first device deletes the sub-production task order corresponding to the first information and the record information corresponding to the sub-production task order, or saves the sub-production task order corresponding to the first information and the record information corresponding to the sub-production task order.
5. A production task pusher device characterized by comprising: The device includes: a production task order acquisition module, a production task order splitting module, and a sub-production task order processing module. The production task order acquisition module is used to acquire production task orders. The production task order includes a product name, and each product name corresponds to a product and each product corresponds to a development team. The production task order includes: project name, task batch, requirement number, key time, product name, and workload. The key time includes the planned submission time for the functional test version and the planned submission time for the production version. The production task order splitting module is used to split the production task order into one or more sub-production task orders according to the product name in the production task order. The sub-production task processing module is used to determine the target development team corresponding to each sub-production task based on the correspondence between the product and the development team; and to push the sub-production task to the collaboration space corresponding to the target development team according to the preset push rules. The collaboration space corresponding to the target development team is used to provide a working environment for the target development team. The sub-production task processing module is further configured to, for each sub-production task, have the first device determine the type of the sub-production task based on whether the sub-production task includes a version name, wherein the type includes a first sub-production task or a second sub-production task, the first sub-production task including the version name, and the second sub-production task not including the version name; the first device pushes the sub-production task to the collaboration space corresponding to the target development team according to a preset push rule, including: the first device pushes the sub-production task to the collaboration space corresponding to the target development team according to the type of the sub-production task and the preset push rule; the first sub-production task also includes a first time, and the first device determines the first time and the version name. Each first sub-production task order corresponds to a version plan; the first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the type of the sub-production task order and the preset push rules, including: when the sub-production task order is a first sub-production task order, the first device pushes the first sub-production task order and the version plan corresponding to the first sub-production task order to the collaboration space corresponding to the target development team according to the preset push rules; the sub-production task order also includes a first time; the first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the preset push rules, including: the first device pushes the sub-production task order to the collaboration space corresponding to the target development team according to the first time and the preset push rules.
6. An electronic device, comprising: The electronic device includes: a processor and a memory; The memory stores instructions that the processor can execute; When the processor is configured to execute the instructions, the electronic device performs the method as described in any one of claims 1-4.
7. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes: computer software instructions; When the computer software instructions are executed in an electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-4.