Schedule configuration method, and related device
By displaying configuration controls and drop-down menus in the schedule table, users can configure and create multi-level sub-work items, solving the problem of existing technologies being unable to break down and subdivide nodes and tasks, thus improving project management efficiency and user experience.
Patent Information
- Application Number
- PCT/CN2025/079602
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-05-30
- Filing Date
- 2025-02-27
- Publication Date
- 2025-12-04
AI Technical Summary
In existing technologies, planning tables can only be managed according to process nodes, and cannot further break down and subdivide nodes or tasks. This makes it impossible for users to intuitively view the detailed information of work items, and work items do not support further breakdown and subdivision.
A method and apparatus for configuring a schedule are provided. By displaying configuration controls in the schedule, users can display drop-down menus at node positions to select and configure various types of sub-work items, and create corresponding sub-work items in response to user selection instructions. The method supports the creation and management of multi-level nodes and sub-work items.
It enables multi-level breakdown and information display of the schedule, allowing users to better manage projects and improving user experience and work efficiency.
Smart Images

Figure CN2025079602_04122025_PF_FP_ABST
Abstract
Description
Configuration schedule and related equipment
[0001] Cross-reference to related applications
[0002] This application claims priority to Chinese Patent Application No. 202410693440.3, filed on May 30, 2024, entitled “Method and Related Equipment for Configuring a Schedule”, the entire contents of which are incorporated herein by reference. Technical Field
[0003] This disclosure relates to the field of computer technology, and in particular to a method and related equipment for configuring a schedule. Background Technology
[0004] With the continuous development of internet technology, many tasks can be completed intelligently. For example, a project can be managed in a process-oriented manner using a schedule. Summary of the Invention
[0005] This disclosure proposes a method and related equipment for configuring a schedule to solve or partially solve the above-mentioned problems.
[0006] In a first aspect, this disclosure provides a method for configuring a schedule, including:
[0007] The schedule table is displayed, and the schedule table includes multiple nodes;
[0008] In response to a configuration instruction for a target node among the plurality of nodes, and the target node is a leaf node, a first menu is displayed at the associated location of the target node, the first menu including at least one first option for configuring multiple types of sub-work items for the target node;
[0009] In response to a selection instruction for a first target option among the plurality of first options, a first target sub-work item corresponding to the first target option is created.
[0010] A second aspect of this disclosure provides an apparatus for configuring a schedule, comprising:
[0011] The first display module is configured to display the schedule, which includes multiple nodes.
[0012] The second display module is configured to: in response to a configuration instruction for a target node among the plurality of nodes, wherein the target node is a leaf node, display a first menu at the associated location of the target node, the first menu including at least one first option for configuring multiple types of sub-work items for the target node;
[0013] The creation module is configured to: in response to a selection instruction for a first target option among the plurality of first options, create a first target sub-work item corresponding to the first target option.
[0014] A third aspect of this disclosure provides a computer device including one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and executed by the one or more processors, the programs including instructions for performing the method according to the first aspect.
[0015] A fourth aspect of this disclosure provides a non-volatile computer-readable storage medium containing a computer program that, when executed by one or more processors, causes the processors to perform the method described in the first aspect.
[0016] A fifth aspect of this disclosure provides a computer program product, including a computer program, characterized in that, when executed by a processor, the computer program implements the steps of the method as described in the first aspect. Attached Figure Description
[0017] To more clearly illustrate the technical solutions in this disclosure or related technologies, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0018] Figure 1A shows a schematic diagram of an exemplary system provided in an embodiment of this disclosure.
[0019] Figure 1B shows a schematic diagram of an exemplary page 110.
[0020] Figure 2A shows a schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0021] Figure 2B shows another schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0022] Figure 2C shows yet another schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0023] Figure 2D shows yet another schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0024] Figure 2E shows yet another schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0025] Figure 2F shows yet another schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0026] Figure 2G shows yet another schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0027] Figure 2H shows yet another schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0028] Figure 2I shows yet another schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0029] Figure 2J shows yet another schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0030] Figure 2K shows yet another schematic diagram of an exemplary page according to an embodiment of this disclosure.
[0031] Figure 2L shows yet another schematic diagram of an exemplary page according to an embodiment of the present disclosure.
[0032] Figure 3 shows a flowchart illustrating an exemplary method provided in an embodiment of this disclosure.
[0033] Figure 4 shows a schematic diagram of an exemplary device provided by an embodiment of the present disclosure.
[0034] Figure 5 shows a schematic diagram of the hardware structure of an exemplary computer device provided in an embodiment of this disclosure. Detailed Implementation
[0035] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.
[0036] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this disclosure should have the ordinary meaning understood by one of ordinary skill in the art to which this disclosure pertains. The terms "first," "second," and similar terms used in the embodiments of this disclosure do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed following the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are used only to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.
[0037] It is understood that before using the technical solutions of the various embodiments in this disclosure, users will be informed of the type, scope of use, and usage scenarios of the personal information involved in an appropriate manner, and user authorization will be obtained.
[0038] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose, based on the prompt message, whether to provide personal information to the software or hardware such as electronic devices, applications, servers, or storage media performing the operations of this disclosed technical solution.
[0039] As an optional but not limited implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.
[0040] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.
[0041] In related technologies, planning tables can only be managed according to process nodes, which is inconvenient to use.
[0042] Figure 1A shows a schematic diagram of an exemplary system 100 provided in an embodiment of this disclosure.
[0043] As shown in Figure 1A, system 100 can be used to implement online or offline project management functions, and may include terminal devices 102A and 102B, server 106, and database server 108. A medium (e.g., a network) may be included to provide a communication link between terminal devices 102A and 102B and server 106 and database server 108. This network may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.
[0044] The terminal devices 102A and 102B can be equipped with various applications (APPs) or software, such as project management applications or software, collaborative office applications or software, image processing applications or software, video conferencing applications or software, reading applications or software, video applications or software, social applications or software, payment applications or software, web browsers, and instant messaging tools. In some embodiments, these applications or software can all be used for project management.
[0045] The terminal devices 102A and 102B here can be either hardware or software. When terminal devices 102A and 102B are hardware, they can be various electronic devices with displays, including but not limited to smartphones, tablets, e-book readers, MP3 players, laptops, and desktop computers (PCs). When terminal devices 102A and 102B are software, they can be installed in the electronic devices listed above. They can be implemented as multiple software programs or software modules (e.g., to provide distributed services) or as a single software program or software module. No specific limitations are set here.
[0046] Server 106 can be a server that provides various services, such as a backend server that supports various applications displayed on terminal devices 102A and 102B. Database server 108 can also be a database server that provides various services. It is understood that if server 106 can implement the relevant functions of database server 108, database server 108 may not need to be set up in system 100.
[0047] The server 106 and database server 108 here can be either hardware or software. When they are hardware, they can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When they are software, they can be implemented as multiple software programs or software modules (e.g., used to provide distributed services), or as a single software program or software module. No specific limitations are made here.
[0048] It should be noted that the document editing method provided in this embodiment can be executed by the server 106. It should be understood that the number of terminal devices, users, servers, and database servers in Figure 1A is merely illustrative. Depending on implementation needs, any number of terminal devices, users, servers, and database servers can be included.
[0049] In some embodiments, project management applications or software may be installed on terminal devices 102A and 102B, and users 104A and 104B can use these applications or software to manage projects. For example, they can set up project workflows and work items related to workflow nodes. As an optional embodiment, user 104A can be the project administrator, responsible for coordinating the management of the entire project workflow. User 104B can be a participant in the project; after user 104A establishes the workflow, user 104B can view the workflow and operate according to it.
[0050] In some embodiments, a schedule can be used to illustrate the project process.
[0051] Figure 1B shows a schematic diagram of an exemplary page 110.
[0052] As shown in Figure 1B, in related technologies, only sub-processes, nodes, and tasks of a project can be created under the planning table, and further decomposition and subdivision of nodes or tasks cannot be achieved.
[0053] In some cases, nodes can be refined by adding work items. However, work items are not displayed in the schedule, making it difficult for users to view the details of the work items intuitively. Furthermore, work items do not support further breakdown or subdivision.
[0054] In view of this, one aspect of the present disclosure provides a method for configuring a schedule.
[0055] Figure 2A illustrates a schematic diagram of an exemplary page 200 according to an embodiment of the present disclosure. This page 200 can be used to configure a schedule.
[0056] As shown in Figure 2A, in some embodiments, user 104A can open collaborative office software using terminal device 102A, and page 200 can be displayed on terminal device 102A. Page 200 can display and configure a schedule. This schedule can be displayed based on a pre-configured process. As shown in Figure 2A, the schedule divides the project into multiple stages, each stage can be further broken down into sub-processes and nodes, sub-processes can be further broken down into nodes, and nodes can be further broken down into sub-nodes.
[0057] As shown in Figure 2A, in some embodiments, the schedule table can display configuration controls 202A to 202J that correspond one-to-one with each node, so that user 104A can further configure the nodes by triggering the configuration controls.
[0058] It is understood that the form of the configuration controls is not limited to that shown in Figure 2A. In some embodiments, as shown in Figure 2B, configuration controls 204A and 204B can also be used to trigger configuration. As an optional embodiment, as shown in Figure 2B, configuration controls 204A and 204B can have different prompts depending on the object that the configuration control can configure. For example, configuration control 204A, used for configuring sub-work items, can display the words "Add Sub-Work Item," while configuration control 204B, used for configuring nodes, can display the words "Add Node." Thus, the user can trigger different configuration functions by triggering different configuration controls. Optionally, as shown in Figure 2B, since sub-work items are a lower-level concept than nodes, and nodes can have sibling or parent-child relationships, the layout positions of configuration controls 204A and 204B can be different. For example, configuration control 204A is indented relative to configuration control 204B to indicate that it belongs to a lower-level concept. The user can immediately understand this by observing this difference. In some embodiments, nodes in the schedule may include nodes that can have nodes or sub-work items added and nodes that cannot have nodes or sub-work items added. Therefore, configuration controls 204A and 204B are displayed in the schedule only for nodes that can have nodes or sub-work items added. For nodes that cannot have nodes or sub-work items added, configuration controls 204A and 204B will not be displayed in the corresponding position of the node in the schedule, as shown in Figure 2B. In this way, user 104A can clearly see which nodes can have objects added, making it more convenient to use.
[0059] Returning to Figure 2A, for example, if user 104A clicks on the configuration control 202A corresponding to the target node (e.g., node 1), different drop-down menus can be displayed on one side of node 1 depending on the nature of node 1.
[0060] As an optional embodiment, if node 1 is a leaf node (i.e., node 1 has no child nodes), a first menu 206 can be displayed at the associated location of node 1 (e.g., below node 1), as shown in FIG2C. Optionally, the first menu 206 includes at least one first option 2062A to 2062D for configuring multiple types of sub-work items for the target node. For example, first option 2062A is used to configure activity-type sub-work items, first option 2062B is used to configure task-type sub-work items, first option 2062C is used to configure problem-type sub-work items, and first option 2062D is used to configure risk-type sub-work items. In this way, by providing configuration options for multiple types of sub-work items, users can create different types of sub-work items to deal with different situations.
[0061] In some embodiments, if user 104 selects a first target option (e.g., first option 2062B), terminal device 102A can create a first target sub-task item 208 corresponding to the first option 2062B for node 1. Optionally, after the first target sub-task item 208 is created, it can also be displayed in the schedule table, as shown in FIG2D. For example, as shown in FIG2D, since the first option 2062B is a sub-task used to create a task type, the first target sub-task item 208 is a subtask under node 1.
[0062] Optionally, as shown in Figure 2D, the name of the first target sub-item 208 has a different formatting relative to the name of the target node (e.g., node 1). For example, the name of the first target sub-item 208 is indented relative to the name of node 1 to indicate that they are parent and child, and the user can immediately understand this by observing this difference.
[0063] As an optional embodiment, when creating a sub-work item, it can be created directly based on the default values configured in the background. That is, when one or more key fields (or required fields) of the first target sub-work item are not empty, the corresponding type of sub-work item can be created directly, thus saving the user 104A the trouble of filling in the key fields one by one. In some embodiments, after the first target sub-work item 208 is automatically created, the cursor can continue to stay at the name of the first target sub-work item 208, so that the user 104A can further enter the name of the first target sub-work item 208, so that the user 104A can name the first target sub-work item 208, avoiding the problem of difficulty in distinguishing different sub-work items caused by using the default name.
[0064] In some cases, the key fields of newly created sub-work items may not have default values. Therefore, when one or more key fields of the first target sub-work item are empty (e.g., the responsible person field is empty), a first window 210 for configuring the target key field is displayed, as shown in Figure 2E. Optionally, the first window 210 may pop up automatically when any one of the key fields of the first target sub-work item is empty. In other words, when any one of the key fields of the first target sub-work item is empty, the sub-work item cannot be created automatically; instead, the key fields need to be filled in through this window 210 before the sub-work item can be created.
[0065] Optionally, the first window 210 can display multiple fields for the corresponding type of sub-work item. The field names of key fields are marked with an asterisk (*) in the upper right corner to indicate to the user that they are key fields and cannot be empty. To further remind the user to fill in the key fields (104A), window 210 also displays the message "Because there are required fields without default values, you must fill in the required fields before creating the sub-work item," thus ensuring that the user completes the key fields in window 210.
[0066] When the target key field is configured with a target value (for example, the person in charge field is configured with "personnel 1"), the terminal device 102A can create a first target sub-work item 208 corresponding to the first target option based on the target value for the target node, and display the first target sub-work item 208 in the plan table, as shown in Figure 2D.
[0067] In some embodiments, after the key fields of the sub-work item are filled in, a second window 212 can be further displayed, as shown in Figure 2F. Optionally, the second window 212 can also configure the process type and relationship type for the sub-work item 208, thereby clarifying the process to which the sub-work item 208 belongs and its relationship with process nodes. Sub-work items can then be filtered based on the process type and relationship type for user convenience.
[0068] At this point, sub-work item 208 has been created.
[0069] It is understood that the field information of the sub-work item shown in the figure is merely exemplary. Optionally, the field information of the sub-work item may include:
[0070] Name: Sub-item name;
[0071] Roles: If a sub-task item has an overall schedule and a corresponding role, the roles listed here are the roles it belongs to.
[0072] Person in Charge: If the sub-work item has the overall scheduling function enabled and has a person in charge configured, the person in charge and the overall scheduling function are linked in two ways. That is, if the configuration information in the plan table is modified, the person in charge information in the overall scheduling function will also be modified accordingly.
[0073] Scheduling: If the sub-work item has enabled the overall scheduling function and configured the scheduling field, the scheduling and overall scheduling functions are linked in two ways. That is, if the configuration information in the plan table is modified, the overall scheduling function will also modify the scheduling information accordingly.
[0074] Planned construction period: Calculate the number of working days based on the schedule;
[0075] Score estimation: If the sub-work item has the overall scheduling function enabled and the score estimation field is configured, the score estimation and the overall scheduling function will work together in both directions.
[0076] Actual working hours: If the sub-work item has the overall scheduling function enabled and the actual working hours field is configured, the actual working hours and the overall scheduling function are linked in both directions.
[0077] Actual start time: The time when the project instance was created;
[0078] Actual end time: The time it takes for the node flow to complete the process of the last node, and the time it takes for the state flow to be archived;
[0079] Deliverables: Maintaining logical consistency with sub-processes, deliverables can be configured on the instance side in both field and instance deliverable modes. Configured deliverables will be displayed in the basic information or schedule configuration information of the corresponding sub-work item;
[0080] Types: sub-work items, sub-tasks, sub-activities, sub-problems, sub-risks, etc.;
[0081] Allow deletion: Yes / No. Deleted items added by the instance side (user A or user B) are "Yes" by default.
[0082] Schedule relationship: Maintain logical consistency with sub-process nodes, and modify the schedule relationship of sub-work items by selecting the corresponding node / subtask / sub-work item from the current plan table.
[0083] Optionally, after creating a sub-item, it can be modified. For example, user 104A can double-click the first target sub-item 208 to reopen the first window 210 for editing. After editing, the updated field information of the first target sub-item 208 will be displayed in the schedule.
[0084] In some embodiments, user 104A can also create other types of sub-work items under the target node in the manner described above. In this case, sub-work items of the same type can be arranged together, while sub-work items of the task type can be placed at the front so that relevant personnel can complete the task in a timely manner.
[0085] In some embodiments, as shown in FIG2E, the first window 210 may further include a continuous creation option 2102. When user 104A selects this option 2102 in the first window 210, after the first target sub-work item 208 is created, sub-work items identical to the first target sub-work item 208 can be created continuously. Therefore, in response to receiving a continuous creation instruction for the first target sub-work item (e.g., pressing the Enter key on the keyboard), the first target sub-work item is recreated, and the newly created first target sub-work item 208A is displayed below the previous first target sub-work item, as shown in FIG2G. In this way, the user can use the continuous creation function to continuously create sub-work items of the same type, which is convenient to use.
[0086] Optionally, as shown in Figure 2G, multiple first target sub-work items 208 and 208A can be arranged in the schedule according to their creation time, and the arrangement order of the multiple first target sub-work items can be adjusted based on drag commands. For example, long-pressing the work item to be adjusted, dragging the work item to the appropriate position, and releasing it completes the order adjustment, which is convenient.
[0087] In some embodiments, referring back to Figure 2C, since the target node is a node, the first menu 206 also includes a second option 2064 for configuring sibling nodes for the target node. This allows user 104A to add other sibling nodes to the target node based on changes in the actual process, facilitating use. In response to a selection instruction for the second option 2064, terminal device 102A can create a sibling node corresponding to the second option for the target node and display the sibling node (not shown in the figure) in the schedule table. The method of creating sibling nodes is similar to the method of creating sub-work items described above, and will not be repeated here.
[0088] Furthermore, as shown in Figure 2D, a configuration control 214 can also be displayed at the associated position of the first target sub-work item 208 (for example, to the right of the name of the first target sub-work item 208), so that the user 104A can further configure the first target sub-work item 208 by triggering the configuration control 214.
[0089] Optionally, if the first target sub-item 208 is the lowest-level sub-item, the configuration control 214 is locked. For example, if the schedule can only create a maximum of 3 levels, as shown in Figure 2D, with the first level being subprocess 1, the second level being node 1, and the third level being subtask 1, then no more sub-items can be created under subtask 1, thus locking the configuration control 214. Even if user 104A clicks the second configuration control 214, the second menu cannot be displayed. In some embodiments, after the configuration control 214 is locked, in response to a hover command on the configuration control 214 (e.g., moving the cursor to the position of the configuration control 214 and holding it for a period of time), a prompt message indicating that no more sub-items can be added can be displayed (e.g., "The schedule has a maximum of 3 levels, and the maximum limit has been reached; no more can be added"). In other embodiments, the configuration can also restrict whether the first target sub-item 208 can have further sub-items added. For example, by setting the "Parent-Child Relationship" field in the first window 210 and configuring this field of the first target sub-item 208 as "Child," even if the maximum level limit is not reached, no further sub-items can be created under the first target sub-item 208. Sub-items can only be created under the first target sub-item 208 when this field is configured as "Parent." Alternatively, the "Parent-Child Relationship" field can be used to overcome the maximum level limit. When this field is configured as "Parent," even if the current first target sub-item 208 is the lowest level, further sub-items can still be created under the first target sub-item 208.
[0090] In other embodiments, if sub-items can be further created under the first target sub-item 208, in response to a configuration instruction for the first target sub-item in the schedule (e.g., clicking configuration control 214), a second menu 216 can be displayed at an associated location of the first target sub-item 208 (e.g., below the first target sub-item 208), as shown in FIG2H. Optionally, the second menu 216 may include at least one third option 2162A to 2162D for configuring multiple types of sub-items for the first target sub-item 208. Similar to the creation of the first target sub-item 208, the terminal device 102A, in response to a selection instruction for a second target option among the at least one third option, creates a second target sub-item corresponding to the second target option for the first target sub-item and displays the second target sub-item in the schedule. Optionally, the name of the second target sub-item may have a different layout format (e.g., different indentation) relative to the name of the first target sub-item, thereby achieving intuitive hierarchical distinction.
[0091] In some embodiments, in response to a configuration instruction for the first target sub-item in the schedule and the first target sub-item being a task type, a third menu 218 is displayed at an associated location (e.g., below the first target sub-item 208). The third menu 218 includes a fourth option 2182 for configuring a task-type sub-item for the first target sub-item, as shown in FIG2I. This is because task-type items require more tasks to be completed, therefore, other types of sub-items are not allowed to appear at their next level; only task-type sub-items can be created. Similar to the creation of the first target sub-item 208, in response to the completion of the fourth option configuration, a third target sub-item of the task type corresponding to the fourth option is created for the first target sub-item, and the third target sub-item is displayed in the schedule. Optionally, the name of the third target sub-item may have a different layout format (e.g., different indentation) relative to the name of the first target sub-item, thereby achieving a visual distinction between levels.
[0092] Returning to Figure 2A, as mentioned earlier, depending on the nature of node 1, different drop-down menus can be displayed at the associated location of node 1 (e.g., below).
[0093] Therefore, in some embodiments, in response to a configuration instruction for a target node (e.g., subprocess 1) among the plurality of nodes, and the target node is a non-leaf node (i.e., subprocess 1 has child nodes, such as node 1 and node 2), a fourth menu 220 is displayed at the associated position of the target node (e.g., below the target node), as shown in FIG2J. Optionally, the fourth menu 220 includes a fifth option 2202 for configuring sibling nodes for the target node and a sixth option 2204 for configuring next-level nodes for the target node. In response to a selection instruction for the fifth option 2202, the terminal device 102A can create a sibling node for the target node and display the sibling node of the target node in the schedule table; or, in response to a selection instruction for the sixth option 2204, the terminal device 102A can create a next-level node for the target node and display the next-level node of the target node in the schedule table. The method of creating sibling nodes and next-level nodes is similar to the method of creating sub-work items described above, and will not be repeated here.
[0094] In some embodiments, sub-work items can also be created in batches for multiple nodes. To enable selection of multiple nodes, as shown in Figure 2A, checkboxes 222A-222D can be displayed at the associated position of the node (e.g., to the left of the node's name). As mentioned earlier, in some embodiments, non-leaf nodes cannot create sub-work items; therefore, checkboxes 222A-222D can be displayed only at the associated position of leaf nodes (e.g., to the left of the node's name) to avoid system conflicts.
[0095] In some embodiments, in response to a batch configuration instruction for multiple first nodes (e.g., node 2, node 3) among the plurality of nodes (e.g., checkboxes 222A and 222C are selected simultaneously), batch configuration options 224A-224D for creating sub-work items for the plurality of first nodes are displayed in the associated position of the schedule (e.g., the right side of the schedule), as shown in Figure 2K. User 104A can fill in the information of the sub-work items into these batch configuration options 224A-224D. In response to the completion of the batch configuration options (e.g., clicking the OK button in the lower right corner), a fourth target sub-work item is created for each of the plurality of first nodes, and one of the fourth target sub-work items is displayed in the corresponding position of each first node in the schedule, as shown in Figure 2L. In this way, multiple sub-work items can be created at once through batching, avoiding repetitive work and improving work efficiency. In some embodiments, in response to the deletion of any fourth target sub-work item, the other fourth target sub-work items are retained to avoid the deletion of one fourth target sub-work item affecting other fourth target sub-work items.
[0096] In some embodiments, any deleted sub-item can be displayed on the Restore Deleted Contents page (e.g., accessed via the Restore Deleted Contents button on page 200 (not shown in the figure)) and can be restored before the schedule is published, facilitating timely recovery of accidentally deleted items. In some embodiments, nodes in the schedule can also be deleted. When a node is deleted, if there are sub-items under that node, a prompt message can be displayed: "After deletion, the sub-items under this node will be unbound; they can be restored before the schedule is published." If both the node and sub-items are deleted, the node can be restored along with its sub-items. Optionally, in some embodiments, on the Restore Deleted Contents page, if the parent node or sub-item has not been restored, the restore button for a single node or sub-item is locked. Hovering over the restore button displays the prompt message: "The node / sub-item to which this node / sub-item belongs needs to be restored first."
[0097] In some embodiments, in response to any of the first nodes having been configured with sub-work items, the configured sub-work items (not shown in the figure) are displayed in the associated position of the schedule (e.g., on the right side of the schedule) to avoid users repeatedly creating sub-work items and improve user work efficiency.
[0098] In some embodiments, as shown in Figure 2L, user 104A can also click the add control 226 to further display the batch configuration options for the new sub-work item, thereby enabling batch configuration of another sub-work item, which is convenient for user use and operation.
[0099] After the schedule is configured, user 104A can publish it. User 104B can view the latest published schedule and understand the latest progress of the project using their terminal device 102B. Optionally, after user 104A modifies the schedule according to the above embodiment, they need to publish the latest version of the schedule through the publishing operation so that user 104B can view the latest version of the schedule, thus maintaining the consistency of work content.
[0100] As can be seen from the above embodiments, the configuration plan method provided in this disclosure can further break down nodes and display the broken-down information in the plan, enabling users to better manage projects and improve user experience.
[0101] It should be noted that the method of this disclosure embodiment can be executed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method of this disclosure embodiment, and the multiple devices will interact with each other to complete the method described.
[0102] It should be noted that the above description describes some embodiments of this disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0103] Figure 3 illustrates a flowchart of an exemplary method 300 provided in an embodiment of this disclosure. This method 300 can be used to configure a schedule. Optionally, this method 300 can be implemented independently by the terminal devices 102A / 102B of Figure 1A, or it can be implemented by the system 100 of Figure 1A.
[0104] As shown in Figure 3, the method 300 may further include the following steps.
[0105] In step 302, the schedule is displayed, which includes multiple nodes (e.g., subprocesses 1-6 and nodes 1-4 in Figure 2A).
[0106] In step 304, in response to a configuration instruction for a target node (e.g., node 1) among the plurality of nodes, and the target node is a leaf node, a first menu (e.g., first menu 206 in FIG. 2C) is displayed at the associated location of the target node. The first menu includes at least one first option (e.g., first options 2062A-2062D in FIG. 2C) for configuring multiple types of sub-work items for the target node.
[0107] In step 306, in response to a selection instruction for a first target option among the plurality of first options (e.g., first option 2062B in FIG2C), a first target sub-work item (e.g., first target sub-work item 208 in FIG2D) corresponding to the first target option is created.
[0108] As can be seen from the above embodiments, the configuration plan method provided in this disclosure can further break down nodes and display the broken-down information in the plan, enabling users to better manage projects and improve user experience.
[0109] In some embodiments, the first menu further includes a second option for configuring sibling nodes for the target node (e.g., second option 2064 in FIG2C);
[0110] The method further includes:
[0111] In response to the selection instruction for the second option, a sibling node of the target node corresponding to the second option is created, and the sibling node of the target node is displayed in the plan table, thereby facilitating the user to create a sibling node.
[0112] In some embodiments, in response to a selection instruction for a first target option among the plurality of first options, a first target sub-work item corresponding to the first target option is created, including:
[0113] In response to a selection instruction for a first target option among the plurality of first options, determine whether one or more key fields of the first target sub-work item are empty;
[0114] In response to one or more key fields of the first target sub-work item being non-empty, create the first target sub-work item corresponding to the first target option; or,
[0115] In response to a target key field being empty in one or more key fields of the first target sub-work item, a first window for configuring the target key field is displayed (e.g., first window 210 in Figure 2E).
[0116] In response to the target key field being configured with a target value, a first target sub-work item corresponding to the first target option is created based on the target value.
[0117] In this way, in response to one or more key fields of the first target sub-work item being empty, an automatic pop-up window is used to prevent users from omitting the filling in of key fields.
[0118] In some embodiments, the method further includes:
[0119] The first target sub-work item is displayed in the schedule;
[0120] In response to a configuration instruction for the first target sub-work item in the schedule, a second menu (e.g., second menu 216 in FIG2H) is displayed at the associated location of the first target sub-work item. The second menu includes at least one third option (e.g., third options 2162A to 2162D in FIG2H) for configuring multiple types of sub-work items for the first target sub-work item.
[0121] In response to a selection instruction for a second target option among the at least one third option, a second target sub-work item corresponding to the second target option is created and displayed in the schedule.
[0122] In some embodiments, the method further includes:
[0123] The first target sub-work item is displayed in the schedule;
[0124] In response to a configuration instruction for the first target sub-work item in the schedule and the first target sub-work item is a task type, a third menu (e.g., the second menu 218 in FIG2I) is displayed at the associated location of the first target sub-work item. The third menu includes a fourth option (e.g., the fourth option 2182 in FIG2I) for configuring a sub-work item of the task type for the first target sub-work item.
[0125] In response to the completion of the fourth option configuration, a third target sub-work item of the task type corresponding to the fourth option is created and displayed in the schedule table.
[0126] In this way, sub-tasks can be further broken down into sub-sub-tasks, meeting users' more detailed needs.
[0127] In some embodiments, in the schedule, the name of the first target sub-item has a different formatting relative to the name of the target node, and the name of the second target sub-item has a different formatting relative to the name of the first target sub-item, to indicate that they are in a parent-child relationship. Users can immediately understand this by observing this difference.
[0128] In some embodiments, the method further includes:
[0129] The first target sub-work item is displayed in the schedule;
[0130] In response to receiving a continuous creation instruction for the first target sub-work item, the first target sub-work item is recreated, and the newly created first target sub-work item is displayed below the previous first target sub-work item.
[0131] This allows users to create sub-work items of the same type consecutively using the continuous creation feature, which is convenient.
[0132] In some embodiments, the method further includes: arranging multiple first target sub-work items in the schedule according to their creation time; and adjusting the arrangement order of the multiple first target sub-work items based on drag-and-drop instructions. For example, long-pressing the work item to be adjusted, dragging the work item to the appropriate position, and releasing it completes the order adjustment, which is convenient.
[0133] In some embodiments, the method further includes:
[0134] In response to a batch configuration instruction for a plurality of first nodes among the plurality of nodes, batch configuration options for creating sub-work items for the plurality of first nodes (e.g., options 224A-224D in Figure 2K) are displayed at the associated location in the schedule table;
[0135] In response to the completion of the batch configuration option configuration, a fourth target sub-work item is created for each of the plurality of first nodes, and one of the fourth target sub-work items is displayed in the corresponding position of each first node in the schedule table.
[0136] In this way, multiple sub-work items can be created at once through batch processing, avoiding repetitive work and improving work efficiency. In some embodiments, in response to the deletion of any of the fourth target sub-work items, the other fourth target sub-work items are retained to prevent the deletion of one fourth target sub-work item from affecting the other fourth target sub-work items.
[0137] In some embodiments, the method further includes: in response to the deletion of any of the fourth target sub-work items, retaining the other fourth target sub-work items to avoid the deletion of one fourth target sub-work item affecting the other fourth target sub-work items.
[0138] In some embodiments, the method further includes: in response to any of the first nodes having been configured with sub-work items, displaying the configured sub-work items at the associated location in the schedule table to avoid users repeatedly creating sub-work items and improve user work efficiency.
[0139] In some embodiments, in response to a configuration instruction for a target node among the plurality of nodes, and the target node is a leaf node, before displaying a first menu on one side of the target node, the method further includes: displaying a first configuration control (e.g., configuration controls 202A-202J of FIG2A) on one side of the target node; and receiving a configuration instruction for the target node among the plurality of nodes in response to the first configuration control being triggered, thereby facilitating the user's configuration operation.
[0140] In some embodiments, the method further includes: displaying the first target sub-work item in the schedule and displaying a second configuration control (e.g., configuration control 214 in FIG2H) at the associated location of the first target sub-work item; and locking the second configuration control in response to the first target sub-work item being the lowest-level sub-work item to prevent the user from creating a sub-work item that cannot be created, thereby causing system conflicts.
[0141] In some embodiments, after locking the second configuration control, the method further includes: in response to a hover command on the second configuration control, displaying a prompt message indicating that sub-work items cannot be added further, to remind the user of the reason why sub-work items cannot be added further at present.
[0142] In some embodiments, the method further includes:
[0143] In response to a configuration instruction for a target node among the plurality of nodes, and the target node is a non-leaf node, a fourth menu is displayed at the associated location of the target node. The fourth menu includes a fifth option to configure sibling nodes for the target node and a sixth option to configure next-level nodes for the target node.
[0144] In response to the selection instruction for the fifth option, create a sibling node of the target node and display the sibling node of the target node in the schedule table; or
[0145] In response to the selection instruction for the sixth option, a next-level node of the target node is created and displayed in the schedule table.
[0146] This makes it easy to create sibling nodes and next-level nodes for non-leaf nodes.
[0147] It should be noted that the method of this disclosure embodiment can be executed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method of this disclosure embodiment, and the multiple devices will interact with each other to complete the method described.
[0148] It should be noted that the above description describes some embodiments of this disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0149] This disclosure also provides an apparatus for configuring a schedule. Figure 4 shows a schematic diagram of an exemplary apparatus 400 provided in this disclosure. As shown in Figure 4, the apparatus 400 can be used to implement method 300 and may further include the following modules.
[0150] The first display module 402 is configured to display the schedule, which includes multiple nodes.
[0151] The second display module 404 is configured to: in response to a configuration instruction for a target node among the plurality of nodes and the target node being a leaf node, display a first menu at the associated location of the target node, the first menu including at least one first option for configuring multiple types of sub-work items for the target node;
[0152] The creation module 406 is configured to: create a first target sub-work item corresponding to the first target option in response to a selection instruction for a first target option among the plurality of first options.
[0153] In some embodiments, the first menu further includes a second option to configure a sibling node for the target node; the creation module 406 is configured to: in response to a selection instruction for the second option, create a sibling node of the target node corresponding to the second option, and display the sibling node of the target node in the schedule table.
[0154] In some embodiments, creation module 406 is configured as follows:
[0155] In response to a selection instruction for a first target option among the plurality of first options, determine whether one or more key fields of the first target sub-work item are empty;
[0156] In response to one or more key fields of the first target sub-work item being non-empty, create the first target sub-work item corresponding to the first target option; or,
[0157] In response to one or more key fields of the first target sub-work item being empty, a first window for configuring the target key field is displayed;
[0158] In response to the target key field being configured with a target value, a first target sub-work item corresponding to the first target option is created based on the target value.
[0159] In some embodiments, creation module 406 is configured as follows:
[0160] The first target sub-work item is displayed in the schedule;
[0161] In response to a configuration instruction for the first target sub-work item in the schedule, a second menu is displayed at the associated location of the first target sub-work item, the second menu including at least one third option for configuring multiple types of sub-work items for the first target sub-work item;
[0162] In response to a selection instruction for a second target option among the at least one third option, a second target sub-work item corresponding to the second target option is created and displayed in the schedule.
[0163] In some embodiments, in the schedule, the name of the first target sub-item has a different formatting relative to the name of the target node, and the name of the second target sub-item has a different formatting relative to the name of the first target sub-item.
[0164] In some embodiments, creation module 406 is configured as follows:
[0165] The first target sub-work item is displayed in the schedule;
[0166] In response to a configuration instruction for the first target sub-work item in the schedule and the first target sub-work item is a task type, a third menu is displayed at the associated location of the first target sub-work item, the third menu including a fourth option for configuring a sub-work item of the task type for the first target sub-work item;
[0167] In response to the completion of the fourth option configuration, a third target sub-work item of the task type corresponding to the fourth option is created and displayed in the schedule table.
[0168] In some embodiments, the creation module 406 is configured to: display the first target sub-work item in the schedule; and, in response to receiving a continuous creation instruction for the first target sub-work item, recreate the first target sub-work item and display the recreated first target sub-work item below the previous first target sub-work item.
[0169] In some embodiments, the creation module 406 is configured to: arrange multiple first target sub-work items in the schedule according to their creation time; and adjust the arrangement order of the multiple first target sub-work items based on drag-and-drop instructions.
[0170] In some embodiments, creation module 406 is configured as follows:
[0171] In response to a batch configuration instruction for multiple first nodes among the plurality of nodes, a batch configuration option for creating sub-work items for the plurality of first nodes is displayed at the associated location in the schedule table;
[0172] In response to the completion of the batch configuration option configuration, a fourth target sub-work item is created for each of the plurality of first nodes, and one of the fourth target sub-work items is displayed in the corresponding position of each first node in the schedule table.
[0173] In some embodiments, the creation module 406 is configured to retain the other fourth target sub-work items in response to the deletion of any of the fourth target sub-work items.
[0174] In some embodiments, the creation module 406 is configured to display the configured sub-work item at the associated location in the schedule in response to any of the first nodes having a configured sub-work item.
[0175] In some embodiments, the creation module 406 is configured to: display the first target sub-work item in the schedule and display a first configuration control at the associated position of the target node; and receive configuration instructions for the target node among the plurality of nodes in response to the first configuration control being triggered.
[0176] In some embodiments, the creation module 406 is configured to: display a second configuration control on one side of the first target sub-work item; and lock the second configuration control in response to the first target sub-work item being the lowest-level sub-work item.
[0177] In some embodiments, the creation module 406 is configured to display a message indicating that no more sub-work items can be added in response to a hover command for the second configuration control.
[0178] In some embodiments, creation module 406 is configured as follows:
[0179] In response to a configuration instruction for a target node among the plurality of nodes, and the target node is a non-leaf node, a fourth menu is displayed at the associated location of the target node. The fourth menu includes a fifth option to configure sibling nodes for the target node and a sixth option to configure next-level nodes for the target node.
[0180] In response to the selection instruction for the fifth option, create a sibling node of the target node and display the sibling node of the target node in the schedule table; or
[0181] In response to the selection instruction for the sixth option, a next-level node of the target node is created and displayed in the schedule table.
[0182] For ease of description, the above apparatus is described in terms of its functions, divided into various modules. Of course, in implementing this disclosure, the functions of each module can be implemented in one or more software and / or hardware.
[0183] The apparatus of the above embodiments is used to implement the corresponding method 300 in any of the foregoing embodiments and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0184] This disclosure also provides a computer device for implementing the method 300 described above. Figure 5 shows a schematic diagram of the hardware structure of an exemplary computer device 500 provided in this disclosure. The computer device 500 can be used to implement the server 106 of Figure 1A, or it can be used to implement the terminal devices 102A and 102B of Figure 1A. In some scenarios, the computer device 500 can also be used to implement the database server 108 of Figure 1A.
[0185] As shown in Figure 5, the computer device 500 may include: a processor 502, a memory 504, a network interface 506, a peripheral interface 508, and a bus 510. The processor 502, memory 504, network interface 506, and peripheral interface 508 are interconnected within the computer device 500 via the bus 510.
[0186] Processor 502 may be a central processing unit (CPU), a graphics processor, a neural network processor (NPU), a microcontroller (MCU), a programmable logic device, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or one or more integrated circuits. Processor 502 can be used to perform functions related to the techniques described in this disclosure. In some embodiments, processor 502 may also include multiple processors integrated as a single logic component. For example, as shown in FIG. 5, processor 502 may include multiple processors 502a, 502b, and 502c.
[0187] Memory 504 can be configured to store data (e.g., instructions, computer code, etc.). As shown in FIG5, the data stored in memory 504 may include program instructions (e.g., program instructions for implementing method 300 of embodiments of this disclosure) and data to be processed (e.g., the memory may store configuration files of other modules, etc.). Processor 502 can also access the program instructions and data stored in memory 504 and execute the program instructions to operate on the data to be processed. Memory 504 may include volatile storage devices or non-volatile storage devices. In some embodiments, memory 504 may include random access memory (RAM), read-only memory (ROM), optical disk, magnetic disk, hard disk, solid-state drive (SSD), flash memory, memory stick, etc.
[0188] Network interface 506 can be configured to provide communication with other external devices to computer device 500 via a network. This network can be any wired or wireless network capable of transmitting and receiving data. For example, the network can be a wired network, a local wireless network (e.g., Bluetooth, WiFi, Near Field Communication (NFC), etc.), a cellular network, the Internet, or a combination thereof. It is understood that the type of network is not limited to the specific examples described above.
[0189] The peripheral interface 508 can be configured to connect the computer device 500 to one or more peripheral devices to enable information input and output. For example, peripheral devices may include input devices such as keyboards, mice, touchpads, touch screens, microphones, and various sensors, as well as output devices such as displays, speakers, vibrators, and indicator lights.
[0190] Bus 510 can be configured to transfer information between various components of computer device 500 (e.g., processor 502, memory 504, network interface 506, and peripheral interface 508), such as internal buses (e.g., processor-memory bus), external buses (USB port, PCI-E bus), etc.
[0191] It should be noted that although the architecture of the computer device 500 described above only shows the processor 502, memory 504, network interface 506, peripheral interface 508, and bus 510, in specific implementations, the architecture of the computer device 500 may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the architecture of the computer device 500 described above may only include the components necessary for implementing the embodiments of this disclosure, and does not necessarily include all the components shown in the figures.
[0192] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this disclosure also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the method 300 as described in any of the above embodiments.
[0193] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.
[0194] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to perform the method 300 as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0195] Based on the same inventive concept, corresponding to the method 300 of any of the above embodiments, this disclosure also provides a computer program product, which includes a computer program. In some embodiments, the computer program is executable by one or more processors to cause the processors to perform the method 300. Corresponding to the execution entity for each step in each embodiment of method 300, the processor executing the corresponding step may belong to the corresponding execution entity.
[0196] In some embodiments, the computer program product includes program modules for resolving operational conflicts, the program modules including modules compiled as a stack-based virtual machine binary instruction set (e.g., wasm) for use by terminal devices and / or modules compiled as static libraries for use by servers.
[0197] The computer program product of the above embodiments is used to cause the processor to execute the method 300 as described in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0198] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this disclosure (including the claims) is limited to these examples; within the framework of this disclosure, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this disclosure as described above, which are not provided in detail for the sake of brevity.
[0199] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this disclosure, the provided drawings may or may not show well-known power / ground connections to integrated circuit (IC) chips and other components. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this disclosure, and this also takes into account the fact that the details of implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this disclosure will be implemented (i.e., these details should be fully understood by those skilled in the art). While specific details (e.g., circuitry) have been set forth to describe exemplary embodiments of this disclosure, it will be apparent to those skilled in the art that the embodiments of this disclosure may be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.
[0200] Although this disclosure has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.
[0201] This disclosure is intended to cover all such substitutions, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.
Claims
1. A method for configuring a schedule, comprising: displaying the schedule, the schedule including a plurality of nodes; in response to a configuration instruction for a target node of the plurality of nodes and the target node being a leaf node, displaying a first menu at an associated position of the target node, the first menu including at least one first option of configuring the target node with a plurality of types of child work items; in response to a selection instruction for a first target option of the at least one first option, creating a first target child work item corresponding to the first target option. 2.The method of claim 1, wherein the first menu further includes a second option of configuring the target node with a sibling node; the method further comprising: in response to a selection instruction for the second option, creating the sibling node of the target node corresponding to the second option and displaying the sibling node of the target node in the schedule. 3.The method of claim 1, wherein in response to a selection instruction for a first target option of the at least one first option, creating a first target child work item corresponding to the first target option, comprises: in response to a selection instruction for a first target option of the at least one first option, determining whether one or more key fields of the first target child work item are empty; in response to none of the one or more key fields of the first target child work item being empty, creating the first target child work item corresponding to the first target option; or, in response to a target key field of the one or more key fields of the first target child work item being empty, displaying a first window for configuring the target key field; in response to the target key field being configured with a target value, creating the first target child work item corresponding to the first target option based on the target value. 4.The method of claim 1, wherein the method further comprises: displaying the first target child work item in the schedule; in response to a configuration instruction for the first target child work item in the schedule, displaying a second menu at an associated position of the first target child work item, the second menu including at least one third option of configuring the first target child work item with a plurality of types of child work items; in response to a selection instruction for a second target option of the at least one third option, creating a second target child work item corresponding to the second target option and displaying the second target child work item in the schedule. 5.The method of claim 4, wherein in the schedule, a name of the first target child work item has a different formatting relative to a name of the target node, and a name of the second target child work item has a different formatting relative to a name of the first target child work item. 6.The method of claim 1, wherein the method further comprises: displaying the first target child work item in the schedule; displaying a third menu at an associated position of the first target sub-work item in response to a configuration instruction for the first target sub-work item in the schedule and the first target sub-work item being of a task type, the third menu including a fourth option to configure a sub-work item of the task type for the first target sub-work item; creating a third target sub-work item of the task type corresponding to the fourth option in response to completion of configuration of the fourth option, and displaying the third target sub-work item in the schedule. 7.The method of claim 1, wherein the method further comprises: displaying the first target sub-work item in the schedule; in response to receiving a continuous creation instruction for the first target sub-work item, creating the first target sub-work item again and displaying the first target sub-work item created again below the previous first target sub-work item. 8.The method of claim 7, wherein the method further comprises: arranging a plurality of the first target sub-work items in the schedule in a chronological order of creation time; adjusting an arrangement order of the plurality of the first target sub-work items based on a drag instruction. 9.The method of claim 1, wherein the method further comprises: in response to a batch configuration instruction for a plurality of first nodes in the plurality of nodes, displaying a batch configuration option for creating sub-work items for the plurality of first nodes at an associated position of the schedule; in response to completion of configuration of the batch configuration option, creating fourth target sub-work items for the plurality of first nodes respectively, and displaying one of the fourth target sub-work items at a corresponding position of each of the first nodes in the schedule. 10.The method of claim 9, wherein the method further comprises: in response to any of the fourth target sub-work items being deleted, retaining the other fourth target sub-work items. 11.The method of claim 9, wherein the method further comprises: in response to any of the first nodes having been configured with a sub-work item, displaying the configured sub-work item at an associated position of the schedule. 12.The method of claim 1, wherein in response to a configuration instruction for a target node in the plurality of nodes and the target node being a leaf node, the method further comprises, before displaying a first menu at an associated position of the target node: displaying a first configuration control at the associated position of the target node; in response to the first configuration control being triggered, receiving the configuration instruction for the target node in the plurality of nodes.
13. The method of claim 12, wherein, the method further comprises: displaying the first target sub-work item in the schedule and a second configuration control at an associated position of the first target sub-work item; in response to the first target sub-work item being a bottommost sub-work item, locking the second configuration control. 14.The method of claim 13, wherein after the second configuration control is locked, the method further comprises: in response to a hovering instruction for the second configuration control, displaying a prompt message that no sub-work item can be added continuously. 15.The method of claim 1, wherein the method further comprises: displaying a fourth menu at an associated position of the target node in response to a configuration instruction for the target node in the plurality of nodes and the target node being a non-leaf node, the fourth menu including a fifth option of configuring a sibling node for the target node and a sixth option of configuring a child node for the target node; creating the sibling node of the target node and displaying the sibling node of the target node in the schedule in response to a selection instruction for the fifth option; or creating the child node of the target node and displaying the child node of the target node in the schedule in response to a selection instruction for the sixth option.
16. An apparatus for configuring a schedule, comprising: a first display module configured to display the schedule, the schedule including a plurality of nodes; a second display module configured to display a first menu at an associated position of a target node in the plurality of nodes in response to a configuration instruction for the target node and the target node being a leaf node, the first menu including at least one first option of configuring a plurality of types of sub-work items for the target node; a creation module configured to create a first target sub-work item corresponding to a first target option in the plurality of first options in response to a selection instruction for the first target option.
17. A computer device, comprising one or more processors, memory; and one or more programs, wherein the one or more programs are stored in the memory and executed by the one or more processors, the programs including instructions for performing the method of any one of claims 1 to 15.
18. A non-transitory computer-readable storage medium containing a computer program which, when executed by one or more processors, causes the processors to perform the method of any one of claims 1 to 15.
19. A computer program product comprising one or more computer programs to be executed by one or more processors to implement the steps of the method of any one of claims 1 to 15.
Citation Information
Patent Citations
Project collaborative management method and system based on task nodes and storage medium
CN112215586A
Task package generation method and device, electronic equipment and storage medium
CN115617236A
Project management system and method, electronic equipment and medium
CN116796981A
Method for configuring schedule and related equipment
CN118657486A
Display control system and method for controlling a display of project management objects
US20180114178A1