Project management method and device and electronic equipment

Abstract

The embodiment of the invention discloses a project management method and device and electronic equipment. A specific embodiment of the method comprises the following steps: in response to detection of a modification operation for modifying a value of a first item into a target value, determining whether the target value passes verification according to a parent item and / or a child item of the first item; and in response to the fact that the target value passes the verification and the fact that the first item has a parent item and the parent item value of the parent item is null or is a summary value type, updating the parent item value according to the target value passing the verification, the summary value type indicating that the parent item value is obtained by summarizing the values of other items. Therefore, a new project management method is obtained, and the method can realize automatic verification and summarization according to the set membership.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a project management method, device and electronic device. Background Art

[0002] With the development of computers, users can use electronic devices to achieve various functions. For example, users can interact with other users through electronic devices, and can also use electronic devices to advance work.

[0003] In some scenarios, data management-based tools or platforms (such as project management systems) can be built to accelerate project launch and avoid project risks by creating standardized business processes. Summary of the invention

[0004] This disclosure section is provided to introduce concepts in a brief form, which will be described in detail in the detailed description section below. This disclosure section is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0005] In a first aspect, an embodiment of the present disclosure provides a method for project management, the method comprising: in response to detecting a modification operation to modify the value of a first item to a target value, determining whether the target value passes verification based on the parent item and / or child item of the first item; in response to the target value passing verification and in response to the first item having a parent item and the parent item value of the parent item is empty or is an aggregate value type, updating the parent item value based on the target value that passes the verification, wherein the aggregate value type indicates that the parent item value is obtained by aggregating the values ​​of other items.

[0006] In a second aspect, an embodiment of the present disclosure provides a project management device, the device comprising: a verification unit for determining whether the target value passes the verification based on the parent item and / or child item of the first item in response to detecting a modification operation to modify the value of a first item to a target value; an update unit for updating the parent item value based on the verified target value in response to the target value passing the verification and in response to the first item having a parent item and the parent item value of the parent item being empty or being an aggregate value type, wherein the aggregate value type indicates that the parent item value is obtained by aggregating the values ​​of other items.

[0007] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the project management method as described in the first aspect.

[0008] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the project management method as described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] Figure 1 is a flowchart of an embodiment of a method for project management according to the present disclosure;

[0011] Figure 2 is a schematic diagram of an application scenario of the project management method according to the present disclosure;

[0012] Figure 3A , Figure 3B , Figure 3C , Figure 3D , Figure 3E and Figure 3F is a schematic diagram of an application scenario of the project management method according to the present disclosure;

[0013] Figure 4 is a schematic diagram of an application scenario of the project management method according to the present disclosure;

[0014] Figure 5 is a schematic structural diagram of an embodiment of a project management device according to the present disclosure;

[0015] Figure 6 is an exemplary system architecture to which the project management method of an embodiment of the present disclosure may be applied;

[0016] Figure 7 It is a schematic diagram of the basic structure of an electronic device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0017] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

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

[0019] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0020] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0021] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0022] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0023] Here, for the convenience of explanation, some concepts that may be involved in the present disclosure are first introduced.

[0024] Project Management System: A software system used to help project teams plan, organize, execute and monitor project processes.

[0025] Space is a basic unit of organizational collaboration, which can be the management of a single project or a collection of multiple projects.

[0026] Work items are a collaborative work item for a team, or a collection of items broken down by a project. Work items can be divided into different types according to their content, such as requirements, defects, versions, iterations, milestones, deliverables, etc.

[0027] Requirements (Feature) can refer to the software functions required by users to solve a problem / achieve a goal. It can help team members track specific details.

[0028] Issues refer to those that do not meet the originally defined business requirements, for example, pop-up windows do not display.

[0029] View is a collection of query dimensions of work items that are of high frequency concern within the team. It can also be called view dual specialization. Views can be of various types, such as tables, lists, Kanban boards, Gantt charts, metrics, etc. Tables can be permutations and combinations of field information, arranging data in a cell mode. Gantt charts can display project progress in a time dimension through bar charts. Metrics are a continuous quantitative process of defining, collecting, and analyzing data for software development projects, processes, and their products. For example, demand throughput, quality, cycle and labor estimation.

[0030] Role: various roles involved in a project. A project requires the support of different roles.

[0031] WBS (W and / or k Breakdown Structure) plan, that is, work breakdown structure plan, can also be called WBS plan, or simply as a plan.

[0032] A process is a basic step in the life cycle of an event, which is composed of process nodes and execution methods in an orderly manner. Nodes can refer to the stage division points of a process.

[0033] The node leader is the person responsible for the node task. He may or may not be the person who handles the node task.

[0034] Node participant is the person who handles node tasks, but not the person in charge of node tasks.

[0035] Sub-process nodes are process subdivision areas or task packages under large-scale planning processes. Other processes introduced into a process are called sub-processes in the current process. Other nodes can be disassembled under sub-process nodes.

[0036] Subtasks, simple items at the end of the process, personnel break down or record the current to-do items of the project.

[0037] Sub-work items, more detailed transaction management at the end of the process, and front-line executors breaking down or recording the current to-do items of the project.

[0038] Scheduling is the time arrangement for an activity or task.

[0039] Planned duration is the number of days for an activity or task minus the working days.

[0040] Estimated score, actual man-days invested.

[0041] Actual work hours, the actual number of hours invested.

[0042] Please refer to Figure 1, which shows the process of an embodiment of the project management method according to the present disclosure. This embodiment can be applied to a project management system. Figure 1 The project management method shown includes the following steps:

[0043] Step 101, in response to detecting a modification operation of modifying a value of a first item to a target value, determining whether the target value passes verification according to a parent item and / or a child item of the first item.

[0044] Step 102: in response to the target value passing verification and in response to the first item having a parent item, and the parent item value of the parent item is empty or is a summary value type, updating the parent item value according to the target value passing the verification.

[0045] Here, the aggregate value type indicates that the parent item value is aggregated from the values ​​of other items.

[0046] Here, the first item can refer to the field of the node, work item or task being operated in the project management system, which may be a field in any project. Here, the fields (such as schedule, planned duration, estimated score, actual working hours) of the project elements (such as nodes, sub-process nodes, sub-tasks, sub-work items) with parent-child relationships can be set, and they can all be used as the first item.

[0047] In some embodiments, if there is a parent-child relationship between the instance to which the first item belongs and the instance to which the parent item belongs, the first item and the parent item may have a parent-child relationship. As an example, if there is a parent-child relationship between work item A and work item A1, then the schedule between work item A and work item A1 has a parent-child relationship.

[0048] The target value may refer to the new value that the user wishes to set for the first item, which needs to pass the validation rule.

[0049] Validation can be a checking process to ensure that the data entered or modified by the user complies with the rules preset by the project management system.

[0050] The parent item may be a corresponding field of a work item one level above the current work item (the instance to which the first item belongs) in the hierarchical structure of the project.

[0051] A sub-item may be a project element located one level below the current work item (the first item) in the project hierarchy.

[0052] Aggregate value type: A parent value that is automatically calculated by aggregating the values ​​of its children.

[0053] Fill value type: A value entered directly by the user or set manually, not calculated by aggregating sub-item values.

[0054] In some embodiments, the verification process of step 101 may include: when the parent item has no value, after the child item is filled in, the value of the child item is automatically summarized and displayed on the parent; when the parent item has a value, and it is the summary value of the child item, after the child item is updated, the summary value of the parent is automatically updated; when the parent is modified, it cannot be less than the child; when the parent item has a value, but it is a filled-in value, when the child item is updated, it cannot exceed the value of the parent item; when the parent item is modified, it cannot be less than the value of the existing child item.

[0055] This embodiment provides a project management method, in response to detecting a modification operation of modifying the value of a first item to a target value, determining whether the target value passes verification based on the parent item and / or child item of the first item; in response to the target value passing verification and in response to the first item having a parent item, and the parent item value of the parent item is empty or is a summary value type, updating the parent item value according to the target value that passes verification, wherein the summary value type indicates that the parent item value is obtained by summarizing the values ​​of other items. This method can not only ensure that the value of the first item is correctly updated according to the parent-child association relationship, but also automatically summarize the parent item value according to the target value modified by the user when the parent item value is empty or the parent item value is a summary value type. As a result, the accuracy of data and the efficiency of operations in the project management system are improved.

[0056] In some embodiments, the method further comprises: in response to the target value passing the verification, displaying the target value. Thus, the verified target value can be displayed in time, so that the displayed target value is more accurate, reducing the manual verification cost of project management, and improving the accuracy and timeliness of data in project management.

[0057] Please refer to Figure 2 , Figure 2 An exemplary process according to some embodiments of the present application is shown.

[0058] In step 201, a constraint item value may be modified.

[0059] The first item mentioned above may also be called a constraint item, and the first item value may be called a constraint item value.

[0060] Here, the points where the constraint item value changes can be set according to the actual scenario.

[0061] For example, the operation point can include a details page. Node card, fill in the schedule, estimated score, and actual working hours; task, schedule, estimated score, and actual working hours; node detail control, fill in the schedule;

[0062] For example, the operation point can include node information controls. Fill in the fields set under the overall scheduling of the work item.

[0063] For example, operation points can include swimlane diagrams, modifying schedules and estimating scores,

[0064] For example, the operation points can include controls in the view - personnel and scheduling, modifying scheduling and estimating scores. The operation points can include the human resources Gantt chart, the work item Gantt chart, dragging scheduling and estimating scores in the view.

[0065] For example, operation points can include view parts in the project management module of other applications, personnel and scheduling controls, overall scheduling fields, modified scheduling and scoring.

[0066] For example, the operation points can include node card scheduling and task scheduling on the mobile terminal. For node card scheduling, you can fill in the schedule and estimated score. For task scheduling, you can fill in the schedule and estimated score.

[0067] For example, the operation point may include the work time registration and writing of work time in plug-ins of other applications.

[0068] For example, operation points may include modifying node schedules, estimated scores, and actual working hours in other interfaces.

[0069] For example, the operation point can include modifying the overall schedule and estimated score fields in the automated operation. If the verification fails, there is no need to report an error, and the execution is unsuccessful.

[0070] For example, the operation point can include the scheduling synchronization in the space linkage and the value of the synchronization schedule. If the verification fails, there is no need to report an error, and the execution is unsuccessful.

[0071] Step 202: Whether the currently modified value passes verification.

[0072] Step 203: If it fails, an error message is displayed.

[0073] The types of error prompts can be distinguished according to the level type of the first item and the relative relationship between the first item and the conflict.

[0074] For example, if the schedule exceeds the parent, the prompt is: the start time is earlier than the parent's start time / the end time is later than the parent's end time; if the schedule is less than the child, the prompt is: the start time is later than the child's start time / the end time is earlier than the child's end time.

[0075] As an example, the duration exceeds the parent's duration, or the schedule exceeds the parent. The duration is less than the child's duration, or the schedule is less than the child.

[0076] As an example, the estimated score exceeds the parent's estimated score, or the estimated score is less than the child's estimated score.

[0077] As examples, Actual Work exceeds the parent's Work, or Actual Work is less than the child's Work.

[0078] Step 204: If passed, write the modified value.

[0079] Here, you can write modified values ​​at the operating point.

[0080] Step 205 , determining whether the instance to which the modified value belongs has a parent value whose value is a summary value or null.

[0081] Step 206, if yes, then aggregate the modified value to the parent item.

[0082] If the answer in step 205 is no, the process ends.

[0083] As an example, see Figure 3A , Figure 3B , Figure 3C , Figure 3D , Figure 3E , Figure 3F . Figure 3A , Figure 3B , Figure 3C , Figure 3D , Figure 3E , Figure 3F , taking the planning schedule and duration of the process nodes in the planning table as an example, the implementation methods of some embodiments of the present application are explained.

[0084] Figure 3A As shown, the sub-items of process node A in the schedule include sub-process nodes A1 and A2. The sub-items of sub-process node A1 include sub-process nodes A11 and A12. The sub-items of sub-process node A2 include sub-process nodes A21 and A22. The fields of the process nodes in the schedule may include node name, person in charge, schedule, duration, estimated score, and actual working hours.

[0085] exist Figure 3A In the example, the first constraint control 301 is in a closed state. The schedules of the process nodes A1, A11, A12 and A21 have filled values. The schedules of the process nodes A, A2 and A22 have no filled values.

[0086] Figure 3B In FIG. 3 , it is shown that the first constraint control 301 is turned on. In the plan table, a sub-process node can be selected as a parent-child constraint item.

[0087] Figure 3C Shows that after Figure 3BAfter opening the first constraint control, you can check the filled values ​​in the schedule table, and get a conflict between A1's schedule (4.2-4.4) and A12's schedule (4.2-4.5), that is, the end time of the parent item is earlier than the end time of the child item. Then, you can automatically summarize and get A2's planned duration of 4.5-4.6; get A's planned duration of 4.2-4.6. After that, you can link the duration and the schedule, and get A2's duration of 2 and A's duration of 5. The automatically summarized values ​​can be displayed separately from the filled values ​​(for example, the summarized values ​​are underlined).

[0088] Figure 3D In the figure, the schedule of A is modified. The modification box shows that the schedule is to be modified to 4.1-4.3. However, because the latest start time of A's sub-item is 4.6, the 4.3 that is to be modified is earlier than 4.6, so the modified value is not verified; therefore Figure 3D After the edit box disappears, Figure 3D The schedule will not change.

[0089] Figure 3E In the figure, the schedule of A22 in the schedule table is filled in, and the filled value is 4.7 to 4.8. Since the schedules of A2 and A are summary values, the parent item of A22 has no filled value. A22 passes the verification, and the schedule of A22 can be used as the basis for summary and linkage.

[0090] Figure 3F In the figure, it is shown that Figure 3E After filling in the planned schedule for A22, the schedule for A22 is displayed as 4.7-4.8, the planned schedule for A2 is displayed as 4.5-4.8, and the planned schedule for A is displayed as 4.2-4.8; the construction period for A22 is displayed as 2, the construction period for A2 is displayed as 4, and the construction period for A is displayed as 7.

[0091] In some embodiments, step 101 may include one or more of the following:

[0092] When the first item has a parent item, in response to a parent item value of the parent item being empty, determining that the target value passes verification;

[0093] When the first item has a parent item, in response to a parent item value of the parent item being not empty and being a summary value type, determining that the target value passes verification;

[0094] When the first item has a parent item, in response to the parent item value of the parent item being not empty and being a filled value type, determining whether the target value is greater than the parent item value; in response to the target value not being greater than the parent item value, determining that the target value passes verification;

[0095] When the first item has a parent item, in response to the parent item value of the parent item being not empty and being a filled-in value type, it is determined whether the time range indicated by the target value is greater than the time range indicated by the parent item value; in response to the time range indicated by the target value being not greater than the time range indicated by the parent item value, it is determined that the target value passes the verification.

[0096] Time range: The start and end time of a work item, which may be used in validation logic to ensure time rationality and continuity. For example, the planned duration can be a time range.

[0097] Therefore, when the parent value is null and the summary value type is processed, it is automatically summarized according to the first item value; when there is a filled parent value, the comparison between the target value and the parent value ensures the logical relationship and data consistency between items with parent-child relationship.

[0098] In some embodiments, step 101 includes one or more of the following:

[0099] When the first item has a sub-item, in response to the sub-item value of the sub-item being not empty, determining whether the target value is less than the sub-item value; in response to determining that the target value is not less than the sub-item value, determining that the target value passes verification;

[0100] When the first item has a sub-item, in response to the sub-item value of the sub-item being not empty, it is determined whether the time range indicated by the target value is smaller than the time range indicated by the sub-item value; in response to determining that the time range indicated by the target value is not smaller than the time range indicated by the sub-item value, it is determined that the target value passes the verification.

[0101] Thus, when the first item has child items, the comparison between the target value and the child item value ensures the logical relationship and data consistency between the items with parent-child relationship.

[0102] In some embodiments, the method further includes: in response to detecting a modification operation that modifies the value of the first item to a target value, determining whether the instance to which the first item belongs is a preset constraint type; if so, in response to detecting a modification operation that modifies the value of the first item to a target value, determining whether the target value passes verification based on the parent item and / or child item of the first item.

[0103] Here, the preset constraint type includes one or more of the following: sub-process node, node, sub-task, sub-work item.

[0104] In some embodiments, the method further includes: configuring a constraint type in a work item management space of the project management system.

[0105] In some embodiments, the method further includes: when a first constraint control of the schedule is in an open state, configuring a constraint type in a schedule interface of the project management system.

[0106] As an example, see Figure 4 , Figure 4 It shows how to configure constraint types in the work item management space interface.

[0107] exist Figure 4 In the work item management control interface, a second constraint control 401 may be included. When the second constraint control 401 is turned on, the constraint type may be configured. Candidates for the constraint type may include nodes, sub-process nodes, sub-work items, and sub-tasks. Figure 4 , selecting Task as the constraint type is shown.

[0108] Thus, allowing users to configure constraint types in the project management system provides flexibility and customization, so that project management can adapt to different project management needs.

[0109] In some embodiments, when the first constraint control of the schedule is in the turned-on state, the constraint type is configured in the schedule interface of the project management system, including one or more of the following: configuring the constraint type for multiple work items in the schedule; configuring the constraint type for a single work item in the schedule.

[0110] Optionally, you can configure the constraint type that applies to a single work item in a single row of the schedule.

[0111] Optionally, the constraint type may be centrally configured in the first constraint control of the schedule.

[0112] If the constraint type of a single configuration conflicts with the constraint type of a centrally configured schedule, the constraint type of a single configuration applies to the work item, and the constraint type of a centrally configured schedule applies to other work items without a single configuration.

[0113] Therefore, configuration options of constraint types are provided in the schedule interface, allowing users to set constraints for single or multiple work items, thereby improving the functionality and flexibility of the schedule.

[0114] In some embodiments, the method further includes: in response to the target value failing verification, displaying a first prompt message.

[0115] Here, the first prompt information is used to prompt that the target value conflicts with the parent item and / or the child item.

[0116] As an example, see Figure 3C The first prompt message is shown to remind A1 of the schedule conflict.

[0117] This can provide timely feedback information to the user to guide the user's operation or remind the user to pay attention to the conflict problem. When the verification fails, an error prompt is provided to help the user quickly identify and resolve data conflicts, thereby improving the user experience and the accuracy of data input.

[0118] In some embodiments, the method further includes: before the modification operation, displaying second prompt information for the first item.

[0119] Here, the second prompt information is used to prompt the value range of the first item, wherein the value range of the first item is generated according to the parent item and / or child item of the first item.

[0120] As an example, when the user selects a field value (indicating that the user may modify the field value) but does not enter a new field value, the value range of the first item may be displayed.

[0121] Therefore, prompt information is provided before the user performs the modification operation to display the value range of the first item, thereby helping the user understand the range of expected values ​​and preventing erroneous data input.

[0122] In some embodiments, in response to a trigger operation on a work item value of a summary value type, third prompt information is displayed.

[0123] Here, the third prompt information is used to prompt that if a work item value of a summary value type is modified, the modified work item value constrains the sub-item corresponding to the work item value.

[0124] In some embodiments, the modified work item value is of a fill-in value type.

[0125] In some embodiments, the method further includes: using different display styles to display the work item values ​​of the filled-in value type and the summarized value type (eg Figure 3C A dashed underscore is used to indicate the type of summary value).

[0126] Therefore, the intuitiveness and ease of use of the user interface are enhanced by distinguishing between filled-in values ​​and summary values ​​through different display styles and providing additional prompts when modifying summary values.

[0127] In some embodiments, the method further includes: in response to deleting the target value, generating a summary value of the first item based on the sub-items of the first item.

[0128] As a result, summary values ​​are automatically generated based on sub-items after the target value is deleted, reducing the need for manual operations and improving the level of automation in data processing.

[0129] In some embodiments, the content type of the first item includes one or more of the following: planned schedule, planned duration, estimated score, and actual working hours.

[0130] Optionally, the planned duration can be called the duration.

[0131] Optionally, a normal node can be called a node.

[0132] Therefore, the types of the first item include schedule planning, planned duration, estimated scores, actual working hours, etc., and automatic verification and aggregation can be achieved for numeric fields with parent-child relationships.

[0133] In some embodiments, the schedule and the duration can be linked. The first item is the schedule, the target value is the schedule value; and the method further includes: in response to the schedule value passing verification, updating the duration value according to the schedule value passing verification.

[0134] In some embodiments, the verification rules for the planning schedule are as follows.

[0135] Here, the scheduling verification rules for the sub-process nodes are as follows.

[0136] Parent item scheduling verification (i.e. parent process node, root instance). If there is an upper-level parent process node, and the parent process schedule is not empty and is not an aggregate value, the start time cannot be earlier than the start time of the parent sub-process, and the end time cannot be later than the end time of the parent sub-process. If there is no upper-level parent process node, and the overall schedule of the root instance is not empty and is not an aggregate value, the schedule start time cannot be earlier than the start time of the overall schedule of the root instance, and the schedule end time cannot be later than the end time of the overall schedule of the root instance (the overall schedule field can be configured on the work item basic information page).

[0137] Sub-item scheduling check (node). If there are nodes under the sub-process, the scheduling start time cannot be later than the earliest start time of the nodes, and the scheduling end time cannot be earlier than the latest end time of the nodes.

[0138] Here, the scheduling verification rules for common nodes are as follows.

[0139] Parent item schedule verification (sub-process node, root instance, sub-work item). If there is an upper-level parent process node and / or sub-work item, and the parent's schedule is not empty and is not an aggregate value, then when the schedule is modified, the start time cannot be earlier than the parent's start time, and the end time cannot be later than the parent's end time. If there is no upper-level parent process node, and the overall schedule of the root instance is not empty and is not an aggregate value, then when the schedule is modified, the start time cannot be earlier than the start time of the root instance's overall schedule, and the schedule end time cannot be later than the end time of the root instance's overall schedule (the overall schedule field configured on the work item basic information page).

[0140] Sub-item scheduling check (subtasks, sub-work items). If there are only subtasks under the node, when the schedule is modified, the start time cannot be later than the earliest start time of the tasks, and the scheduled end time cannot be earlier than the latest end time of the tasks. If there are only sub-work items under the node, when the schedule is modified, the start time cannot be later than the earliest start time of the first-level sub-work items, and the scheduled end time cannot be earlier than the latest end time of the tasks. If there are both, the schedule of the subtasks and the first-level sub-work items is combined for calculation.

[0141] Here, the scheduling verification rules for subtasks are as follows.

[0142] Parent Schedule Verification (Node) If the parent node's schedule is not empty and is not a summary value, when the schedule is modified, the start time cannot be earlier than the parent node's start time, and the end time cannot be later than the parent node's end time.

[0143] Here, the scheduling verification rules for sub-work items are as follows.

[0144] Parent schedule check (nodes, other child work items) If the parent schedule is not empty and is not a summary value, when the schedule is modified, the start time cannot be earlier than the start time of the parent schedule, and the end time cannot be later than the end time of the parent schedule.

[0145] Sub-item scheduling verification (other sub-work items, nodes under sub-work items). If a sub-work item has nodes and other sub-work items, when modifying the schedule, the start time cannot be later than the earliest start time of the first-level sub-work items and / or nodes, and the schedule end time cannot be later than the latest start time of the first-level sub-work items and / or nodes.

[0146] In some embodiments, please refer to the summary rules of the planning schedule as follows.

[0147] Here, the scheduling rules for sub-process nodes are summarized.

[0148] If there is an upper-level parent process node, and the schedule of the upper-level parent process node is empty or an aggregate value, the modified value will be aggregated and appended to the parent schedule. The duration of the parent process node will increase in tandem. If there is no upper-level parent process node and / or child work item, and the overall schedule of the root instance is empty or an aggregate value, the modified value will be aggregated and appended to the overall schedule of the root instance. The root instance has no duration and does not need to be changed. If it is aggregated to the direct parent and the verification and aggregation rules of the parent's predecessor are triggered, it is necessary to aggregate and / or verify the parent level of the parent layer by layer until there is a filled value on the nearest level, or it is aggregated to the root instance. If the currently modified schedule is aggregated to the parent and exceeds the filled value of the parent's parent schedule, the modification is unsuccessful.

[0149] Here, the scheduling rules for common nodes are summarized.

[0150] If there is an upper-level parent process node and / or child work item, and the parent's schedule is empty or an aggregated value, the modified value will be aggregated and appended to the parent schedule. The parent's duration will increase in tandem. If there is no upper-level parent process node and / or child work item, and the overall schedule of the root instance is empty or an aggregated value, the modified value will be aggregated and appended to the overall schedule of the root instance. The root instance has no duration and does not need to be changed. If it is aggregated to the direct parent and the verification and aggregation rules of the parent's predecessor are triggered, it is necessary to aggregate and / or verify the parent's parent level layer by layer until there is a filled value on the nearest level, or it is aggregated to the root instance. If the currently modified schedule is aggregated to the parent and exceeds the filled value of the parent's parent schedule, the modification is unsuccessful.

[0151] Here, the scheduling rules for subtasks are summarized.

[0152] If the parent node schedule is empty or a summary value, the modified value will be added to the parent schedule. The duration of the parent node will be increased. If the schedule is aggregated to the direct parent, the validation and aggregation rules of the parent's predecessor are triggered. Then, it is necessary to aggregate and / or verify the parent's parent level layer by layer until the nearest level has a filled value, or aggregate to the root instance. If the currently modified schedule is aggregated to the parent and exceeds the filled value of the parent's other parent schedules, the modification is unsuccessful.

[0153] Here, the scheduling rules for sub-work items are summarized.

[0154] If the parent node and / or child work item schedule is empty or a summary value, the modified value will be added to the parent schedule. The parent's duration will be increased. If it is aggregated to the direct parent, the verification and aggregation rules of the parent's predecessor are triggered, and it is necessary to aggregate and / or verify the parent's parent level layer by layer until there is a filled value on the nearest level, or it is aggregated to the root instance. If the currently modified schedule is aggregated to the parent and exceeds the filled value of the parent's other parent schedules, the modification is unsuccessful.

[0155] Here, the planned duration verification and summary rules are as follows.

[0156] In some embodiments, the verification rules for the planned duration are as follows.

[0157] Here are the planned duration verification rules for the sub-process nodes.

[0158] Parent duration check (parent process node). If the parent duration is not empty and is not a summary value, when the duration is modified, the duration cannot be scheduled beyond the parent's schedule, and the time range cannot be greater than the parent's duration value.

[0159] Sub-item duration check. If there are nodes under the sub-process, the duration cannot be less than the duration between the earliest start time and the latest end time of the nodes under it when the duration is modified.

[0160] Here are the planned duration verification rules for common nodes.

[0161] Parent duration check (sub-process node, root instance, sub-work item). If the parent duration is not empty and is not a summary value, when the duration is modified, the duration cannot be scheduled beyond the parent's schedule, and the time range cannot be greater than the parent's duration value.

[0162] Sub-item duration check (subtask, sub-work item). If there are only subtasks under the node, when the duration is modified, the duration cannot be scheduled less than the sub-tasks' schedule, and cannot be less than the duration between the earliest start time and the latest end time of the tasks under it. If there are only sub-work items under the node, when the duration is modified, the duration cannot be scheduled less than the sub-tasks' schedule, and cannot be less than the duration between the earliest start time and the latest end time of the first-level sub-work items. If both exist, the schedules of the subtasks and the first-level sub-work items are combined for calculation.

[0163] Here are the rules for verifying the planned duration of subtasks.

[0164] Parent duration check (node). If the parent's duration is not empty and is not a summary value, when the duration is modified, the duration cannot be scheduled beyond the parent's schedule and cannot be less than the duration between the start time and end time of the parent node.

[0165] Here are the rules for verifying the planned duration of sub-work items.

[0166] Parent item duration check (nodes, other child work items). If the parent's duration is not empty and is not a summary value, when the duration is modified, the duration cannot be scheduled beyond the parent's schedule, and cannot be less than the duration between the start time and end time of the parent's schedule.

[0167] Sub-item duration check (other sub-work items, nodes under sub-work items). If a sub-work item has nodes and other sub-work items, when modifying the duration, it cannot be less than the duration between the earliest start time of the first-level sub-work items and / or nodes and the latest start time of the first-level sub-work items and / or nodes, and the duration cannot be scheduled less than the sub-schedule.

[0168] In some embodiments, please refer to the summary rules of the planned duration as follows.

[0169] Here, the planned duration summary rules for sub-process nodes.

[0170] If there is an upper parent process node, and the duration of the upper parent process node is empty or a summary value, the modified value needs to be summarized and appended to the parent duration. The scheduling of the parent process node is linked to increase. If it is summarized to the direct parent, the verification and aggregation rules of the parent's predecessor are triggered, then it is necessary to summarize and / or verify the parent level of the parent layer by layer until there is a filled value on the nearest level, or it is summarized to the root instance. If the currently modified schedule is summarized to the parent and exceeds the filled value of the other parent durations of the parent, the modification is unsuccessful. If the duration is not exceeded, but the schedule plus the duration exceeds the value of the other parent schedules of the parent, the modification is also unsuccessful.

[0171] Here, the planned duration summary rules for common nodes are given.

[0172] If there is an upper-level parent process node and / or child work item, and the parent's duration is empty or a summary value, the modified value will be summarized and appended to the parent's duration. The parent's schedule is linked to increase. If it is summarized to the direct parent, triggering the verification and summary rules of the parent's predecessor, it is necessary to summarize and / or verify the parent's parent level layer by layer until there is a filled value on the nearest level, or summarize to the root instance. If the currently modified schedule is summarized to the parent and exceeds the filled value of the parent's other parent durations, the modification is unsuccessful. If the duration is not exceeded, but the schedule plus the duration exceeds the value of the parent's other parent schedules, the modification is also unsuccessful.

[0173] Here, the planned duration of subtasks is summarized.

[0174] If the duration of the parent node is empty or a summary value, the modified value will be added to the parent duration. The parent node's schedule is linked and increased. If it is aggregated to the direct parent, the parent item precedence is triggered. The parent's verification and aggregation rules need to be aggregated and / or verified layer by layer to the parent's parent level until there is a filled value on the nearest level, or it is aggregated to the root instance. If the currently modified schedule is aggregated to the parent and exceeds the filled value of the parent's other parent durations, the modification will fail. If the duration is not exceeded, but the schedule plus the duration exceeds the value of the parent's other parent schedules, the modification will also fail.

[0175] Here, the planned duration of sub-work items is summarized.

[0176] If the duration of the parent node and / or child work item is empty or a summary value, the modified value will be added to the parent duration. The parent's schedule will be linked. If the schedule is aggregated to the direct parent, the verification and aggregation rules of the parent's predecessor are triggered, and the parent's parent level needs to be aggregated and / or verified layer by layer until the nearest level has a filled value, or it is aggregated to the root instance. If the currently modified schedule is aggregated to the parent and exceeds the filled value of the other parent durations of the parent, the modification is unsuccessful.

[0177] In some embodiments, the verification rules for the estimated scores are as follows.

[0178] Here are the scoring verification rules for the sub-process nodes.

[0179] Parent estimated score check (parent process node). If the parent's estimated score is not empty and is not a summary value, the value range cannot be greater than the parent's estimated score when the estimated score is modified.

[0180] Sub-item score check (node). If there is a node under the sub-process, when the score is modified, it cannot be less than the sum of the scores of the nodes under it.

[0181] Verify the estimated score of ordinary nodes.

[0182] Parent item estimated score verification (sub-process node, root instance, sub-work item) If the parent's estimated score is not empty and is not a summary value, the time range cannot be greater than the parent's estimated score when the estimated score is modified.

[0183] Sub-item score verification (subtasks, sub-work items). If a node only has subtasks, the score modification cannot be less than the sum of the scores of the tasks under it. If a node only has sub-work items, the duration modification cannot be less than the duration between the earliest start time and the latest end time of the first-level sub-work items. If both exist, the schedule of the subtasks and the first-level sub-work items are combined for calculation.

[0184] The scoring verification rules for subtasks.

[0185] Parent estimated score check (node). If the parent's estimated score is not empty and is not a summary value, when the estimated score is modified, the value range cannot be greater than the parent's estimated score.

[0186] Scoring verification rules for sub-work items.

[0187] Parent item score verification (nodes, other child work items). If the parent's score is not empty and is not a summary value, the value range cannot be greater than the parent's score when the score is modified.

[0188] Sub-item score verification (other sub-work items, nodes under sub-work items). If a sub-work item has nodes and other sub-work items, when modifying the score, it cannot be less than the sum of the scores of the first-level sub-work items and / or nodes.

[0189] Score summary rules for sub-process nodes.

[0190] If there is an upper parent process node, and the upper parent process node's estimated score is empty or a summary value, the modified estimated score value will be summarized and appended to the parent's estimated score. If the summary is to the direct parent, the validation and summary rules of the parent's predecessor are triggered, and it is necessary to summarize and / or verify the parent's parent level layer by layer until there is a filled value on the nearest level, or it is summarized to the root instance. If the current modified estimated score is summarized to the parent and exceeds the filled value of the parent's parent's estimated score, the modification is unsuccessful.

[0191] Score summary rules for common nodes.

[0192] If there is a parent process node and / or child work item, and the parent's estimated score is empty or a summary value, the modified value will be summarized and appended to the parent's estimated score. If the summary is to the direct parent, the verification and summary rules of the parent's predecessor are triggered, and it is necessary to summarize and / or verify the parent's parent level layer by layer until there is a filled value on the nearest level, or it is summarized to the root instance. If the current modified estimated score is summarized to the parent and exceeds the filled value of the parent's parent's estimated score, the modification is unsuccessful.

[0193] The scoring aggregation rules for subtasks.

[0194] If the parent node's estimated score is empty or a summary value, the modified value will be summarized and appended to the parent's estimated score. If the score is summarized to the direct parent, the validation and aggregation rules of the parent's predecessor are triggered, and the parent's parent level needs to be summarized and / or verified layer by layer until the nearest level has a filled value, or it is summarized to the root instance. If the currently modified estimated score is summarized to the parent and exceeds the filled value of the parent's other parent's estimated scores, the modification is unsuccessful.

[0195] The scoring aggregation rules for sub-work items.

[0196] If the upper parent node and / or child work item estimate is empty or a summary value, the modified value will be added to the parent estimate. The parent's schedule is linked to increase. If it is aggregated to the direct parent, triggering the verification and aggregation rules of the parent's predecessor, it is necessary to aggregate and / or verify the parent's parent level layer by layer until there is a value filled in the nearest level, or aggregate to the root instance. If the currently modified estimate is aggregated to the parent and exceeds the filled-in value of the parent's other parent's estimate, the modification is unsuccessful.

[0197] In some embodiments, the verification rules for actual working hours are as follows.

[0198] Here, the actual working hours verification rules of the sub-process node. Parent working hours verification (parent process node). If the parent's working hours are not empty and are not summary values, when the working hours are modified, the value range cannot be greater than the parent's working hours value. Sub-item working hours verification. If there are nodes under the sub-process, when the working hours are modified, they cannot be less than the sum of the working hours of the nodes under it.

[0199] Here are the actual working hours verification rules for ordinary nodes. Parent item working hours verification (sub-process node, root instance, sub-work item). If the parent's working hours are not empty and are not a summary value, the time range cannot be greater than the parent's working hours when the working hours are modified. Sub-item working hours verification (sub-task, sub-work item). If there are only sub-tasks under the node, the working hours cannot be less than the sum of the working hours of the tasks under it when they are modified. If there are only sub-work items under the node, the duration cannot be less than the duration between the earliest start time and the latest end time of the first-level sub-work items when the duration is modified. If both are present, the scheduling of the sub-tasks and the first-level sub-work items is combined to calculate

[0200] Here, the actual working hours verification rules of the subtask. Parent working hours verification (node). If the parent working hours are not empty and not a summary value, when the working hours are modified, the value range cannot be greater than the parent working hours value. Sub-item working hours verification, none.

[0201] Here are the actual working hours verification rules for child work items. If the parent node working hours are empty or a summary value, the modified value will be added to the parent working hours. If the parent's working hours are not empty and are not summary values, the value range cannot be greater than the parent's working hours when the working hours are modified. Child work hour verification (other child work items, nodes under child work items). If a child work item has nodes and other child work items, when modifying the working hours, it cannot be less than the sum of the working hours of the first-level child work items and / or nodes.

[0202] In some embodiments, the aggregation rules for actual working hours are as follows.

[0203] Here, the actual working hours summary rule of the sub-process node. If there is an upper parent process node, and the working hours of the upper parent process node are empty or a summary value, the modified working hours value will be summarized and appended to the parent working hours. If it is summarized to the direct parent, the verification and summary rules of the parent's predecessor are triggered, and it is necessary to summarize and / or verify the parent's parent level layer by layer until there is a filled value on the nearest level, or it is summarized to the root instance. If the actual working hours currently modified are summarized to the parent and exceed the filled value of the actual working hours of the other parents of the parent, the modification is unsuccessful.

[0204] Here are the actual working hours summary rules for common nodes. If there is an upper parent process node and / or child work item, and the parent's working hours are empty or are summary values, the modified values ​​will be summarized and appended to the parent's working hours. If it is summarized to the direct parent, the verification and summary rules of the parent's predecessor are triggered, and it is necessary to summarize and / or verify the parent's parent level layer by layer until there is a filled value on the nearest level, or it is summarized to the root instance. If the actual working hours currently modified are summarized to the parent and exceed the filled value of the actual working hours of the parent's other parents, the modification is unsuccessful.

[0205] Here, the actual working hours of the subtask are summarized. If the summary is to the direct parent, the verification and summary rules of the parent's predecessor are triggered, and then it is necessary to summarize and / or verify the parent's parent level layer by layer until there is a value filled in the nearest level, or it is summarized to the root instance. If the actual working hours of the current modification are summarized to the parent and exceed the actual working hours filled in the other parents of the parent, the modification is unsuccessful.

[0206] Here are the rules for summarizing the actual working hours of child work items. If the working hours of the parent node and / or child work item are empty or are summary values, the modified values ​​will be summarized and appended to the parent working hours. If the summary is to the direct parent, the verification and summary rules of the parent's predecessor are triggered, and it is necessary to summarize and / or verify the parent's parent level layer by layer until there is a filled value on the nearest level, or it is summarized to the root instance. If the actual working hours currently modified are summarized to the parent and exceed the filled value of the actual working hours of the parent's other parents, the modification is unsuccessful.

[0207] Further references Figure 5 As an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of a project management device, and the device embodiment is Figure 1 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0208] like Figure 5 As shown, the project management device of this embodiment includes: a verification unit, for determining whether the target value passes the verification based on the parent item and / or child item of the first item in response to detecting a modification operation of modifying the value of the first item to the target value; an update unit, for updating the parent item value according to the target value that passes the verification in response to the target value passing the verification and in response to the first item having a parent item and the parent item value of the parent item is empty or is a summary value type, wherein the summary value type indicates that the parent item value is obtained by summarizing the values ​​of other items.

[0209] In this embodiment, the specific processing of the verification unit 501 and the updating unit 502 of the project management device and the technical effects thereof can be referred to in Figure 1 The relevant descriptions of step 101 and step 102 in the corresponding embodiment are not repeated here.

[0210] In some embodiments, the device is further configured to: display the target value in response to the target value passing verification.

[0211] In some embodiments, in response to detecting a modification operation to modify the value of the first item to a target value, determining whether the target value passes the verification based on the parent item and / or child item of the first item includes one or more of the following: when the first item has a parent item, in response to the parent item value of the parent item being empty, determining that the target value passes the verification; when the first item has a parent item, in response to the parent item value of the parent item being not empty and being a summary value type, determining that the target value passes the verification; when the first item has a parent item, in response to the parent item value of the parent item being not empty and being a filled-in value type, determining whether the target value is greater than the parent item value; in response to the target value not being greater than the parent item value, determining that the target value passes the verification; when the first item has a parent item, in response to the parent item value of the parent item being not empty and being a filled-in value type, determining whether the time range indicated by the target value is greater than the time range indicated by the parent value; in response to the time range indicated by the target value being not greater than the time range indicated by the parent value, determining that the target value passes the verification.

[0212] In some embodiments, in response to detecting a modification operation to modify the value of the first item to a target value, determining whether the target value passes the verification based on the parent item and / or child item of the first item includes one or more of the following: when the first item has child items, in response to the child item value of the child item being not empty, determining whether the target value is less than the child item value; in response to determining that the target value is not less than the child item value, determining that the target value passes the verification; when the first item has child items, in response to the child item value of the child item being not empty, determining whether the time range indicated by the target value is less than the time range indicated by the child item value; in response to determining that the time range indicated by the target value is not less than the time range indicated by the child item value, determining that the target value passes the verification.

[0213] In some embodiments, the device is further used to: in response to the target value failing verification, display a first prompt message, wherein the first prompt message is used to prompt that the target value conflicts with the parent item and / or the child item.

[0214] In some embodiments, the device is also used to: before the modification operation, display second prompt information for the first item, wherein the second prompt information is used to prompt the value range of the first item, wherein the value range of the first item is generated based on the parent item and / or child item of the first item.

[0215] In some embodiments, the device is also used to: display a third prompt message in response to a trigger operation on a work item value of a summary value type; wherein the third prompt message is used to prompt: if the work item value of the summary value type is modified, the modified work item value constitutes a constraint on the sub-item corresponding to the work item value.

[0216] In some embodiments, in response to detecting a modification operation that modifies the value of a first item to a target value, determining whether the instance to which the first item belongs is a preset constraint type, wherein the preset constraint type includes one or more of the following: sub-process node, node, sub-task, sub-work item; in response to detecting a modification operation that modifies the value of the first item to a target value, determining whether the target value passes verification based on the parent item and / or child item of the first item, includes: based on determining that the instance to which the first item belongs is a preset constraint type, and in response to detecting a modification operation that modifies the value of the first item to a target value, determining whether the target value passes verification based on the parent item and / or child item of the first item; and the device is also used for one or more of the following: configuring the constraint type in the work item management space of the project management system; configuring the constraint type in the schedule interface of the project management system when the first constraint control of the schedule is in the on state.

[0217] In some embodiments, when the first constraint control of the schedule is in the turned-on state, the constraint type is configured in the schedule interface of the project management system, including one or more of the following: configuring the constraint type for multiple work items in the schedule; configuring the constraint type for a single work item in the schedule.

[0218] In some embodiments, the content type of the first item includes one or more of the following: planned schedule, planned duration, estimated score, actual working hours; and

[0219] In some embodiments, the first item is a planned schedule, and the target value is a planned schedule value; and the device is further used to: in response to the planned schedule value passing verification, update the duration value according to the verified planned schedule value.

[0220] In some embodiments, the apparatus is further configured to: in response to deleting the target value, generate a summary value of the first item based on the sub-items of the first item.

[0221] Please refer to Figure 6 , Figure 6 An exemplary system architecture is shown in which the project management method according to one embodiment of the present disclosure can be applied.

[0222] like Figure 6 As shown, the system architecture may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 is used to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. The network 604 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0223] The terminal devices 601, 602, and 603 can interact with the server 605 through the network 604 to receive or send messages, etc. Various client applications, such as web browser applications, search applications, and news information applications, can be installed on the terminal devices 601, 602, and 603. The client applications in the terminal devices 601, 602, and 603 can receive user instructions and perform corresponding functions according to the user instructions, such as adding corresponding information to the information according to the user instructions.

[0224] Terminal devices 601, 602, and 603 can be hardware or software. When terminal devices 601, 602, and 603 are hardware, they can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, Moving Picture Experts Group Audio Layer 3), MP4 (Moving Picture Experts Group Audio Layer IV, Moving Picture Experts Group Audio Layer 4) players, laptop computers, and desktop computers, etc. When terminal devices 601, 602, and 603 are software, they can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules (for example, software or software modules used to provide distributed services), or it can be implemented as a single software or software module. No specific limitation is made here.

[0225] The server 605 may be a server that provides various services, such as receiving information acquisition requests sent by the terminal devices 601, 602, and 603, and acquiring display information corresponding to the information acquisition requests in various ways according to the information acquisition requests. The relevant data of the display information is sent to the terminal devices 601, 602, and 603.

[0226] It should be noted that the project management method provided in the embodiment of the present disclosure can be executed by a terminal device, and accordingly, the project management device can be set in the terminal devices 601, 602, and 603. In addition, the project management method provided in the embodiment of the present disclosure can also be executed by a server 605, and accordingly, the project management device can be set in the server 605.

[0227] It should be understood that Figure 6 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0228] Reference below Figure 7 , which shows an electronic device (eg, Figure 6The terminal device in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0229] like Figure 7 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the electronic device 700 are also stored. The processing device 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0230] Typically, the following devices may be connected to the I / O interface 705: input devices 706 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 707 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 708 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 709. The communication devices 709 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although Figure 7 An electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0231] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 709, or installed from a storage device 708, or installed from a ROM 702. When the computer program is executed by the processing device 701, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

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

[0233] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0234] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0235] The above-mentioned computer-readable medium carries one or more programs. When the above-mentioned one or more programs are executed by the electronic device, the electronic device: in response to detecting a modification operation to modify the value of the first item to the target value, determines whether the target value passes the verification based on the parent item and / or child item of the first item; in response to the target value passing the verification and in response to the first item having a parent item and the parent item value of the parent item is empty or is a summary value type, updates the parent item value according to the target value that passes the verification, wherein the summary value type indicates that the parent item value is obtained by summarizing the values ​​of other items.

[0236] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0237] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0238] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, a verification unit may also be described as a "unit for determining whether the target value passes verification".

[0239] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

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

[0241] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.

[0242] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0243] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

Claims

1. A project management method, the method comprising: In response to detecting a modification operation of modifying the value of the first item to the target value, determining whether the target value passes verification according to a parent item and / or a child item of the first item; In response to the target value passing verification and in response to the first item having a parent item, and the parent item value of the parent item is empty or is a summary value type, the parent item value is updated according to the verified target value, wherein the summary value type indicates that the parent item value is obtained by summarizing the values ​​of other items.

2. The method according to claim 1, characterized in that The method further comprises: In response to the target value passing verification, the target value is displayed.

3. The method according to claim 1, characterized in that In response to detecting a modification operation of modifying the value of the first item to the target value, determining whether the target value passes verification according to the parent item and / or the child item of the first item includes one or more of the following: When the first item has a parent item, in response to a parent item value of the parent item being empty, determining that the target value passes verification; When the first item has a parent item, in response to a parent item value of the parent item being not empty and being a summary value type, determining that the target value passes verification; When the first item has a parent item, in response to a parent item value of the parent item being not empty and being a filled value type, determining whether the target value is greater than the parent item value; In response to the target value not being greater than the parent value, determining that the target value passes verification; When the first item has a parent item, in response to the parent item value of the parent item being not empty and being a filled-in value type, it is determined whether the time range indicated by the target value is greater than the time range indicated by the parent item value; in response to the time range indicated by the target value being not greater than the time range indicated by the parent item value, it is determined that the target value passes the verification.

4. The method according to claim 1, characterized in that: In response to detecting a modification operation of modifying the value of the first item to the target value, determining whether the target value passes verification according to the parent item and / or the child item of the first item includes one or more of the following: When the first item has a sub-item, in response to a sub-item value of the sub-item being not empty, determining whether the target value is less than the sub-item value; In response to determining that the target value is not less than the sub-item value, determining that the target value passes verification; When the first item has a sub-item, in response to the sub-item value of the sub-item being not empty, it is determined whether the time range indicated by the target value is smaller than the time range indicated by the sub-item value; in response to determining that the time range indicated by the target value is not smaller than the time range indicated by the sub-item value, it is determined that the target value passes the verification.

5. The method according to claim 1, characterized in that The method further comprises: In response to the target value failing verification, a first prompt message is displayed, wherein the first prompt message is used to prompt that there is a conflict between the target value and the parent item and / or the child item.

6. The method according to claim 1, characterized in that The method further comprises: Before the modification operation, second prompt information is displayed for the first item, wherein the second prompt information is used to prompt a value range of the first item, wherein the value range of the first item is generated according to a parent item and / or a child item of the first item.

7. The method according to claim 1, characterized in that The method further comprises: In response to a trigger operation on a work item value of a summary value type, displaying third prompt information; The third prompt information is used to prompt that if a work item value of a summary value type is modified, the modified work item value constrains the sub-item corresponding to the work item value.

8. The method according to claim 1, characterized in that The method further comprises: In response to detecting a modification operation to modify the value of the first item to a target value, determining whether the instance to which the first item belongs is a preset constraint type; and In response to detecting a modification operation of modifying the value of the first item to the target value, determining whether the target value passes verification according to the parent item and / or the child item of the first item includes: Based on determining that the instance to which the first item belongs is a preset constraint type, and in response to detecting a modification operation of modifying the value of the first item to a target value, determining whether the target value passes verification according to a parent item and / or a child item of the first item; The preset constraint types include one or more of the following: sub-process node, node, sub-task, sub-work item; and The method may further include one or more of the following: In the work item management space of the project management system, configuring a constraint type; When the first constraint control of the schedule is in an open state, the constraint type is configured in the schedule interface of the project management system.

9. The method according to claim 8, characterized in that When the first constraint control of the schedule is in the open state, the constraint type is configured in the schedule interface of the project management system, including one or more of the following: For multiple work items in the plan table, configure constraint types; For a single work item in the plan, a constraint type is configured.

10. The method according to claim 9, characterized in that The content type of the first item includes one or more of the following: Schedule, planned duration, estimated points, actual working hours.

11. The method according to claim 10, characterized in that The first item is a planned schedule, and the target value is a planned schedule value; as well as The method further comprises: In response to the plan schedule value passing verification, the duration value is updated according to the plan schedule value passing the verification.

12. The method according to claim 1, characterized in that The method further comprises: In response to deleting the target value, a summary value of the first item is generated based on the sub-items of the first item.

13. A project management device, comprising: a verification unit, configured to, in response to detecting a modification operation of modifying the value of a first item to a target value, determine whether the target value passes verification according to a parent item and / or a child item of the first item; An updating unit is used to update the parent item value in response to the target value passing the verification and in response to the first item having a parent item, and the parent item value of the parent item is empty or is a summary value type, according to the target value that passes the verification, wherein the summary value type indicates that the parent item value is obtained by summarizing the values ​​of other items.

14. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 12.

15. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 12 is implemented.

Images