Task allocation method and device, electronic equipment, storage medium and program product

Abstract

Embodiments of the present disclosure relate to a task allocation method and device, electronic equipment, storage medium and program product, wherein the task allocation method comprises: obtaining a target task to be solved; determining task description information of the target task, the task description information comprising: a task type and / or a technical type; determining a target task pool in which a technical capability attribute matches the task description information; and allocating the target task to the target task pool. The embodiments of the present disclosure realize automatic task allocation, and improve the rationality and efficiency of task allocation.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a task allocation method, apparatus, electronic device, storage medium, and program product. Background Technology

[0002] In business product development or other work, there is a need for task allocation. Current task allocation methods involve manually assigning tasks to specific personnel. However, manual allocation makes it difficult to fully ascertain whether the personnel have the necessary skills to complete the task. Therefore, on the one hand, it may take time to understand the personnel's capabilities; on the other hand, limited understanding of the personnel's capabilities may result in a mismatch between the assigned personnel's skills and the task. Current task allocation methods suffer from low efficiency and unreasonable allocation. Summary of the Invention

[0003] In order to solve the above-mentioned technical problems, or at least partially solve the above-mentioned technical problems, this disclosure provides a task allocation method, apparatus, electronic device, storage medium and program product.

[0004] In a first aspect, embodiments of this disclosure provide a task allocation method, including:

[0005] Obtain the target task to be solved;

[0006] Determine the task description information of the target task, the task description information including: task type and / or technology type;

[0007] Determine the target task pool that matches the technical capability attributes with the task description information;

[0008] The target task is assigned to the target task pool.

[0009] Secondly, embodiments of this disclosure also provide a task allocation device, including:

[0010] The acquisition module is used to acquire the target task to be solved.

[0011] The matching module is used to determine the task description information of the target task, the task description information including: task type and / or technology type; and to determine a target task pool that matches the capability information with the task description information.

[0012] The allocation module is used to allocate the target task to the target task pool.

[0013] Thirdly, embodiments of this disclosure also provide an electronic device, the electronic device comprising: a processor; a memory for storing executable instructions of the processor; the processor for reading the executable instructions from the memory and executing the executable instructions to implement any of the task allocation methods provided in embodiments of this disclosure.

[0014] Fourthly, embodiments of this disclosure also provide a computer-readable storage medium storing a computer program for executing any of the task allocation methods described in embodiments of this disclosure.

[0015] Fifthly, embodiments of this disclosure also provide a computer program product for executing any of the task allocation methods described in embodiments of this disclosure.

[0016] The task allocation method provided in this disclosure can obtain a target task to be solved and determine the task description information of the target task; and obtain a target task pool from a selectable task pool whose technical capability attributes match the task description information, and allocate the target task to the target task pool. By matching the technical capability attributes of the selectable task pool with the task description information of the current target task to be solved, the method can allocate the target task to a target task pool with matching technical capability attributes and achieve automatic task allocation, thereby improving the rationality and efficiency of task allocation. Attached Figure Description

[0017] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0018] Figure 1 A schematic diagram illustrating a business product development and testing process provided for an embodiment of this disclosure;

[0019] Figure 2 A flowchart illustrating a task allocation method provided in an embodiment of this disclosure;

[0020] Figure 3 A flowchart illustrating another task allocation method provided in an embodiment of this disclosure;

[0021] Figure 4 This is a schematic diagram of the structure of a task allocation device provided in an embodiment of the present disclosure;

[0022] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0023] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0024] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0025] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0026] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0027] The task allocation method, apparatus, electronic device, storage medium, and program product provided in this disclosure can be applied to any business allocation scenario.

[0028] For example, some business products go through two phases, development and testing, before they can be used. Some businesses also need to be redeveloped and tested periodically according to requirements. During these processes, after the business products are tested, some bugs will be found and corresponding bug tasks will be generated. By executing such bug tasks, the bugs in the business products can be resolved.

[0029] Figure 1 This is a schematic diagram illustrating a business product development and testing process provided in an embodiment of this disclosure.

[0030] like Figure 1 As shown, the process of obtaining an applicable business product involves the following stages:

[0031] 101. Gathering Requirements. This stage begins by gathering the requirements for the business product, and then the business product is developed based on these requirements.

[0032] 102. Product Development. This stage involves developing business products based on requirements, as well as resolving bugs discovered during testing and generating bug tasks.

[0033] 103. Product Testing. Test the business products developed during the product development phase. If bugs are found, a bug task can be generated and returned to the product development phase workflow.

[0034] The task allocation method, apparatus, and electronic device provided in this disclosure can be used to automatically allocate bug tasks in such scenarios, thereby improving the rationality and efficiency of task allocation.

[0035] Figure 2 This is a flowchart illustrating a task allocation method provided in an embodiment of the present disclosure, which can be applied to any business allocation scenario. The task allocation method can be executed by a task allocation device, which can be implemented in software and / or hardware and integrated into any electronic device with computing capabilities.

[0036] like Figure 2 As shown, the task allocation method provided in this embodiment may include, but is not limited to, the following steps:

[0037] 201. Obtain the target task to be solved.

[0038] The target task can refer to any task to be assigned. For example, the target task could be a bug task.

[0039] 202. Determine the task description information for the target task.

[0040] The task description information includes: task type and / or technology type. The task type can refer to the task line to which the task belongs.

[0041] For example, taking the target task as a bug task in a product development related to road testing, the task type can include at least one of pre-run, in-run, and post-run; the technology type can include at least one of JS, iOS, and Android.

[0042] The "pre-trip" refers to the tasks before the road test begins, the "trip" refers to the tasks during the road test, and the "post-trip" refers to the tasks after the road test is completed. It should be noted that road testing typically involves a test vehicle driving on the road to be tested and collecting road-related data through sensors on the vehicle, which is then used to update map data.

[0043] JS refers to JavaScript, a lightweight, interpreted or just-in-time (JIT) programming language with a function-first approach. It can be used as a scripting language for developing web pages and supports object-oriented, imperative, declarative, and functional programming paradigms. The technology type JS refers to the tasks associated with the JS programming language. iOS refers to the mobile operating system developed by Apple Inc. The technology type iOS refers to the tasks applied to the iOS mobile operating system. Android refers to a free and open-source operating system based on the Linux kernel, primarily used on mobile devices such as smartphones and tablets. The technology type Android refers to the tasks applied to the Android operating system.

[0044] 203. Obtain a target task pool that matches the technical capability attributes with the task description information.

[0045] The aforementioned technical capability attributes may include, but are not limited to: task type, and / or, technology type, etc.

[0046] In some embodiments, the technical capability attribute may also include: the number of times a certain task type has been completed in the past, and the number of times a certain technology type has been used to complete a task in the past.

[0047] In this embodiment of the disclosure, the technical capability attributes of the currently selectable task pool can be stored in advance, wherein the technical capability attributes of the task pool can include the correspondence between the task pool and the technical capability attributes.

[0048] For example, as shown in Table 1 below, the above-mentioned task pool technical capability attributes can be stored in the form of a task pool technical capability table.

[0049] Table 1

[0050]

[0051] In Table 1, A, B, C, D, and E are five different task pools. The beginning, middle, and end of the line represent different task types, and JS, iOS, and Android represent different technology types.

[0052] Among them, the five different task pools A, B, C, D and E in Table 1 can correspond to different personnel information. That is, at least one personnel information will correspond to a task pool, and the tasks in the task pool will eventually be completed by the personnel indicated by the personnel information corresponding to the task pool.

[0053] JS refers to JavaScript, a lightweight, interpreted or just-in-time (JIT) programming language with functions. It can be used as a scripting language for developing web pages and supports object-oriented, imperative, declarative, and functional programming paradigms. The technology type JS refers to the tasks associated with this programming language. iOS refers to the mobile operating system developed by Apple Inc. The technology type iOS refers to the tasks applied to this mobile operating system. Android refers to a free and open-source operating system based on the Linux kernel, primarily used on mobile devices such as smartphones and tablets. The technology type Android refers to the tasks applied to this operating system.

[0054] It should be noted that Table 1 is an example of storing the technical capability attributes of 5 task pools. In actual practice, there may be more or fewer sets of technical capability attributes for task pools. This embodiment of the disclosure does not limit this.

[0055] In some embodiments, after obtaining the target task to be solved, the target requirement to which the target task belongs can be determined first, and the technical capability attributes of the task pool corresponding to the target requirement can be determined; then, in the technical capability attributes of the task pool, the target task pool that matches the task description information can be obtained, so as to obtain the target task pool.

[0056] Different needs can correspond to different task pool allocations. The technical capability attributes of the task pool corresponding to the target need are the technical capability attributes of the task pool allocated based on the target need.

[0057] In this embodiment of the disclosure, different requirements can be divided into: new requirements and historical requirements. New requirements refer to the requirements corresponding to the latest version of the business product in the current development cycle, while historical requirements are the requirements corresponding to previous versions of the business product in previous development cycles.

[0058] Furthermore, different requirements can exist within new and historical requirements. New requirements can include multiple requirements corresponding to the current development cycle; historical requirements can include multiple requirements corresponding to previous development cycles.

[0059] In this embodiment of the disclosure, one or more tasks are set for each requirement, and a corresponding task pool is allocated for each requirement so that the personnel corresponding to the task pool can complete the task.

[0060] In this embodiment of the disclosure, when allocating a corresponding task pool for each requirement, requirement task pool allocation information can be recorded, which includes the correspondence between requirement information and task pool.

[0061] For example, as shown in Table 2 below, the above-mentioned task pool allocation information can be stored in the form of a task pool allocation table.

[0062] Table 2

[0063] Requirement 1 A Requirement 2 B Requirement 3 C Requirement 4 D Requirement 5 E, F, G …… ……

[0064] In Table 2, requirements 1, 2, 3, 4 and 5 are five different requirements. Different task pools can be configured for these five different requirements. The task pool configured for requirement 1 is A, the task pool configured for requirement 2 is B, the task pool configured for requirement 3 is C, the task pool configured for requirement 4 is D, and the task pool configured for requirement 5 includes E, F and G.

[0065] By combining the task pool allocation table shown in Table 2 with the task pool technical capability table shown in Table 1, we can obtain the task pool allocation for each requirement and the technical capability attributes of the task pool allocated to each requirement.

[0066] In some embodiments, the technical capability attributes corresponding to the task pool can also be stored in the task pool allocation table. Referring to Table 2 above, the technical capability attributes corresponding to the task pool can be added as shown in Table 3.

[0067] Table 3

[0068]

[0069] In some embodiments, the method of obtaining the target task pool whose technical capability attributes match the task description information in the task pool technical capability attributes may include, but is not limited to: obtaining at least one task pool whose technical capability attributes match the task description information in the task pool technical capability attributes; and determining the target task pool with the fewest currently unsolved tasks from the at least one task pool.

[0070] For example, assuming the task description information of the target task indicates that the task type is iOS, and the task type to which the target task belongs is requirement 5 in Table 3 above, then it can be determined from Table 3 that the technical capability attributes of task pools E and F match the task description information; then it is determined that the task pool with task pool E currently has 4 unresolved tasks, and the task pool with task pool F currently has 1 unresolved task, and the task pool with task pool F currently has 1 unresolved task is selected as the target task pool.

[0071] In the above embodiments, when there are multiple task pools with technical capability attributes matching task description information, the target task pool with the fewest currently unsolved tasks can be selected, which can improve the efficiency of solving the target tasks while ensuring the rationality of target task allocation.

[0072] In some embodiments, the method of obtaining the target task pool that matches the task description information in the task pool technical capability attributes may include, but is not limited to: determining at least one task pool with a number of tasks to be solved that is less than a preset number in the task pool technical capability attributes; and obtaining the target task pool that matches the task description information from at least one task pool.

[0073] The aforementioned preset quantity can be set arbitrarily based on actual needs, and the efficiency of different task pools in processing tasks can be considered when setting it.

[0074] For example, assuming the task description information of the target task indicates that the task type is iOS, the preset quantity can be 3, and the task type to which the target task belongs is requirement 5 in Table 3 above, firstly, it is determined that the task pool with task pool E currently has 4 unresolved tasks, the task pool with task pool F currently has 1 unresolved task, and the task pool with task pool G currently has 2 unresolved tasks. According to the preset quantity of 3, it can be determined that the number of unresolved tasks in task pools F and G currently meets the requirements. Furthermore, Table 3 can determine that the technical capability attributes of task pool F match the task description information, and task pool F is determined as the target task pool.

[0075] In the above embodiments, selecting a target task pool whose technical capability attributes match the task description information of the target task from at least one task pool with fewer currently unsolved tasks can improve the rationality of target task allocation while ensuring the efficiency of target task resolution.

[0076] In some embodiments, after determining the technical capability attributes of the task pool corresponding to the target requirement, if the technical capability attributes of each task pool do not match the task description information, the redistribution task pool set according to the target requirement is determined as the target task pool.

[0077] In this embodiment of the disclosure, when allocating a task pool for each requirement, at least one redistribution task pool can be specified for each requirement. The redistribution task pool can be the task pool corresponding to the person in charge of the requirement. The person in charge can be called the person in charge (or owner) of the human resources team corresponding to the requirement. The person in charge can have coordination ability and can coordinate to redistribute the task to other people when they are unable to perform the task themselves. That is to say, the tasks in the redistribution task pool can be handled by the person in charge themselves, or they can be redistributed by the person in charge to other task pools for the people corresponding to the other task pools to handle.

[0078] 204. Assign the target tasks to the target task pool.

[0079] Among them, assigning the target task to the target task pool can be a process node that submits the target task to the corresponding personnel in the target task pool for processing.

[0080] The task allocation method provided in this disclosure matches the technical capability attributes of the task pool with the task description information of the target task to be solved. This allows the target task to be allocated a target task pool with matching technical capability attributes, and the corresponding personnel with business capabilities matching the target task can handle the tasks in the target task pool. This achieves automatic task allocation and can improve the rationality and efficiency of task allocation.

[0081] In some embodiments, after allocating target tasks based on the target task pool, if the number of unresolved tasks associated with the target task pool is greater than or equal to a preset number, a prompt message is output to indicate that there are too many unresolved tasks associated with the target task pool.

[0082] The number of tasks to be resolved refers to the current number of tasks to be resolved. The preset number can be set arbitrarily based on actual needs, and the efficiency of task processing in different task pools can be considered when setting it.

[0083] In the above embodiments, after the target task is assigned to the target task pool, before the target task is resolved, the number of unresolved tasks associated with the target task pool can be monitored. If the number exceeds the preset number, it indicates that there are too many unresolved tasks in the target task pool. At this time, a prompt message is output so that the administrator can be aware of it and reassign the tasks manually if necessary.

[0084] In some embodiments, after a target task is assigned based on the target task pool and after the target task is completed, the technical capability attributes corresponding to the target task pool can be updated based on the task description information of the target task.

[0085] For example, suppose the target task's task type is "Pre-line" and the technology type is "iOS". Before the update, the target task pool's corresponding technology capability attribute is: the solvable task type is "In-line" and the solvable technology type is "iOS". After updating the target task pool's corresponding technology capability attribute based on the target task's task description information, the target task pool's corresponding technology capability attribute after the update is: the solvable task types are "Pre-line" and "In-line", and the technology type is "iOS".

[0086] The above updates to the technical capability attributes are merely illustrative. Furthermore, other parameters in the technical capability attributes can also be updated, such as the number of times the "pre-execution" task type has been performed historically, and the number of times the "iOS" technical task has been performed.

[0087] In the above embodiments, after the target task is completed, the technical capability attributes corresponding to the target task pool can be updated based on the task description information of the target task. In this way, while using the stored technical capability attributes, the technical capability attributes of the task pool can be continuously updated. The status of the technical capability attributes of the task pool can be monitored and recorded in a timely manner, so that the accurate technical capability attributes of each task pool can be obtained when allocating tasks in the future.

[0088] Figure 3 This is a flowchart illustrating another task allocation method provided in an embodiment of the present disclosure.

[0089] like Figure 3 As shown, this task allocation method may include, but is not limited to, the following steps:

[0090] 301. A bug task has been obtained.

[0091] This bug task can be a bug task generated for any bug.

[0092] 302. Determine if it is a bug task corresponding to a new requirement.

[0093] After receiving a bug task, first determine whether it is a new requirement or a historical requirement. If the bug task is a historical requirement, execute steps 303 to 305 below; if the bug task is a new requirement, execute steps 306 to 305 below; then execute steps 306 to 312 below.

[0094] 303. Obtain the task pool and technical capability attributes corresponding to historical requirements based on the task pool technical capability table.

[0095] In some embodiments, a separate task pool technology capability table can be set up for historical needs.

[0096] In some embodiments, a task pool technical capability table can be set for all allocable task pools, and the task pool and technical capability attributes corresponding to historical requirements can be obtained from the task pool technical capability table set for all allocable task pools.

[0097] 304. Determine the target task pool that matches the technical capability attributes of the bug task.

[0098] 305. Assign the bug task to the target task pool.

[0099] 306. Obtain the task pool allocation table corresponding to the current period's requirements.

[0100] The current requirement can refer to the requirements within the current development cycle.

[0101] In some embodiments, a task pool allocation table can be set up for the current period's requirements. Furthermore, the task pool technical capability attributes of the task pool assigned to the new requirement can be obtained from the task pool allocation table corresponding to the current period's requirements.

[0102] 307. Determine the task pool technical capability attributes of the task pool to which the new requirement is assigned based on the task pool allocation table.

[0103] 308. Determine whether the bug task belongs to a two-end problem or a one-end problem.

[0104] Among them, dual-end issues refer to problems that occur when tested on different operating systems. For example, bugs that appear when tested on both iOS and Android operating systems. The bug tasks generated for these bugs are of the JS type, because bugs that usually appear when tested on both iOS and Android operating systems are not problems specific to iOS or Android, but rather problems corresponding to the JS technology type.

[0105] A single-endpoint problem refers to a problem that occurs when testing in a single operating system. For example, a bug that occurs when testing in an Android operating system. The bug task generated for this type of bug is of the Android type, because a bug that occurs when testing in a single Android operating system is usually a problem corresponding to the Android technology type.

[0106] 309. Determine the relevant task pool technical capability attributes from the task pool technical capability attributes.

[0107] Among them, the technical capability attributes of the task pool corresponding to the dual-end problem can refer to the technical capability attributes of the task pool that can handle the JS type of technology.

[0108] 310. From the technical capability attributes of the partial task pool corresponding to the dual-end problem, determine the target task pool with the fewest unsolved tasks.

[0109] By analyzing the technical capabilities of task pools that can handle technologies like JavaScript, we can identify the target task pool with the fewest unresolved tasks. This ensures the efficient execution of the bug-related task and avoids excessive waiting time.

[0110] In some embodiments, after determining the task pool technical capability attributes of the task pool corresponding to the JS type of technology, the task type corresponding to the bug task can also be determined, and the target task pool matching the task type can be determined from the partial task pool technical capability attributes corresponding to the dual-end problem.

[0111] After executing 310 above, you can execute 305 above.

[0112] 311. From the technical capability attributes of the task pool, determine the partial technical capability attributes of the task pool corresponding to the single-end problem.

[0113] Among them, the technical capability attributes of the task pool corresponding to the single-end problem can refer to the technical capability attributes of the task pool that can be competent for Android or iOS, and the technical capability attributes of the task pool.

[0114] 312. From the technical capability attributes of the partial task pool corresponding to the single-end problem, determine the target task pool where the technical capability attributes match the description information of the bug task and / or the number of tasks to be solved is less than a preset number.

[0115] Determining the target task pool based on whether the technical capability attributes match the description information of the bug task can improve the matching degree of task allocation and improve the rationality of task allocation; determining the target task pool based on the number of unresolved tasks being less than a preset number can improve the execution efficiency of tasks after allocation.

[0116] After executing 312 above, you can execute 305 above.

[0117] 313. Determine whether the number of tasks to be solved is greater than or equal to the preset number.

[0118] After a bug task is assigned to the task pool indicated by the target task pool, before the bug task is completed, the number of unresolved tasks in the target task pool can be detected. If the number of unresolved tasks is greater than or equal to the preset number, a prompt message will be output to indicate that there are too many unresolved tasks. At this time, manual assignment can be performed.

[0119] 314. Manually assign the bug-related task.

[0120] 315. Confirm that the task has been completed.

[0121] 316. Improve the task pool technical capability table.

[0122] In the above embodiments, after the bug task is completed, the technical capability attributes corresponding to the target task pool can be updated based on the task description information of the bug task. In this way, the stored technical capability attributes can be continuously updated during the use of the technical capability attributes, and the changes in the technical capability attributes of the task pool can be monitored and recorded in a timely manner, so that accurate technical capability attributes can be obtained when allocating tasks in the future.

[0123] Figure 4This is a schematic diagram of a task allocation device provided in an embodiment of the present disclosure. The device can be implemented in software and / or hardware and can be integrated into any electronic device with computing capabilities.

[0124] like Figure 4 As shown, the task allocation device 400 provided in this embodiment may include:

[0125] Module 401 is used to acquire the target task to be solved;

[0126] Matching module 402 is used to determine the task description information of the target task; and to obtain a target task pool that matches the technical capability attributes with the task description information.

[0127] The allocation module 403 is used to allocate the target task to the target task pool.

[0128] In some embodiments, the matching module 402 is further configured to: before determining a target task pool that matches the technical capability attributes with the task description information,

[0129] Determine the target requirements to which the target task belongs;

[0130] Determine the technical capability attributes of the task pool corresponding to the target requirement;

[0131] The target task pool that matches the acquisition technology capability attributes with the task description information includes:

[0132] In the task pool technical capability attributes, determine the target task pool that matches the technical capability attributes with the task description information;

[0133] The task pool technical capability attribute includes multiple task pools and the correspondence between each task pool and the technical capability attribute.

[0134] In some embodiments, the matching module 402 is further configured to: after determining the task pool technical capability attribute corresponding to the target requirement,

[0135] When the technical capability attributes corresponding to each task pool in the task pool technical capability attributes do not match the task description information, the redistribution task pool set according to the target requirement is determined as the target task pool.

[0136] In some embodiments, the matching module 402 is specifically used for:

[0137] In the task pool technical capability attributes, at least one task pool is identified that matches the task description information.

[0138] Determine the target task pool with the fewest currently unresolved tasks from the at least one task pool. In some embodiments, the matching module 402 is specifically used for:

[0139] In the technical capability attributes of the task pool, at least one task pool with a number of unresolved tasks less than a preset number is identified.

[0140] From the at least one task pool, a target task pool matching the task description information is obtained. In some embodiments, the task allocation device 400 further includes:

[0141] The prompting module 404 is used to output a prompting message when the number of unresolved tasks in the target task pool is greater than or equal to a preset number after the target task is assigned to the target task pool. The prompting message is used to indicate that there are too many unresolved tasks in the target task pool.

[0142] In some embodiments, the task allocation device 400 further includes:

[0143] The update module 405 is configured to update the technical capability attributes corresponding to the target task pool based on the task description information of the target task after the allocation module 403 allocates the target task to the target task pool and after the target task is completed. In some embodiments, the task description information includes: task type and / or technical type.

[0144] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure. It is used to illustrate the electronic device implementing the task allocation method in the embodiments of the present disclosure and should not be construed as a specific limitation on the embodiments of the present disclosure.

[0145] like Figure 5 As shown, the electronic device 500 may include a processor (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the electronic device 500. The processor 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0146] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although an electronic device 500 with various devices is shown, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0147] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 509, or installed from a storage device 508, or installed from a ROM 502. When the computer program is executed by the processor 501, it can perform the functions defined in the task allocation method provided in embodiments of this disclosure.

[0148] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0149] In some implementations, the client and server can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol), and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0150] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0151] The aforementioned computer-readable medium carries one or more programs. When these programs are executed by the electronic device, the electronic device causes the following: to acquire a target task to be solved; to determine task description information of the target task, including task type and / or technology type; to determine a target task pool that matches the technical capability attributes with the task description information; and to allocate the target task to the target task pool. This enables automatic task allocation, improving the rationality and efficiency of task allocation.

[0152] In embodiments of this disclosure, computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof. These programming languages ​​include, but are not limited to, object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on a computer, partially on a computer, as a standalone software package, partially on a computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0153] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0154] The units described in the embodiments of this disclosure can be implemented in software or hardware. The names of the units are not, in some cases, intended to limit the specific unit.

[0155] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0156] In the context of this disclosure, a computer-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0157] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0158] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0159] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A task allocation method, comprising: Obtain the target task to be solved, wherein the target task is a bug task generated when a bug is found during testing of a business product; Determine the task description information of the target task, the task description information including: task type and / or technology type; Determine the target requirement to which the target task belongs, and determine the task pool technical capability attribute corresponding to the target requirement from the pre-stored task pool technical capability attributes; wherein, the target requirement is the requirement on which the development of the business product is based, and the task pool technical capability attribute corresponding to the target requirement is the technical capability attribute of the task pool allocated based on the target requirement. In the task pool technical capability attributes, a target task pool that matches the task description information is determined; the task pool technical capability attributes include multiple task pools, and the correspondence between each task pool and the technical capability attributes; The target task is assigned to the target task pool.

2. The task allocation method according to claim 1, wherein, After determining the task pool technical capability attributes corresponding to the target requirement, the method further includes: When the technical capability attributes corresponding to each task pool in the task pool technical capability attributes do not match the task description information, the redistribution task pool set according to the target requirement is determined as the target task pool.

3. The task allocation method according to claim 1, wherein, The step of obtaining the target task pool whose technical capability attributes match the task description information from the technical capability attributes of the task pool includes: In the task pool technical capability attributes, at least one task pool is identified that matches the task description information. The target task pool with the fewest currently unresolved tasks is determined from the at least one task pool.

4. The task allocation method according to claim 1, wherein, The step of obtaining the target task pool that matches the task description information from the task pool's technical capability attributes includes: In the technical capability attributes of the task pool, at least one task pool with a number of unresolved tasks less than a preset number is identified. From the at least one task pool, obtain the target task pool that matches the task description information.

5. The method according to claim 1, wherein, After assigning the target task to the target task pool, the method further includes: When the number of unresolved tasks in the target task pool is greater than or equal to a preset number, a prompt message is output, which is used to indicate that there are too many unresolved tasks in the target task pool.

6. The method according to claim 1, wherein, After assigning the target task to the target task pool, the method further includes: After the target task is completed, the technical capability attributes corresponding to the target task pool are updated based on the task description information of the target task.

7. A task allocation device, comprising: The acquisition module is used to acquire the target task to be solved, wherein the target task is a bug task generated when a bug is found during testing of a business product; A matching module is used to determine the task description information of the target task, the task description information including: task type and / or technology type; determine the target requirement to which the target task belongs, and determine the task pool technology capability attribute corresponding to the target requirement from the pre-stored task pool technology capability attributes; wherein, the target requirement is the requirement on which the development of the business product is based, and the task pool technology capability attribute corresponding to the target requirement is the technology capability attribute of the task pool allocated based on the target requirement; in the task pool technology capability attributes, determine the target task pool whose technology capability attribute matches the task description information; the task pool technology capability attribute includes multiple task pools, and the correspondence between each task pool and the technology capability attribute; The allocation module is used to allocate the target task to the target task pool.

8. An electronic device, the electronic device comprising: processor; Memory for storing processor-executable instructions; The processor is configured to read the executable instructions from the memory and execute the executable instructions to implement the task allocation method as described in any one of claims 1 to 6.

9. A computer-readable storage medium storing a computer program, which, when executed by a processor, performs the task allocation method as described in any one of claims 1 to 6.

10. A computer program product, when executed by a processor, for performing the task allocation method according to any one of claims 1 to 6.

Images