Centralized online project management system

Abstract

The invention discloses a centralized online project management system, and relates to the technical field of artificial intelligence, the system comprises a database module, an interface module and an auxiliary module, the auxiliary module is used for determining a plurality of display fields of a corresponding to-be-online project according to an online plan when the online plan is received, and displaying the display fields of the to-be-online project according to the display fields of the to-be-online project. The method comprises the following steps: acquiring a to-be-online project, creating a project group corresponding to the to-be-online project, and then synchronizing online data of the to-be-online project in the project group, the online data being determined according to a plurality of display fields; the database module is used for storing project data of the to-be-online project; and the interface module is used for displaying a plurality of display fields corresponding to the item to be online on at least one deployed platform. Through the system, each to-be-online project can be monitored in time, and the online plan of the to-be-online project is prevented from being influenced.

Description

Technical Field

[0001] The present application relates to the field of artificial intelligence technology, and more specifically, to a centralized online project management system. Background Art

[0002] In current project management, "pending projects" typically refer to features or services that are already under development but not yet officially available to users. To prevent developers from missing out on upcoming features and ensure they can easily track these updates, developers display these pending projects on the project management system's display interface.

[0003] However, the existing project management system only displays the projects to be launched on the display interface. When there are many projects to be launched, there is still a risk of missing the monitoring of the projects to be launched, which affects the launch plan of the projects to be launched. Summary of the Invention

[0004] The present application provides a centralized online project management system to solve the problem of omissions in monitoring of projects to be launched, which affects the launch plan of the projects to be launched.

[0005] In a first aspect, the present application provides a centralized online project management system, the system comprising a database module, an interface module, and an auxiliary module, wherein:

[0006] The auxiliary module is configured to, upon receiving a launch plan, determine a plurality of display fields corresponding to a project to be launched according to the launch plan, create a project group corresponding to the project to be launched, and then synchronize launch data of the project to be launched in the project group, wherein the launch data is determined according to the plurality of display fields;

[0007] The database module is used to store the project data of the project to be launched;

[0008] The interface module is used to display multiple display fields corresponding to the project to be launched on at least one deployed platform.

[0009] In one possible implementation, the auxiliary module includes a conversion component and a synchronization component, wherein:

[0010] The conversion component is configured to obtain, upon receiving the launch plan, launch requirements, projects to be launched, and project data of the projects to be launched, and determine a plurality of display fields according to the launch requirements and the project data;

[0011] The synchronization component is used to determine the users to be notified according to the online requirement, create a project group based on the users to be notified, and then synchronize the online data of the projects to be launched in the project group.

[0012] In a possible implementation, the synchronization component includes a creation unit, specifically configured to:

[0013] Determine whether the project to be launched has any associated projects based on the launch requirements;

[0014] If not, determining the user to be notified corresponding to the project to be launched according to the launch requirement;

[0015] If so, retrieve the project personnel information of the associated project, and determine the user to be notified based on the project personnel information and the online requirements;

[0016] Based on a preset format, obtaining a group name of the project group to be created according to the project data;

[0017] A project group associated with the project to be launched is created according to the user to be notified, and the project group is named according to the group name.

[0018] In a possible implementation, the synchronization component further includes a notification unit, specifically configured to:

[0019] When a synchronization requirement is detected, locating a target project group and a plurality of display fields to be synchronized according to the synchronization requirement;

[0020] Determine the project cycle corresponding to each project node of the to-be-launched project based on the launch requirements or historical launch data of the to-be-launched project corresponding to the target project group;

[0021] According to the multiple display fields, the current project node of the project to be launched is obtained, and the project cycle corresponding to each project node is updated;

[0022] Online data is generated according to the current project node, the updated project cycle corresponding to each project node, and the users to be notified associated with each project node, and the online data is synchronized within the target project group.

[0023] In a possible implementation, the synchronization component further includes an adjustment unit, specifically configured to:

[0024] When receiving a personnel change notification, determine the users to be deleted and the users to be added, as well as the corresponding projects to be launched, according to the personnel change notification;

[0025] Locate the project group corresponding to the project to be launched;

[0026] According to the users to be deleted and the users to be added, a personnel change operation is performed in the project group corresponding to the project to be launched.

[0027] In a possible implementation, the display field includes a project field, a status field, and a time field, and the conversion component includes an extraction unit specifically configured to:

[0028] Acquire the project field according to the project data of the project to be launched;

[0029] Determine the launch time point and the data to be monitored for the project to be launched according to the launch requirements;

[0030] Determine the time field according to the online time point, and determine the status field according to the data to be monitored;

[0031] The time field is used to indicate the time interval from the current time to the online time point, and the status field is used to indicate whether there is any abnormality in the data to be monitored.

[0032] In a possible implementation, the conversion component further includes an updating unit, specifically configured to:

[0033] Determining an update period according to the time field;

[0034] Update the time field according to the update cycle and the online time point;

[0035] updating the data to be monitored according to the update cycle, and updating the status field according to the updated data to be monitored;

[0036] Generate update prompt information based on the updated time field and the updated status field, and send the update prompt information to the interface module so that the interface module displays the updated time field and the updated status field on the display interface of at least one deployed platform.

[0037] In one possible implementation, the interface module includes a display component, wherein:

[0038] When receiving the online plan, adding a new partition to the display interface;

[0039] Locating a target display block for each display field corresponding to the launch plan according to the multiple display blocks included in the new partition and the label corresponding to each display block;

[0040] Displaying corresponding display fields in each target display block to display the to-be-launched projects corresponding to the launch plan on the display interface;

[0041] The display interface includes at least one partition arranged horizontally, and each partition includes multiple display blocks.

[0042] In a possible implementation, the display component includes a confirmation unit, specifically configured to:

[0043] When detecting that a new partition is added to the display interface, obtaining corresponding display parameters according to the time field in the new partition based on pre-stored display rules, and then displaying corresponding multiple display fields in the new partition according to the display parameters;

[0044] When an update indication is detected, determining a first target partition according to the update indication, and updating a time field and a status field in the first target partition according to the update indication;

[0045] The display parameters of the first target partition are updated according to the updated time field, and the corresponding multiple display fields are displayed in the first target partition according to the updated display parameters.

[0046] In a possible implementation, the display component further includes a prompt unit, specifically configured to:

[0047] When it is detected that there is a second target partition with a display parameter change among the multiple partitions displayed on the display interface, determining a to-be-launched project with a notification requirement based on the second target partition, and generating corresponding synchronization prompt information;

[0048] The synchronization prompt information is sent to the auxiliary module, so that the auxiliary module synchronizes the corresponding online data in the project group corresponding to the to-be-launched project with notification requirements.

[0049] This application provides a centralized launch project management system, which includes three modules: a database, an interface, and an auxiliary module. The auxiliary module is responsible for determining the display fields of the projects to be launched based on the launch plan, creating project groups, and synchronizing the launch data within the project groups. The database module is responsible for storing the project data of the projects to be launched, and the interface module displays the display fields corresponding to the projects to be launched on at least one deployed platform. Through this system, each project to be launched can be monitored in a timely manner to avoid affecting the launch plan of the projects to be launched. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0051] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0052] Figure 1 A schematic diagram of the structure of a centralized online project management system provided in an embodiment of the present application Figure 1 ;

[0053] Figure 2 A schematic diagram of the structure of a centralized online project management system provided in an embodiment of the present application Figure 2 ;

[0054] Figure 3 A schematic diagram of the structure of a centralized online project management system provided in an embodiment of the present application Figure 3 ;

[0055] Figure 4 A schematic diagram of the structure of a centralized online project management system provided in an embodiment of the present application Figure 4 ;

[0056] Figure 5 A schematic diagram of the display interface of a centralized online project management system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0057] To make the objectives, technical solutions, and advantages of this application more clear, the technical solutions in this application will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0058] Projects in development are features or services that are currently under development but not yet publicly available. To ensure developers don't miss out on upcoming features and to easily track updates, the project management system displays these projects in its interface. However, when the number of projects in development is large, simply displaying them in the interface can still lead to some projects being overlooked, potentially impacting their launch schedules.

[0059] This application provides a centralized launch project management system, which includes three modules: a database, an interface, and an auxiliary module. The auxiliary module is responsible for determining the display fields of the projects to be launched based on the launch plan, creating project groups, and synchronizing the launch data within the project groups. The database module is responsible for storing the project data of the projects to be launched, and the interface module displays the display fields corresponding to the projects to be launched on at least one deployed platform. Through this system, each project to be launched can be monitored in a timely manner to avoid affecting the launch plan of the projects to be launched.

[0060] Figure 1 A schematic diagram of the structure of a centralized online project management system provided in an embodiment of the present application Figure 1 .like Figure 1 As shown, the centralized online project management system includes a database module, an interface module and an auxiliary module, among which:

[0061] The auxiliary module is configured to, upon receiving a launch plan, determine a plurality of display fields corresponding to a project to be launched according to the launch plan, create a project group corresponding to the project to be launched, and then synchronize launch data of the project to be launched in the project group, wherein the launch data is determined according to the plurality of display fields;

[0062] The database module is used to store the project data of the project to be launched;

[0063] The interface module is used to display multiple display fields corresponding to the project to be launched on at least one deployed platform.

[0064] In this system, the launch plan is used to indicate that a project to be launched needs to be added to the system. Multiple display fields are used for users to identify the project to be launched corresponding to the multiple display fields and indicate the launch data of the project to be launched.

[0065] Considering that when the system displays a small number of pending launch projects on the display interface, users can promptly monitor the launch data of each pending launch project. However, when the number of pending launch projects displayed is large, it is difficult for users to manually monitor the launch data of each pending launch project, and there may be a risk of omissions. Therefore, this embodiment uses an auxiliary module to create a project group corresponding to each pending launch project, and synchronizes the launch data of the corresponding pending launch project within the project group to ensure that each pending launch project is monitored promptly to avoid affecting the launch plan.

[0066] Specifically, when the auxiliary module in the system receives the launch plan, it determines the projects to be launched that need to be added to the system based on the launch plan, and obtains multiple display fields for the projects to be launched according to the launch plan. The number and type of display fields are preset. Afterwards, a project group corresponding to the project to be launched is created. The project group contains at least one user to be notified. The user to be notified is the initiator or related user of the project to be launched. The user to be notified is determined according to the launch plan. At the same time, the project group must also include a machine user for synchronizing information. The machine user can be a virtual user in the artificial intelligence area or a real user operated by a real person. After the corresponding project group is created, when the machine user receives a synchronization instruction, the corresponding online data is synchronized in the project group corresponding to the synchronization instruction, so that the users to be notified in the project group can understand the launch status of the corresponding project to be launched.

[0067] To ensure that the pending projects are launched according to the launch plan, they must be in a ready-to-go state and must be continuously monitored before launch. Therefore, upon receiving the launch plan, the auxiliary module determines the initial display fields for the corresponding pending projects. Subsequently, some of these fields must be updated. The display fields that require updating, and how to update them, will be described in subsequent examples.

[0068] It should be noted that the user of this embodiment and subsequent embodiments may be a developer or a person related to a project to be launched. The specific person corresponding to the user is determined according to the actual application scenario.

[0069] Furthermore, the database module is used to centrally store the project data of the projects to be launched displayed in the system to avoid the project data of the projects to be launched being scattered in different storage systems or recorded by corresponding related users, resulting in inconsistent or lost project data.

[0070] In the interface module, prompt information containing multiple display fields transmitted by the auxiliary module is received, and based on the prompt information, the multiple display fields are displayed on the display interface of at least one deployed platform. This embodiment does not impose any restrictions on how the interface module displays the projects to be launched on the display interface.

[0071] In a possible implementation, the interface module may determine display parameters based on the field indicating time among the multiple display fields, and display the multiple fields on the display interface according to the determined display parameters, that is, display the corresponding items to be launched.

[0072] For example, the time field is used to indicate the time interval between the current time and the launch time of the corresponding project to be launched, and the display parameter is the sorting position. The shorter the time interval, the higher the corresponding sorting position.

[0073] This application provides a centralized launch project management system, which includes three modules: a database, an interface, and an auxiliary module. The auxiliary module is responsible for determining the display fields of the projects to be launched based on the launch plan, creating project groups, and synchronizing the launch data within the project groups. The database module is responsible for storing the project data of the projects to be launched, and the interface module displays the display fields corresponding to the projects to be launched on at least one deployed platform. Through this system, each project to be launched can be monitored in a timely manner to avoid affecting the launch plan of the projects to be launched.

[0074] Figure 2 A schematic diagram of the structure of a centralized online project management system provided in an embodiment of the present application Figure 2 This embodiment provides a detailed description of the structure of the auxiliary module and the synchronization components included in the auxiliary module. Figure 2As shown, the auxiliary module includes a conversion component and a synchronization component, wherein:

[0075] The conversion component is configured to obtain, upon receiving the launch plan, launch requirements, projects to be launched, and project data of the projects to be launched, and determine a plurality of display fields according to the launch requirements and the project data;

[0076] The synchronization component is used to determine the users to be notified according to the online requirement, create a project group based on the users to be notified, and then synchronize the online data of the projects to be launched in the project group.

[0077] In this system, the auxiliary module is used to convert the received online plan into multiple display fields displayed on the display interface later, and create a project group of projects to be launched based on the online plan, and synchronize the online data of the projects to be launched within the project group. The online data is determined based on the multiple display fields currently displayed on the display interface of the projects to be launched.

[0078] Specifically, the auxiliary module includes a conversion component and a synchronization component. Upon receiving a launch plan, the conversion component retrieves the launch requirements and the project to be launched based on the launch plan. Furthermore, it retrieves the corresponding project data from the database module based on the project to be launched. For example, the launch requirements include the launch time, the associated users corresponding to the project to be launched, and other information. The launch requirements and corresponding project data for the project to be launched are analyzed to obtain multiple display fields for the project to be launched. Simultaneously, the synchronization component determines the users to be notified corresponding to the project to be launched based on the launch requirements, creates a project group containing the users to be notified, and then synchronizes the launch data of the project to be launched within the project group.

[0079] Furthermore, the project group is designed so that users to be notified can directly view changes in the online data of the projects to be launched within the group, such as changes in the time interval from the launch time. At the same time, when the project group is just created, it is also necessary to notify the internal users to be notified within the project group and inform them of the current online data. Therefore, when the synchronization component determines that there is a synchronization requirement, it will synchronize the online data of the corresponding project to be launched at the current time within the project group corresponding to the synchronization requirement. The synchronization requirement includes a synchronization indication and multiple display fields of the project to be launched corresponding to the current time. The synchronization indication is sent to the synchronization component by the conversion component when it obtains the multiple display fields of the project to be launched according to the corresponding launch plan, or it is sent by the interface module when it determines that the display parameters corresponding to the project to be launched have changed.

[0080] Therefore, the synchronization component first creates a project group corresponding to the project to be launched, and then synchronizes the online data when a synchronization requirement is detected.

[0081] If a project to be launched is too large or has a long launch cycle, it will be divided into multiple phases. Projects from different phases are related to each other. Because these phases are strongly related, when building a project group for one of these projects, you need to determine whether to include users from the related project in the project group. Therefore, when building a project group for a project to be launched, you need to determine whether there are any related projects and, based on the determination, retrieve the users to be notified.

[0082] The process of building a project group is:

[0083] The creation unit of the synchronization component determines whether the project to be launched has an associated project according to the launch requirement;

[0084] If not, determining the user to be notified corresponding to the project to be launched according to the launch requirement;

[0085] If so, retrieve the project personnel information of the associated project, and determine the user to be notified based on the project personnel information and the online requirements;

[0086] Based on a preset format, obtaining a group name of the project group to be created according to the project data;

[0087] A project group associated with the project to be launched is created according to the user to be notified, and the project group is named according to the group name.

[0088] For example, the group name may include the project name and project version.

[0089] Furthermore, a project to be launched typically includes multiple project nodes, with different nodes corresponding to different responsible persons and different cycles. Therefore, in order to ensure that users waiting to be notified within the project group can clearly and quickly view the launch data they want to know, the launch data will be synchronized based on the project node. At the same time, due to the uncontrollable nature of the execution process of the project to be launched, there is a possibility that a project node will be completed early or delayed. Therefore, it is necessary to adjust the project cycle of each project node accordingly. Therefore, the specific steps for synchronizing launch data within the project group are as follows:

[0090] When a synchronization requirement is detected, the notification unit of the synchronization component locates the target project group and the plurality of display fields to be synchronized according to the synchronization requirement;

[0091] Determine the project cycle corresponding to each project node of the to-be-launched project based on the launch requirements or historical launch data of the to-be-launched project corresponding to the target project group;

[0092] According to the multiple display fields, the current project node of the project to be launched is obtained, and the project cycle corresponding to each project node is updated;

[0093] Online data is generated according to the current project node, the updated project cycle corresponding to each project node, and the users to be notified associated with each project node, and the online data is synchronized within the target project group.

[0094] At the same time, considering the variability of project personnel for the project to be launched, that is, the users to be notified of the project to be launched need to be changed. Therefore, the synchronization component is further provided with an adjustment unit, which is specifically used to:

[0095] When receiving a personnel change notification, determine the users to be deleted and the users to be added, as well as the corresponding projects to be launched, according to the personnel change notification;

[0096] Locate the project group corresponding to the project to be launched;

[0097] According to the users to be deleted and the users to be added, a personnel change operation is performed in the project group corresponding to the project to be launched.

[0098] This application provides a centralized launch project management system. The auxiliary module integrates a conversion component and a synchronization component. The conversion component is responsible for processing the launch plan, extracting necessary information, and determining the multiple display fields of the projects to be launched. The synchronization component is responsible for identifying users to be notified and establishing project groups for them, while also synchronizing the launch data of the projects to be launched. Through this system, users can be informed of changes in the launch status of the projects to be launched without interrupting them with excessive synchronization, thereby improving the intelligence of monitoring the projects to be launched.

[0099] Figure 3 A schematic diagram of the structure of a centralized online project management system provided in an embodiment of the present application Figure 3 This embodiment describes in detail the structure of the conversion component included in the auxiliary module. The display field includes the project field, the status field and the time field. Figure 3 As shown:

[0100] The conversion component of this system is used to obtain multiple display fields of the corresponding project to be launched according to the launch plan upon receiving the launch plan. At the same time, the multiple display fields of the project to be launched need to be updated regularly so that users can understand the changes in the launch status of the project to be launched and ensure the smooth launch of the project to be launched. Therefore, the conversion component needs to include a unit for extracting the multiple display fields of the project to be launched according to the launch plan, and a unit for updating the multiple display fields extracted by the aforementioned unit. Specifically:

[0101] The transformation component includes an extraction unit, which is specifically used to:

[0102] Acquire the project field according to the project data of the project to be launched;

[0103] Determine the launch time point and the data to be monitored for the project to be launched according to the launch requirements;

[0104] Determine the time field according to the online time point, and determine the status field according to the data to be monitored;

[0105] The time field is used to indicate the time interval from the current time to the online time point, and the status field is used to indicate whether there is any abnormality in the data to be monitored.

[0106] The transformation component also includes an update unit, which is used to:

[0107] Determining an update period according to the time field;

[0108] Update the time field according to the update cycle and the online time point;

[0109] updating the data to be monitored according to the update cycle, and updating the status field according to the updated data to be monitored;

[0110] Generate update prompt information based on the updated time field and the updated status field, and send the update prompt information to the interface module so that the interface module displays the updated time field and the updated status field on the display interface of at least one deployed platform.

[0111] The project field is used by users to identify the corresponding project to be launched. Considering that there may be multiple versions of the same project, in order to facilitate accurate identification by users, the project field may contain the name and version of the project to be launched. For example: Project Field 1 is a group chat project that is launched without forwarding, and Project Field 2 is version 2.0. The time field is used to indicate the time interval from the current time to the launch time point of the project to be launched. This time interval can be used to inform users how long it will take for the corresponding project to be launched to be launched. At the same time, it can also be used to determine the update cycle in the update module. The status field is used to indicate whether the project to be launched is in an online state at the current time. When the status field indicates that the project to be launched is in an unavailable state at the current time, an abnormal prompt message needs to be sent to prompt the user to check the abnormality of the project to be launched. The data to be monitored used to determine the status field is determined according to the online requirements. This embodiment does not impose any restrictions on the specific parameters included in the data to be monitored.

[0112] Furthermore, when a project is typically launched, it is typically added to the system for management about seven days in advance. Frequently updating the displayed fields increases the system's workload. Similarly, updating a time field from 5 days, 3 hours, and 20 minutes to 5 days, 3 hours, and 15 minutes doesn't significantly help users understand changes in the launch data for the project to be launched. Furthermore, the likelihood of the launch status of the project to be launched changing during this time period is low. Therefore, the update period in this embodiment is positively correlated with the time interval indicated by the time field. In other words, the longer the time interval indicated by the time field, the longer the corresponding update period.

[0113] Specifically, after the extraction unit determines the time field, the update unit determines the corresponding update cycle based on the time interval range to which the time interval corresponding to the time field belongs. For example, if the time interval is 5 days and 3 hours, the corresponding update cycle is once every 6 hours; if the time interval is 2 days and 3 hours, the corresponding update cycle is once every 4 hours. The update unit then updates the time field and status field based on the obtained update cycle, generates update prompt information based on the updated time field and updated status field, and sends the update prompt information to the interface module, so that the interface module displays the updated time field and updated status field.

[0114] It should be noted that, except for the update period of the first update operation which is determined according to the time interval corresponding to the time field obtained by the extraction unit, the update periods corresponding to subsequent update operations are all determined according to the updated time field obtained in the previous update operation.

[0115] The present application provides a centralized online project management system. Upon receiving an online plan, the extraction unit included in the conversion component extracts multiple display fields corresponding to the project to be launched according to the online plan and displays them through the interface module. At the same time, the update unit included in the conversion component determines the update cycle based on the time field, and updates the time field and status field according to the update cycle. Afterwards, update prompt information containing the updated display fields is sent to the interface module. Through the above system, potential problems and risks of the project to be launched can be discovered in a timely manner while simplifying the system operation process, and timely troubleshooting measures can be taken.

[0116] Figure 4 A schematic diagram of the structure of a centralized online project management system provided in an embodiment of the present application Figure 4 This embodiment describes the structure of the interface module in detail. Figure 4 As shown:

[0117] The display interface is divided into multiple horizontal partitions, equal to the number of projects currently available for launch. Each partition contains multiple display blocks, each labeled to match the corresponding display field. The number of display blocks in each partition is fixed, pre-set by the developer, and equal to the number of display fields.

[0118] Therefore, when the interface module determines that a new launch plan needs to be added, it is necessary to give priority to adding a new partition to the display interface. The implementation method is as follows:

[0119] The interface module contains display components, including:

[0120] When receiving the online plan, adding a new partition to the display interface;

[0121] Locating a target display block for each display field corresponding to the launch plan according to the multiple display blocks included in the new partition and the label corresponding to each display block;

[0122] Displaying corresponding display fields in each target display block to display the to-be-launched projects corresponding to the launch plan on the display interface;

[0123] The display interface includes at least one partition arranged horizontally, and each partition includes multiple display blocks.

[0124] like Figure 5 As shown, it is a schematic diagram of the display interface of a centralized online project management system provided by an embodiment of the present application. Figure 5 As shown, the display interface contains 4 partitions, that is, 4 projects to be launched are displayed on the display interface. On the far left of the display interface is the serial number indicating the sequence of the projects to be launched. The serial number is determined according to the time when the launch plan corresponding to each partition is received. The earlier the reception time, the smaller the corresponding serial number. As shown in partition 1, each partition contains 4 display blocks, which display project field 1, project field 2, time field and status field from left to right. Project field 1 is used to indicate the name of the project to be launched displayed in this partition, and project field 2 is used to indicate the version number of the project to be launched displayed in this partition.

[0125] Furthermore, when the display interface displays a large number of projects to be launched, in order to facilitate users to quickly locate the target project to be launched among multiple projects to be launched, this embodiment determines the display parameters of each partition according to preset display rules.

[0126] It should be noted that when a new item to be displayed online is added to the display interface, that is, when a new partition is added to the display interface, it is necessary to determine the corresponding display parameters based on the time field in the new partition, and display the new partition according to the display parameters. Furthermore, when the display component detects an update indication, it updates the time field and status field of the corresponding first target partition according to the update indication, and updates the display of the first target partition according to the updated time field. The update indication comes from the update prompt information of the aforementioned update unit. The specific implementation process is:

[0127] The display component includes a confirmation unit, which is used to:

[0128] When detecting that a new partition is added to the display interface, obtaining corresponding display parameters according to the time field in the new partition based on pre-stored display rules, and then displaying corresponding multiple display fields in the new partition according to the display parameters;

[0129] When an update indication is detected, determining a first target partition according to the update indication, and updating a time field and a status field in the first target partition according to the update indication;

[0130] The display parameters of the first target partition are updated according to the updated time field, and the corresponding multiple display fields are displayed in the first target partition according to the updated display parameters.

[0131] Because the time field corresponding to the pending project is updated multiple times daily—for example, from 5 days and 12 hours to 5 days—the time interval between the pending project's launch and the launch time is relatively long. If each time field change corresponds to a different display parameter, it would interfere with the user's ability to monitor the launch data of the pending project. Therefore, this embodiment updates the display parameters based on the updated time field, potentially obtaining new display parameters or the original display parameters.

[0132] Furthermore, when there is a partition with display parameter changes, in order to promptly inform the corresponding users to be notified of the project to be launched, it is necessary to send a synchronization prompt message to the aforementioned notification unit. The specific implementation process is as follows:

[0133] The display component also includes a prompt unit, which is used to:

[0134] When it is detected that there is a second target partition with a display parameter change among the multiple partitions displayed on the display interface, determining a to-be-launched project with a notification requirement based on the second target partition, and generating corresponding synchronization prompt information;

[0135] The synchronization prompt information is sent to the auxiliary module, so that the auxiliary module synchronizes the corresponding online data in the project group corresponding to the to-be-launched project with notification requirements.

[0136] The present application provides a centralized online project management system, in which the interface module includes a display component. When receiving an online plan, the display component adds a new partition and displays multiple display fields of the corresponding project to be launched in the new partition. When adding a new partition and receiving an update indication, the confirmation unit included in the display component determines the display parameters according to the time field or the updated time field, and displays them in the corresponding partition according to the display parameters. When the prompt unit included in the display component determines that there is a partition with a display parameter change, it sends a synchronization prompt message to the auxiliary module to synchronize the current online data in the corresponding project group. Through the above system, it is convenient to track and monitor the projects to be launched, and improve management efficiency.

[0137] In the above embodiments, the description of each embodiment has its own focus. For parts not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0138] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of the present application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0139] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A centralized online project management system, characterized by: The system comprises a database module, an interface module and an auxiliary module, wherein: The auxiliary module is configured to, upon receiving a launch plan, determine a plurality of display fields corresponding to a project to be launched according to the launch plan, create a project group corresponding to the project to be launched, and then synchronize launch data of the project to be launched in the project group, wherein the launch data is determined according to the plurality of display fields; The database module is used to store the project data of the project to be launched; The interface module is used to display multiple display fields corresponding to the project to be launched on at least one deployed platform.

2. The system according to claim 1, wherein: The auxiliary module includes a conversion component and a synchronization component, wherein: The conversion component is configured to obtain, upon receiving the launch plan, launch requirements, projects to be launched, and project data of the projects to be launched, and determine a plurality of display fields according to the launch requirements and the project data; The synchronization component is used to determine the users to be notified according to the online requirement, create a project group based on the users to be notified, and then synchronize the online data of the projects to be launched in the project group.

3. The system according to claim 2, characterized in that The synchronization component includes a creation unit, which is specifically used to: Determine whether the project to be launched has any associated projects based on the launch requirements; If not, determining the user to be notified corresponding to the project to be launched according to the launch requirement; If so, retrieve the project personnel information of the associated project, and determine the user to be notified based on the project personnel information and the online requirements; Based on a preset format, obtaining a group name of the project group to be created according to the project data; A project group associated with the project to be launched is created according to the user to be notified, and the project group is named according to the group name.

4. The system according to claim 3, characterized in that The synchronization component further includes a notification unit, which is specifically used to: When a synchronization requirement is detected, locating a target project group and a plurality of display fields to be synchronized according to the synchronization requirement; Determine the project cycle corresponding to each project node of the to-be-launched project based on the launch requirements or historical launch data of the to-be-launched project corresponding to the target project group; According to the multiple display fields, the current project node of the project to be launched is obtained, and the project cycle corresponding to each project node is updated; Online data is generated according to the current project node, the updated project cycle corresponding to each project node, and the users to be notified associated with each project node, and the online data is synchronized within the target project group.

5. The system according to claim 4, characterized in that The synchronization component further includes an adjustment unit, which is specifically configured to: When receiving a personnel change notification, determine the users to be deleted and the users to be added, as well as the corresponding projects to be launched, according to the personnel change notification; Locate the project group corresponding to the project to be launched; According to the users to be deleted and the users to be added, a personnel change operation is performed in the project group corresponding to the project to be launched.

6. The system according to claim 2, wherein: The display fields include a project field, a status field, and a time field, and the conversion component includes an extraction unit specifically configured to: Acquire the project field according to the project data of the project to be launched; Determine the launch time point and the data to be monitored for the project to be launched according to the launch requirements; Determine the time field according to the online time point, and determine the status field according to the data to be monitored; The time field is used to indicate the time interval from the current time to the online time point, and the status field is used to indicate whether there is any abnormality in the data to be monitored.

7. The system according to claim 6, characterized in that The conversion component further includes an update unit, which is specifically used to: Determining an update period according to the time field; Update the time field according to the update cycle and the online time point; updating the data to be monitored according to the update cycle, and updating the status field according to the updated data to be monitored; Generate update prompt information based on the updated time field and the updated status field, and send the update prompt information to the interface module so that the interface module displays the updated time field and the updated status field on the display interface of at least one deployed platform.

8. The system according to any one of claims 6 to 7, characterized in that: The interface module includes a display component, wherein: When receiving the online plan, adding a new partition to the display interface; Locating a target display block for each display field corresponding to the launch plan according to the multiple display blocks included in the new partition and the label corresponding to each display block; Displaying corresponding display fields in each target display block to display the to-be-launched projects corresponding to the launch plan on the display interface; The display interface includes at least one partition arranged horizontally, and each partition includes multiple display blocks.

9. The system according to claim 8, characterized in that The display component includes a confirmation unit, which is specifically used to: When detecting that a new partition is added to the display interface, obtaining corresponding display parameters according to the time field in the new partition based on pre-stored display rules, and then displaying corresponding multiple display fields in the new partition according to the display parameters; When an update indication is detected, determining a first target partition according to the update indication, and updating a time field and a status field in the first target partition according to the update indication; The display parameters of the first target partition are updated according to the updated time field, and the corresponding multiple display fields are displayed in the first target partition according to the updated display parameters.

10. The system according to claim 9, characterized in that The display component further includes a prompt unit, which is specifically used to: When it is detected that there is a second target partition with a display parameter change among the multiple partitions displayed on the display interface, determining a to-be-launched project with a notification requirement based on the second target partition, and generating corresponding synchronization prompt information; The synchronization prompt information is sent to the auxiliary module, so that the auxiliary module synchronizes the corresponding online data in the project group corresponding to the to-be-launched project with notification requirements.

Images