Task creation method and device, electronic equipment and storage medium
By introducing a task creation method in the task management system, users are allowed to create tasks and generate subtasks in the association diagram, which solves the problem of task isolation in the existing technology, realizes the association relationship between tasks, and improves collaboration efficiency and innovation capabilities.
Patent Information
- Application Number
- CN202510078570.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-17
- Publication Date
- 2025-05-30
AI Technical Summary
In the prior art, tasks between departments and departments, projects and projects, and modules are in isolation, resulting in high cost of collaboration and communication, division of innovation, and failure to maximize the use of enterprise resources.
By providing a task creation method, users can create tasks in the association diagram, generate task creation requirements content interface, obtain target content and generate subtasks of target tasks, and display the task number of subtasks. This method supports torque creation method, allowing tasks to be created across sequences and enhancing the relationship between tasks.
The correlation between tasks is realized, and users can intuitively see the source of the tasks, tasks at the same level and tasks generated, thereby improving collaborative communication efficiency, reducing innovation costs, and maximizing the utilization of enterprise resources.
Smart Images

Figure CN120066332A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to the field of computer technology, and in particular, to a task creation method, apparatus, electronic device, and storage medium. Background Art
[0002] In general, the task management method of an enterprise creates data tables with department - project - module - framework / component as the segmentation boundaries in the three life stages of task creation, construction, and reflection. The advantage of this is that a certain type of tasks in the system are stacked in one information area, which is convenient for users to batch search and permission management, and also conforms to the characteristics of the hierarchical organizational structure of general enterprises. Tasks between departments are isolated, tasks between projects are isolated, tasks between modules are isolated, and each hierarchy has a person in charge. However, this method has many limitations. For example, whether it is people or business, departments, projects, and modules will be isolated from each other. People in different departments will become more and more estranged, their ways of thinking will gradually separate, and their interests and positions will also separate, resulting in higher collaboration and communication costs, heavy coordination meetings between various departments, and fragmented innovation capabilities. Another example is that the collaboration relationship has become a dependent relationship, and the growth of employees' comprehensive knowledge and working ability will be naturally hindered. Large - team collaboration has become a passive obligation rather than an active participation. Although the professional ability is strong, the collaboration ability is weak. The overall consequences directly caused by the above limitations are the unbalanced development of each department in the enterprise. One department is doing tasks while another department has no idea what tasks they are doing for a long time. Without knowing, they can only participate passively. The activities of one department cannot directly empower other departments, and other departments cannot fully apply their professional knowledge and labor time to the business. The resources of the enterprise are not maximally utilized in production.
[0003] Therefore, how to break the limitation that tasks between departments, projects, and modules are in an isolated state and create tasks with an associated relationship has become a technical problem to be solved urgently. Summary of the Invention
[0004] The embodiments of the present invention provide a task creation method, apparatus, electronic device, and storage medium, which are used to solve the technical problem of how to break the limitation that tasks between departments, projects, and modules are in an isolated state and create tasks with an associated relationship.
[0005] In a first aspect, the embodiments of the present invention provide a task creation method, including:
[0006] Obtaining a task creation instruction generated by a first user clicking a task creation button, where the task creation instruction is used to indicate creating a subtask of a target task;
[0007] In response to the task creation instruction, generate a task creation requirement content interface;
[0008] Obtain the target content filled in by the first user on the task creation requirement content interface, where the target content is the attribute information of the subtask to be generated;
[0009] In response to the target content, generate subtasks of the target task;
[0010] Display the task number of the subtask.
[0011] In a possible implementation, before obtaining the task creation instruction generated by the first user clicking the task creation button, the method further includes:
[0012] Obtain the click target task instruction generated by the second user clicking the target task in the association relationship diagram;
[0013] In response to the click target task instruction, generate a creation interface, where the creation interface displays a task creation button and a torque creation button;
[0014] Obtain the creation torque instruction generated by the second user clicking the torque creation button;
[0015] In response to the creation torque instruction, generate a first requirement content interface;
[0016] Obtain the first requirement content filled in by the second user on the first requirement content interface, where the first requirement content is the core content of the requirement, the problems encountered, and the content of the return information area described according to the R & D process;
[0017] In response to the first requirement content, generate a second requirement content interface, where the second requirement content interface displays a torque destination option and a recipient button;
[0018] Obtain the torque destination instruction generated after the second user selects the torque destination and the recipient instruction generated after clicking the recipient button, and generate a torque bar, where the torque bar is displayed in the "Torque Given to Me" interface and the association relationship diagram;
[0019] Obtain the click torque bar instruction generated by the first user clicking the torque bar in the "Torque Given to Me" interface or the association relationship diagram;
[0020] In response to the click torque bar instruction, generate a task creation button.
[0021] In a possible implementation, the generating a task creation requirement content interface in response to the task creation instruction includes:
[0022] In response to the task creation instruction, generate a task creation option interface, where the task creation option interface displays a create new task option and an expand existing task option;
[0023] If a new task creation instruction generated by the first user selecting the option to create a new task is obtained, a task creation requirement content interface is generated;
[0024] If an instruction to expand an existing task generated by the first user selecting the option to expand an existing task is obtained, an interface for expanding the existing task is generated. The interface for expanding the existing task displays options for the name or task number of the task to be expanded and a location positioning option. The option for the name or task number of the task to be expanded is retrieved from the existing task library by the first user after entering a prompt word in the search box;
[0025] Obtain the name or task number of the task to be expanded selected by the first user and the selected location positioning;
[0026] In response to the name or task number of the task to be expanded selected by the first user and the selected location positioning, a task creation requirement content interface is generated.
[0027] In a possible implementation, the target content includes: the module to which the subtask belongs, the framework under the module, the technical column to which the subtask belongs, the subtask name, and management parameters. The management parameters include: investment direction, user scenario, pressure level, and the optimal external intelligence group.
[0028] In a possible implementation, the location positioning options include: product idea + calculation option, content plan option, and technical level option.
[0029] In a possible implementation, after generating the task creation requirement content interface in response to the task creation instruction, the method further includes:
[0030] Obtain a host configuration instruction.
[0031] In a possible implementation, generating the subtasks of the target task in response to the target content includes:
[0032] In response to the target content and the host configuration instruction, a host configuration interface is generated;
[0033] Obtain the host content filled in by the first user on the host configuration interface;
[0034] In response to the host content, a to-be-acknowledged subtask of the target task is generated;
[0035] Obtain a tactical acknowledgment instruction for the to-be-acknowledged subtask;
[0036] In response to the tactical acknowledgment instruction, a parameter configuration interface is generated;
[0037] Obtain the parameters written by the theater supervisor of the first user or the theater to which the subtask to be recognized belongs in the parameter configuration interface;
[0038] Obtain a policy recognition instruction for reviewing the written parameters and the content recognized by the tactical recognition instruction;
[0039] In response to the policy recognition instruction, generate a subtask of the target task, where the subtask is a series of tasks of the task to be extended, and the version number of the subtask is increased based on the task to be extended.
[0040] In a second aspect, an embodiment of the present invention provides a task creation device, including:
[0041] A first acquisition unit, configured to acquire a task creation instruction generated by a first user clicking a task creation button, where the task creation instruction is used to indicate the creation of a subtask of a target task;
[0042] A first generation unit, configured to generate a task creation requirement content interface in response to the task creation instruction;
[0043] A second acquisition unit, configured to acquire target content filled in by the first user in the task creation requirement content interface, where the target content is attribute information of the subtask to be generated;
[0044] A second generation unit, configured to generate a subtask of the target task in response to the target content;
[0045] A display unit, configured to display the task number of the subtask.
[0046] In a third aspect, an embodiment of the present invention provides an electronic device, including:
[0047] A memory and a processor, where the processor and the memory communicate with each other through a bus; the memory stores program instructions executable by the processor, and the processor can execute the method described in the first aspect and each step in various possible implementations by calling the program instructions.
[0048] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the method described in the first aspect and each step in various possible implementations.
[0049] In a fifth aspect, an embodiment of the present invention provides a computer program product containing instructions, and when the computer program product runs on a computer, it causes the computer to execute the method described in the first aspect and each step in various possible implementations.
[0050] The embodiments of the present invention disclose the following technical effects:
[0051] In the embodiments of the present invention, it can be visually seen which task in the association relationship diagram generates a certain task, what its sibling tasks are, and what tasks it generates.
[0052] Of course, when implementing any product of the present invention, it is not necessarily required to achieve all the above-mentioned advantages simultaneously. BRIEF DESCRIPTION OF THE DRAWINGS
[0053] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.
[0054] Figure 1 It is a system architecture diagram applicable to the embodiments of the present invention;
[0055] Figure 2 It is a schematic flowchart of a task creation method provided by the embodiments of the present invention;
[0056] Figure 3 It is a schematic diagram of the association relationship diagram presented by Sequence A provided by the embodiments of the present invention;
[0057] Figure 4 It is a schematic diagram of the first requirement content interface provided by the embodiments of the present invention;
[0058] Figure 5 It is a schematic diagram of the association relationship diagram presented by Sequence B provided by the embodiments of the present invention;
[0059] Figure 6a It is a schematic diagram of a torsion bar appearing above the task with the task number 1003 provided by the embodiments of the present invention;
[0060] Figure 6b It is a schematic diagram of the "Twist to me" interface provided by the embodiments of the present invention;
[0061] Figure 7 It is a schematic diagram of a newly generated subtask 1007 appearing directly above the task with the task number 1003 provided by the embodiments of the present invention;
[0062] Figure 8 It is a schematic block diagram of a task creation device provided by the embodiments of the present invention;
[0063] Figure 9 It is a schematic block diagram of an electronic device provided by the embodiments of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0064] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without making creative efforts shall fall within the protection scope of the present invention.
[0065] The terms used in the embodiments of the present invention are for the purpose of describing specific embodiments only and are not intended to limit the present invention. The singular forms "a", "said" and "the" used in the embodiments of the present invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.
[0066] It should be understood that the term "and / or" used herein is merely a description of the associated relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " herein generally represents an "or" relationship between the associated objects before and after.
[0067] Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to determining" or "in response to detecting". Similarly, depending on the context, the phrase "if determined" or "if monitoring (stated condition or event)" may be interpreted as "when determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)".
[0068] In the traditional enterprise task management method, departments, projects, and modules are isolated from each other, whether it is people or business. People in different departments are becoming more and more estranged, their ways of thinking are gradually separated, and their interests and positions will also be separated, resulting in higher collaboration and communication costs, heavy coordination meetings between various departments, and fragmented innovation capabilities. The collaborative relationship has become a dependent relationship, and the growth of employees' comprehensive knowledge and working ability will be naturally hindered. The collaboration of large teams has become a passive obligation rather than an active participation. Although the professional ability is strong, the collaboration ability is weak. The overall consequence directly caused by the above limitations is the unbalanced development of each department in the enterprise. One department is doing tasks while another department has no idea what tasks they are doing for a long time. Without knowing, they can only participate passively. The activities of one department cannot directly empower other departments, and other departments cannot apply their professional knowledge and saturated working hours to the business. The resources of the enterprise are not maximally utilized in production.
[0069] In view of this, an embodiment of the present invention provides a new idea. To facilitate the understanding of this application, first, the system architecture on which the embodiments of the present invention are based will be described. Figure 1 An exemplary system architecture to which the embodiments of the present invention can be applied is shown, such as Figure 1 As shown, the system architecture may include a terminal device and a task creation device located on the server side.
[0070] Among them, the terminal device may include, but is not limited to, such as: intelligent mobile terminals, smart home devices, wearable devices, PCs (Personal Computers), etc. Among them, intelligent mobile terminals may include, such as mobile phones, tablets, laptops, PDAs (Personal Digital Assistants), Internet cars, etc. Smart home devices may include smart TVs, smart refrigerators, and so on. Wearable devices may include, such as smart watches, smart glasses, virtual reality devices, augmented reality devices, mixed reality devices (i.e., devices that can support virtual reality and augmented reality), and so on.
[0071] The task creation device may use the task creation method provided in the embodiments of the present invention to create tasks.
[0072] The above-mentioned task creation device may be set up in a single server, or in a server group composed of multiple servers, or in a cloud server. A cloud server, also known as a cloud computing server or a cloud host, is a host product in the cloud computing service system to solve the problems of large management difficulty and weak service scalability existing in traditional physical hosts and virtual private servers (VPS, Virtual Private Server) services. In addition to Figure 1 the architecture shown, the task creation device may also be set up in a computer terminal with strong computing power.
[0073] Figure 2 A schematic flowchart of a task creation method provided by an embodiment of the present invention. This method may be executed by Figure 1 the task creation device in the system shown. As Figure 2 shown, this method may include the following steps:
[0074] Step 201: Obtain a task creation instruction generated by a first user clicking a task creation button. The task creation instruction is used to indicate the creation of subtasks of a target task.
[0075] Step 202: In response to the task creation instruction, generate a task creation requirement content interface.
[0076] Step 203: Obtain the target content filled in by the first user on the task creation requirement content interface, where the target content is the attribute information of the subtask to be generated.
[0077] Step 204: In response to the target content, generate a subtask of the target task.
[0078] Step 205: Display the task number of the subtask.
[0079] Next, each step in the above process and the further effects that can be generated will be described in detail in combination with the embodiments of the present invention. It should be noted that the "first", "second", etc. limitations involved in the embodiments of the present invention do not have limitations in terms of size, order, quantity, etc., and are only used to distinguish by name. For example, the "first requirement content interface" and the "second requirement content interface" are used to distinguish two different requirement content interfaces.
[0080] First, in combination with the embodiments of the present invention, the above step 201, that is, "obtain the create task instruction generated by the first user clicking the create task button, and the create task instruction is used to indicate the creation of a subtask of the target task" will be described in detail.
[0081] In the embodiments of the present invention, it should be noted that there are two ways to create a subtask of the target task. One is the manual direct creation method, and the other is the torque creation method.
[0082] If the manual direct creation method is adopted in the embodiments of the present invention, before executing step 201, the first user generates a click target task instruction after clicking the target task in the association relationship diagram. Exemplarily, the association relationship diagram presented by sequence A is as Figure 3 shown. The task with task number 1000 is associated with tasks with task numbers 1001, 1003, and 1004 respectively. The task with task number 1001 is associated with tasks with task numbers 1002, 1005, and 1006 respectively. The first user generates a click target task instruction after clicking the task with task number 1003 in the association relationship diagram. The task creation device can obtain the click target task instruction. The task creation device generates a creation interface in response to the click target task instruction. The creation interface displays a create task button and a create torque button. The first user clicks the create task button, generating a create task instruction. The create task instruction is used to indicate the creation of a subtask of the target task. The task creation device can obtain the create task instruction. The create task instruction is used to indicate the creation of a subtask of the target task.
[0083] It should be noted that the manual direct creation method can only create tasks within this sequence.
[0084] If the torque creation method is adopted in the embodiments of the present invention, before performing step 201, after the second user clicks on the target task in the association relationship diagram, a click target task instruction is generated. The task creation device can obtain the click target task instruction. In response to the click target task instruction, the task creation device generates a creation interface. The creation interface displays a create task button and a create torque button. After the second user clicks the create torque button, a create torque instruction is generated. The task creation device can obtain the create torque instruction. In response to the create torque instruction, the task creation device generates a first requirement content interface, such as Figure 4 shown. The second user fills in the first requirement content in the first requirement content interface. The first requirement content is the core content of the requirement described according to the R & D process, the problems encountered, and the content in the return information area. The task creation device can obtain the first requirement content filled in by the second user in the first requirement content interface. In response to the first requirement content, the task creation device generates a second requirement content interface. The second requirement content interface displays a torque destination option and a recipient button. The torque destination option is used to select which sequence the torque goes to. Here, the torque can go to other sequences (that is to say, when using the torque creation method, cross-sequence task creation can be selected). In the embodiments of the present invention, it is selected that the torque goes to sequence B. The association relationship diagram presented by sequence B is as Figure 5 shown. After the second user selects the torque destination and generates a torque destination instruction and clicks the recipient button, a recipient instruction is generated. The task creation device can obtain the torque destination instruction and the recipient instruction, and generate a torque bar. The torque bar will appear in the association relationship diagram, as Figure 6a shown. It should be noted that the torque bar can also appear in the "Sent to Me" interface at the same time, as Figure 6b shown.
[0085] Exemplarily, since there is no subtask above the task with task number 1003, the torque bar will appear above this task, as Figure 6a shown. If there is a subtask above the task with task number 1003, since the task with task number 1003 is located on the left side of the main trunk association chain (formed by tasks with task numbers 1000, 1001, and 1002 respectively), the torque bar will appear on the left side of the subtask above the task with task number 1003, which is not shown in Figure 6a . Correspondingly, if before performing step 201, the first user selects and clicks on the task with task number 1006 in the association relationship diagram and generates a torque bar, and at this time there is a subtask above the task with task number 1006, since the task with task number 1006 is located on the right side of the main trunk association chain, the torque bar will appear on the right side of the subtask above the task with task number 1006, in Figure 6aIt is no longer shown herein. If there is no subtask above the task with the task number 1006, the torsion bar will appear above this task. After the first user clicks the torsion bar, a click torsion bar instruction is generated. The task creation device can obtain the click torsion bar instruction. In response to the click torsion bar instruction, the task creation device generates a create task button. The first user clicks the create task button, generating a create task instruction. The task creation device can obtain the create task instruction. The create task instruction is used to indicate creating a subtask of the target task.
[0086] It should be noted that in the "Twist for Me" interface, the first user selects to click the torsion bar to generate a click torsion bar instruction. The task creation device can obtain the click torsion bar instruction. In response to the click torsion bar instruction, the task creation device generates a create task button. The first user clicks the create task button, generating a create task instruction. The task creation device can obtain the create task instruction. Then steps 202 to 205 are executed. It can be understood that in the "Twist for Me" interface, the first user can click the torsion bar again to generate a click torsion bar instruction. The task creation device can obtain the click torsion bar instruction. In response to the click torsion bar instruction, the task creation device generates a create task button. The first user clicks the create task button, generating a create task instruction. The task creation device can obtain the create task instruction. Then steps 202 to 205 are executed. And so on until all tasks are created. That is to say, the first user can click the torsion bar multiple times to perform multiple task creations.
[0087] Next, the above step 202, that is, "in response to the create task instruction, generate a task creation requirement content interface", will be described in detail in combination with the embodiments of the present invention.
[0088] If the manual direct creation method is adopted in the embodiments of the present invention, the task creation device directly generates a task creation requirement content interface in response to the create task instruction obtained in step 201.
[0089] If the torque creation method is adopted in the embodiments of the present invention, the task creation device generates a task creation option interface in response to a task creation instruction. The task creation option interface displays a new task creation option and an existing task extension option. If the first user clicks the new task creation option, a new task creation instruction is generated. After the task creation device obtains the new task creation instruction, it generates a task creation requirement content interface. If the first user clicks the existing task extension option, an existing task extension instruction is generated. It should be noted that if the result of the existing task does not meet the expectation, the first user will click the existing task extension option. Exemplarily, if the result of the task with task number 1105 in sequence B does not meet the expectation, the first user will click on this task option. After the task creation device obtains the existing task extension instruction, it generates an existing task extension interface. The existing task extension interface displays the name or task number option of the task to be extended and a location positioning option. The name or task number option of the task to be extended is retrieved from the existing task library by the first user after entering a prompt word in the search box. The location positioning options include: product idea + calculation option, content plan option, and technical level option. The first user selects the name or task number of the task to be extended and the location positioning. The task creation device obtains the name or task number of the task to be extended selected by the first user and the selected location positioning. The task creation device generates a task creation requirement content interface in response to the name or task number of the task to be extended selected by the first user and the selected location positioning, as Figure 4 shown.
[0090] It should be noted that the product idea + calculation option represents that there is a direction for re - design in the task to be extended, that is, the overall content is redone. The product idea includes: the goal of enhancing team collaboration from a new application logic, saving time costs, reducing the human error rate, reducing production processes, reusability, and sustainable learnability. The calculation includes: data parameter range, quantization field, data format, traceability requirements, application scenarios, application processes, role design, and the expected effect quantization of team competitiveness. That is to say, once the above - mentioned data parameter range, quantization field, data format, traceability requirements, application scenarios, application processes, role design, and the expected effect quantization of team competitiveness change, they all belong to the scope of calculation. The content plan option represents that there is a direction for optimization in the task to be extended, that is, most or a small part of the content is redone. The content plan includes fields, function · performance parameters, legality · security, adequacy of interaction experience, and in - depth work on positive reviews. The technical level option represents that there is a direction for technological innovation in the task to be extended. The technical level includes: rewriting the front - end and back - end code, that is, updating the implementation technology. Specifically, such as computer language replacement, writing optimization, and database re - configuration.
[0091] The following describes in detail the above step 203, that is, "obtain the target content filled in by the first user on the task creation requirement content interface, where the target content is the attribute information of the subtask to be generated".
[0092] In the embodiments of the present invention, it should be noted that a host configuration button may also be displayed on the task creation requirement content interface. After the first user fills in the target content on the task creation requirement content interface and clicks the host configuration button, a host configuration instruction is generated. The task creation device can obtain the target content and the host configuration instruction.
[0093] Among them, the target content is the attribute information of the subtask to be generated. Specifically, the target content includes: the module to which the subtask belongs (a product or engineering project is divided into three segments in terms of quantity, namely the total quantity, the partial quantity, and the single quantity. The total quantity and the single quantity cannot be further divided. The partial quantity can be further divided into smaller parts. A module is a partial quantity), the framework under the module (the framework is the smaller part after the partial quantity is further divided), the technical column to which the subtask belongs (tasks with certain same attributes are classified into a technical column), the subtask name, and management parameters. The management parameters include: the input direction (used to represent the direction applicable to the new task. For example, organizational capacity building, intelligent finance, marketing cloud platform), the user scenario (can choose only internal interaction, only external interaction, or all), the pressure level (can choose low frequency, medium frequency, high frequency. Among them, low frequency, medium frequency, and high frequency respectively correspond to the frequencies of the user operating the new task being low frequency, medium frequency, and high frequency), and the optimal external economic and intellectual team (can choose yes or no). Among them, the optimal external economic and intellectual team refers to a team that uses empirical knowledge and labor and is more practical in terms of technology.
[0094] The following describes in detail the above step 204, that is, "generate a subtask of the target task in response to the target content".
[0095] In an embodiment of the present invention, the task creation device generates a host configuration interface in response to a target content and a host configuration instruction. A first user fills in host content in the host configuration interface. The task creation device can obtain the host content. The task creation device generates a to-be-acknowledged subtask of the target task in response to the host content. The theater supervisor of the theater to which the to-be-acknowledged subtask belongs (responsible for theater operation and achievement of work objectives. Main responsibilities: 1. Whether the task is within the scope of the team's tactical agreement; 2. Whether the task creation technical column (grouping tasks with the same attributes into one technical column) is compliant; 3. The task plan of the tactical agreement) acknowledges the to-be-acknowledged subtask. The task creation device can obtain a tactical acknowledgment instruction for acknowledging the to-be-acknowledged subtask. The task creation device generates a parameter configuration interface in response to the tactical acknowledgment instruction. The task creation device obtains the parameters (including financial parameters, cycle parameters, and execution technical parameters) written by the first user or the theater supervisor of the theater to which the to-be-acknowledged subtask belongs in the parameter configuration interface. A parameter consists of a main item and a description item. For example: the main item of the delivery content of a certain task: whether to deliver a development specification, the description item: 1. Deliver a development specification, 2. Temporarily do not need a development specification, this is the value of a single-choice defined parameter. After tactical acknowledgment and parameter writing, the theater manager (responsible for achieving the comprehensive objectives of a project within the theater and also responsible for the management and application of team members) or the sequence director (responsible for achieving the objectives of a production sequence and the objectives of personnel operation management of a sequence) acknowledges whether the standard of the written parameters meets the collaborative needs of the theater strategy and reviews the content acknowledged by the tactical acknowledgment instruction. The task creation device can obtain a strategy acknowledgment instruction for reviewing the written parameters and the content acknowledged by the tactical acknowledgment instruction. The task creation device generates a subtask of the target task in response to the strategy acknowledgment instruction. Exemplarily, the task number of the generated subtask is 1007. The subtask is a series of tasks of the to-be-expanded task, and the version number of the subtask is increased based on the to-be-expanded task. In an embodiment of the present invention, if the version number of the to-be-expanded task with the task number 1105 is 1.0, then the version number of the subtask with the task number 1007 can be increased based on 1.0, such as 1.1.
[0096] The following describes in detail step 205 above, that is, "display the task number of the subtask", in combination with the embodiments of the present invention.
[0097] In the embodiments of the present invention, the task numbers of subtasks are displayed in the association relationship diagram. If the newly generated subtask is the first subtask of the target task, it is displayed directly above the target task. If the newly generated subtask is not the first subtask of the target task, it is displayed beside the last subtask of the target task. Exemplarily, if the target task is located on the left side of the main association chain and the generated subtask is not the first subtask of the target task, the newly generated subtask is displayed on the left side of the last subtask of the target task. Correspondingly, if the target task is located on the right side of the main association chain and the generated subtask is not the first subtask of the target task, the newly generated subtask is displayed on the right side of the last subtask of the target task.
[0098] Exemplarily, as Figure 7 shown, the subtask with task number 1007 is displayed directly above the task with task number 1003.
[0099] It can be understood that since the subtask with task number 1007 is a series task of the task to be expanded with task number 1105, therefore, in the association relationship diagram as Figure 5 shown, only the task to be expanded with task number 1105 is displayed, and the subtask with task number 1007 is not displayed. Among them, the task to be expanded with task number 1105 has covered the subtask with task number 1007.
[0100] It should be noted that the subtask with task number 1007 can be quickly located through the positioning function.
[0101] From the above, it can be seen that in the embodiments of the present invention, it can be intuitively seen which task generates the tasks in the association relationship diagram, what its sibling tasks are, and what tasks it generates.
[0102] According to an embodiment of another aspect, a task creation device is provided. Figure 8 The schematic block diagram of the task creation device according to an embodiment is shown. The device can be set in the Figure 1 server side in the architecture shown. As Figure 8 shown, the device 800 may include: a first acquisition unit 801, a first generation unit 802, a second acquisition unit 803, a second generation unit 804, and a display unit 805. Among them, the main functions of each component unit are as follows:
[0103] The first acquisition unit 801 is configured to acquire a task creation instruction generated by a first user clicking a task creation button, and the task creation instruction is used to indicate the creation of a subtask of a target task;
[0104] The first generation unit 802 is configured to generate a task creation requirement content interface in response to the task creation instruction;
[0105] The second acquisition unit 803 is configured to acquire the target content filled in by the first user on the task creation requirement content interface;
[0106] The second generation unit 804 is configured to generate subtasks of the target task in response to the target content;
[0107] The display unit 805 is configured to display the task numbers of the subtasks.
[0108] In a possible implementation, the apparatus further includes a third generation unit;
[0109] The third generation unit is configured to acquire a click target task instruction generated by the second user clicking on the target task in the association relationship diagram; in response to the click target task instruction, generate a creation interface, where the creation interface displays a create task button and a create torque button; acquire a create torque instruction generated by the second user clicking on the create torque button; in response to the create torque instruction, generate a first requirement content interface; acquire the first requirement content filled in by the second user on the first requirement content interface, where the first requirement content is the core content of the requirement, the problems encountered, and the content in the return information area described according to the R & D process; in response to the first requirement content, generate a second requirement content interface, where the second requirement content interface displays a torque destination option and a recipient button; acquire a torque destination instruction generated by the second user after selecting the torque destination and a recipient instruction generated by the second user after clicking on the recipient button, and generate a torque bar, where the torque bar is displayed in the "Twisted to Me" interface and the association relationship diagram; acquire a click torque bar instruction generated by the first user clicking on the torque bar in the "Twisted to Me" interface or the association relationship diagram; in response to the click torque bar instruction, generate a create task button.
[0110] In a possible implementation, the first generation unit 802 is specifically configured to, in response to the create task instruction, generate a create task option interface, where the create task option interface displays a create new task option and an expand existing task option; if a create new task instruction generated by the first user selecting the create new task option is acquired, then generate a task creation requirement content interface; if an expand existing task instruction generated by the first user selecting the expand existing task option is acquired, then generate an expand existing task interface, where the expand existing task interface displays the name or task number option of the task to be expanded and a location positioning option; acquire the name or task number of the task to be expanded selected by the first user and the selected location positioning, where the name or task number option of the task to be expanded is retrieved from the existing task library by the first user after entering a prompt word in the search box; in response to the name or task number of the task to be expanded selected by the first user and the selected location positioning, generate a task creation requirement content interface.
[0111] In a possible implementation, the target content includes: the module to which the subtask belongs, the framework under the module, the technical column to which the subtask belongs, the subtask name, and management parameters. The management parameters include: input direction, user scenario, pressure level, and the optimal external intelligence group.
[0112] In a possible implementation, the location positioning options include: product idea + calculation option, content plan option, and technical level option.
[0113] In a possible implementation, the device further includes a third acquisition unit;
[0114] The third acquisition unit is used to acquire the host configuration instruction.
[0115] In a possible implementation, the second generation unit 804 is specifically configured to generate a host configuration interface in response to the target content and the host configuration instruction; acquire the host content filled in by the first user on the host configuration interface; generate a to-be-acknowledged subtask of the target task in response to the host content; acquire a tactical acknowledgment instruction for the to-be-acknowledged subtask; generate a parameter configuration interface in response to the tactical acknowledgment instruction; acquire the parameters written by the first user or the theater supervisor of the theater to which the to-be-acknowledged subtask belongs on the parameter configuration interface; acquire a strategy acknowledgment instruction for reviewing the written parameters and the content acknowledged by the tactical acknowledgment instruction; and generate a subtask of the target task in response to the strategy acknowledgment instruction. The subtask is a series of tasks of the task to be extended, and the version number of the subtask is incremented based on the task to be extended.
[0116] Each embodiment in this specification is described in a progressive manner. The same or similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiments, since they are basically similar to the method embodiments, they are described relatively simply. For the relevant parts, refer to the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art can understand and implement it without creative work.
[0117] In addition, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the steps of the method described in any one of the foregoing method embodiments are implemented.
[0118] and an electronic device, comprising:
[0119] one or more processors; and
[0120] a memory associated with the one or more processors, the memory being configured to store program instructions that, when read and executed by the one or more processors, perform the steps of the method according to any one of the foregoing method embodiments.
[0121] An embodiment of the present invention further provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method according to any one of the foregoing method embodiments.
[0122] Wherein, Figure 9 exemplarily shows the architecture of the electronic device, which may specifically include a processor 910, a video display adapter 911, a disk drive 912, an input / output interface 913, a network interface 914, and a memory 920. The above-mentioned processor 910, video display adapter 911, disk drive 912, input / output interface 913, network interface 914, and the memory 920 may be communicatively connected via a communication bus 930.
[0123] Wherein, the processor 910 may be implemented in a general-purpose CPU, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, etc., and is used to execute relevant programs to implement the technical solutions provided by the embodiments of the present invention.
[0124] The memory 920 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), a static storage device, a dynamic storage device, etc. The memory 920 may store an operating system 921 for controlling the operation of the electronic device 900, and a basic input / output system (BIOS) 922 for controlling the low-level operations of the electronic device 900. Additionally, a web browser 923, a data storage management system 924, and a task creation device 925, etc., may also be stored. The above-mentioned task creation device 925 may be the application program that specifically implements the operations of the foregoing steps in the embodiments of the present invention. In summary, when implementing the technical solutions provided by the embodiments of the present invention through software or firmware, the relevant program codes are stored in the memory 920 and are called and executed by the processor 910.
[0125] The input / output interface 913 is used to connect to the input / output module to achieve information input and output. The input / output module can be configured as a component in the device (not shown in the figure), or can be externally connected to the device to provide corresponding functions. Among them, the input device can include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device can include a display, a speaker, a vibrator, an indicator light, etc.
[0126] The network interface 914 is used to connect to the communication module (not shown in the figure) to achieve communication and interaction between this device and other devices. Among them, the communication module can achieve communication through wired means (such as USB, network cable, etc.), or can also achieve communication through wireless means (such as mobile network, WIFI, Bluetooth, etc.).
[0127] The bus 930 includes a path for transmitting information between various components of the device (such as the processor 910, the video display adapter 911, the disk drive 912, the input / output interface 913, the network interface 914, and the memory 920).
[0128] It should be noted that although the above device only shows the processor 910, the video display adapter 911, the disk drive 912, the input / output interface 913, the network interface 914, the memory 920, the bus 930, etc., in the specific implementation process, this device may also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above device may also only include the components necessary to implement the solution of the present application, and do not have to include all the components shown in the figure.
[0129] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the essence of the above technical solution, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.
[0130] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, rather than limiting them; although the embodiments of the present invention have been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.
Claims
1. A task creation method, characterized in that: include: Obtaining a task creation instruction generated by the first user clicking a create task button, wherein the task creation instruction is used to instruct the creation of a subtask of the target task; In response to the task creation instruction, generating a task creation requirement content interface; Obtaining target content filled in by the first user in the task creation requirement content interface, where the target content is attribute information of the subtask to be generated; In response to the target content, generating subtasks of the target task; Displays the task number of the subtask.
2. The method according to claim 1, characterized in that Before obtaining the task creation instruction generated by the first user clicking the create task button, the method further includes: Obtaining a click target task instruction generated by the second user clicking the target task in the association relationship graph; In response to the click target task instruction, a creation interface is generated, wherein the creation interface displays a create task button and a create torque button; Obtain a torque creation instruction generated by the second user clicking a torque creation button; In response to creating the torque command, generating a first demand content interface; Obtaining the first requirement content filled in by the second user on the first requirement content interface, where the first requirement content is the core content of the requirement, the problems encountered, and the content of the return information area explained according to the R&D process; In response to the first demand content, generating a second demand content interface, wherein the second demand content interface displays a torque destination option and a recipient button; Obtain the torque destination instruction generated after the second user selects the torque destination and the recipient instruction generated after clicking the recipient button, and generate a torque bar, which is displayed in the "Torque to Me" interface and the association relationship diagram; Obtaining a torque bar click instruction generated by the first user clicking the torque bar in the "Twist for Me" interface or the association relationship diagram; In response to the click torque bar instruction, a create task button is generated.
3. The method according to claim 2, characterized in that The step of generating a task creation requirement content interface in response to the task creation instruction includes: In response to the create task instruction, generate a create task option interface, wherein the create task option interface displays a create new task option and an expand existing task option; If a new task creation instruction generated by the first user selecting the create a new task option is obtained, a task creation requirement content interface is generated; If an expand existing task instruction generated by the first user selecting the expand existing task option is obtained, an expand existing task interface is generated, wherein the expand existing task interface displays a name or task number option and a location positioning option of the task to be expanded, wherein the name or task number option of the task to be expanded is retrieved from the existing task library after the first user enters a prompt word in the search box; Obtaining the name or task number of the task to be expanded and the selected location position selected by the first user; In response to the name or task number of the task to be expanded and the location selected by the first user, a task creation requirement content interface is generated.
4. The method according to any one of claims 1 to 3, characterized in that: The target content includes: the module to which the subtask belongs, the framework under the module, the technical column to which the subtask belongs, the subtask name and management parameters. The management parameters include: investment direction, user scenario, pressure level and optimal foreign economic intelligence group.
5. The method according to claim 3, characterized in that: The positioning options include: product creative + calculation options, content planning options and technical level options.
6. The method according to claim 3, characterized in that After generating a task creation requirement content interface in response to the task creation instruction, the method further includes: Get the host configuration instructions.
7. The method according to claim 6, characterized in that The step of generating a subtask of the target task in response to the target content includes: In response to the target content and the sponsor configuration instruction, generating a sponsor configuration interface; Obtaining the sponsor content filled in by the first user in the sponsor configuration interface; In response to the sponsor content, generating a subtask to be approved of the target task; Obtaining a tactical approval instruction for the subtask to be approved; In response to the tactical approval instruction, generating a parameter configuration interface; Obtaining the parameters written by the first user or the theater supervisor of the theater to which the subtask to be approved belongs in the parameter configuration interface; Obtaining a strategic approval instruction for reviewing the written parameters and the contents approved by the tactical approval instruction; In response to the policy approval instruction, a subtask of the target task is generated, the subtask being a series of tasks of the task to be extended, and a version number of the subtask is increased based on the task to be extended.
8. A task creation device, characterized in that: include: A first acquisition unit is used to acquire a task creation instruction generated by a first user clicking a create task button, wherein the task creation instruction is used to instruct to create a subtask of a target task; A first generating unit, configured to generate a task creation requirement content interface in response to the task creation instruction; A second acquisition unit is used to acquire target content filled in by the first user in the task creation requirement content interface, where the target content is attribute information of the subtask to be generated; A second generating unit, configured to generate subtasks of the target task in response to the target content; The display unit is used to display the task number of the subtask.
9. An electronic device, characterized in that: include: A memory and a processor, wherein the processor and the memory communicate with each other via a bus; The memory stores program instructions executable by the processor, and the processor can execute the method according to any one of claims 1 to 7 by calling the program instructions.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.