A data processing method, apparatus, device, medium, and product

Abstract

The application discloses a data processing method and device, equipment, medium and product, and relates to the technical field of computers. The method comprises the following steps: when it is detected that a target project is created in working software, obtaining product participant information and demand information of the target project; based on the product participant information and the demand information, automatically creating a project group chat in the working software; when it is detected that a participant corresponding to a project node in the target project is changed, obtaining participant change information of a target participant; if the participant change information is participant increase information, the target participant is added to the project group chat; the target participant comprises a development participant and / or a test participant; change information of the project node of the target project is obtained, and the project group chat is updated according to the change information. Through the technical scheme, the research and development efficiency can be improved and the management cost can be reduced.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a data processing method, apparatus, device, medium, and product. Background Technology

[0002] In the software development process, from requirement identification to final deployment, multiple roles such as product, development, testing, and operations are typically involved, resulting in numerous process nodes and low collaboration efficiency. Although existing project management tools can record process status, each step still relies on manual intervention, notification, and verification, which can easily lead to information delays and process blockages, resulting in low overall development efficiency and high management costs. Summary of the Invention

[0003] This invention provides a data processing method, apparatus, device, medium, and product to solve the problem of low research and development efficiency.

[0004] According to one aspect of the present invention, a data processing method is provided, comprising: When it is detected that the target project has been created in the working software, obtain the product participant information and requirement information of the target project; Based on the product participant information and the demand information, a project group chat is automatically created in the working software; When a change is detected in the participants corresponding to a project node in the target project, the participant change information of the target participant is obtained; If the participant change information is a participant addition, then the target participant will be added to the project group chat; the target participant includes development participants and / or testing participants; Obtain the change information of the project nodes of the target project, and update the project group chat according to the change information.

[0005] According to another aspect of the present invention, a data processing apparatus is provided, comprising: The project data acquisition module is used to acquire the product participant information and requirement information of the target project when it is detected that the target project has been created in the working software; The group chat creation module is used to automatically create project group chats in the working software based on the product participant information and the requirement information. The participant information acquisition module is used to acquire participant change information of the target participant when a change is detected in the participant corresponding to a project node in the target project. The participant update module is used to add the target participant to the project group chat if the participant change information is a participant addition; the target participant includes development participants and / or testing participants; The group chat update module is used to obtain the change information of the project nodes of the target project and update the project group chat according to the change information.

[0006] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data processing method according to any embodiment of the present invention.

[0007] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the data processing method described in any embodiment of the present invention.

[0008] According to another aspect of the present invention, a computer program product is provided, comprising a computer program / instructions that, when executed by a processor, implement the data processing method as described in any embodiment of the present invention.

[0009] This invention deeply integrates project behaviors such as project creation, changes in participants, and changes in project nodes with the creation, member management, and status updates of project group chats. This replaces the traditional manual operation of communication platforms and achieves automated, precise, and real-time linkage management of project collaboration and communication platforms throughout the entire lifecycle of a target project. This significantly improves project collaboration efficiency and management standardization, eliminates information gaps in project collaboration, increases R&D efficiency, and reduces management costs.

[0010] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart of a data processing method provided in an embodiment of the present invention; Figure 2This is a flowchart of another data processing method provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device that implements the data processing method of the present invention. Detailed Implementation

[0013] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0014] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0015] Furthermore, it should be noted that the information collected in the technical solution of this invention is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of related data all comply with the relevant laws, regulations and standards of relevant countries and regions, necessary confidentiality measures have been taken, and public order and good morals are not violated. Corresponding operation entry points are provided for users to choose to authorize or refuse.

[0016] Figure 1 This is a flowchart of a data processing method provided in an embodiment of the present invention. This embodiment is applicable to situations involving full lifecycle management and collaboration of projects. The method can be executed by a data processing device, which can be implemented in hardware and / or software. This device can be configured in an electronic device with corresponding data processing capabilities, such as working software. Figure 1 As shown, the method includes: S110. When it is detected that the target project has been created in the working software, obtain the product participant information and requirement information of the target project.

[0017] The working software refers to the computer program software used to implement the entire lifecycle management of the project. The target project is the project to be managed. Product stakeholder information refers to the relevant information of the product stakeholders. The product stakeholders are the main entities responsible for the product design, development, management, testing, and other work related to the target project. Requirements information refers to the product requirements and specifications in the target project.

[0018] Specifically, through preset monitoring logic, the project creation operation status within the software is monitored in real time. Once a target project's requirements are detected to be created within the software, the system automatically retrieves the product participant information and requirement information bound to that target project. The retrieved requirement information consists of data relevant to the implementation of the target project. This allows for immediate acquisition and matching of relevant information upon completion of the target project's requirements creation, improving information retrieval efficiency. All acquired information is structured data bound to the target project within the software, ensuring accuracy and uniqueness. This reduces the number of steps required from staff within the software, improving its usability and overall project management efficiency.

[0019] S120: Based on product participant information and requirements, automatically create project group chats in the work software.

[0020] Among them, project group chat is an instant messaging group created in the work software based on the target project and used for the target project.

[0021] Specifically, within the software, a pre-defined automated creation logic generates a project group chat corresponding to the target project based on product participant information and requirement information. This automated creation logic includes the group chat creation logic. The group chat creation logic refers to obtaining the product participant information and requirement information for each requirement node after its creation, and then generating the project group chat based on this information. The product participant information and requirement information are the information entered by the user in the input boxes within the node information input area of ​​each requirement node. Product participant information can include the email addresses of product participants. When a user enters product participant information and requirement information in the input box of the node information input area of ​​a requirement node, the system triggers the group chat creation process. Based on the preset mapping relationship between participants (such as their email addresses) and user IDs (Identity), the system obtains the user ID of the product participant. The user ID is used to uniquely identify the participant within the working software. The system then creates a project group chat corresponding to the requirement node of the target project, generates a group chat ID, and binds the target project ID to the group chat ID. Based on the requirement information, the system determines the group chat name. Through the association relationship between the project ID and the group chat ID, the system establishes an association between the user ID of the product participant corresponding to the requirement node of the target project and the group chat ID, thus adding the product participant to the project group chat. For example, if the system detects that the requirement creation of the target project has been completed and obtains the participant (such as Mr. Wang from the product department) and requirement information, it automatically creates a project group chat in the working software and automatically adds Mr. Wang to the group. This project group chat is used for communication and collaboration throughout the entire lifecycle of the target project. This eliminates the need to manually create group chats in the work software, retrieve product participant information one by one, and add group members. It automatically builds project group chats based on product participant and requirement information, improving project collaboration startup efficiency and eliminating the time cost of manual operation. Group chat members are directly determined based on product participant information, avoiding problems such as missing key participants or adding irrelevant personnel when adding them manually. Project group chats are bound to target projects and requirement information, ensuring that each project's collaboration group chat is exclusive and preventing confusion between project group chats and target projects, thus ensuring the basic accuracy of project collaboration. Project group chats are created based on requirement information and directly display the requirement information in the project group chat, ensuring that all participants have a consistent understanding of the project requirements and laying a unified information foundation for subsequent collaboration.

[0022] S130. When a change is detected in the participant corresponding to a project node in the target project, obtain the participant change information of the target participant.

[0023] In this context, a project milestone is a phased work unit within the entire lifecycle of the target project, characterized by clearly defined objectives, deadlines, and responsible parties. Target stakeholders are those involved in the project milestones. Stakeholder change information refers to information regarding changes in stakeholders.

[0024] Specifically, the target project includes at least one project node. The relationship between each project node and the participants in the target project is monitored in real time through a preset monitoring logic. When any change in the relationship between the participants corresponding to any project node is detected, such as the addition, deletion, or replacement, the participant change information of the target participants bound to the project node after the change is automatically retrieved. In this way, by accurately obtaining the participant change information of the target participants, real-time and accurate subject information is provided for subsequent node collaboration and allocation of rights and responsibilities.

[0025] S140. If the participant change information is an addition of participant information, then the target participant will be added to the project group chat; the target participants include development participants and / or testing participants.

[0026] In this context, development participants are the entities responsible for the functional development of the target project. Testing participants are the entities responsible for the functional testing of the target project. Development participants can include front-end development participants and back-end development participants. Testing participants can include front-end testing participants and back-end testing participants. It should be noted that target participants include, but are not limited to, development participants and testing participants, and can be set according to actual needs. If a new project node is added to the target project (such as a project approval node), the corresponding target participants (approval participants) can be flexibly set based on the requirements of the new project node. Participant change information includes participant additions or removals. Participant additions indicate newly added participants to the target project. Participant removals indicate participants leaving the target project.

[0027] Specifically, when the participant information changes after the target project node is changed, the corresponding target participant is automatically added to the project group chat. The target participants are mainly the personnel responsible for project development and / or the personnel responsible for project testing. There is no need to manually add people throughout the process, so that the participants in the project group chat are automatically updated after the project node participants change.

[0028] Optionally, if the change information for a participant is a reduction in the number of participants, the corresponding target participant will be removed from the project group chat.

[0029] Specifically, when the participant change information is a reduction in the number of participants, it means that the target participant has withdrawn from the target project. The corresponding target participant will be removed from the project group chat so that the target participant will no longer receive messages in the project group chat.

[0030] S150. Obtain the change information of the project nodes of the target project, and update the project group chat according to the change information.

[0031] Among them, change information is information that represents changes in the state of project nodes.

[0032] Specifically, it automatically acquires information on changes to project nodes of the target project, and then automatically updates the project group chat accordingly based on the specific changes. The entire process requires no manual viewing of node changes or manual modification of the group chat, achieving automatic synchronization between project node changes and the status of the project group chat, ensuring that the project group chat always matches the latest progress status of the project nodes.

[0033] Optionally, it also includes: periodically checking the requirement information of the target project to obtain project vulnerability information; the project vulnerability information includes the requirement link address, requirement status and the person in charge; and pushing the project vulnerability information to the project group chat.

[0034] Among them, project vulnerability information reflects problems encountered during the implementation of target project requirements. The requirement link address is the access address for the requirement information. The requirement status indicates the processing status of the requirement information.

[0035] Specifically, according to a preset time cycle, all requirement information of the target project is cyclically checked. Through a preset vulnerability identification logic, abnormal data is extracted from the requirement information and integrated into project vulnerability information. The project vulnerability information includes the requirement link address, requirement status, and the person in charge. The structured project vulnerability information is automatically pushed to the target project's group chat. This achieves full-cycle automated monitoring and problem synchronization of the target project's requirement advancement process. The detection results are directly linked with the communication platform, enabling timely discovery, accurate identification, and information synchronization of requirement vulnerabilities.

[0036] This invention deeply integrates project behaviors such as project creation, changes in participants, and changes in project nodes with the creation, member management, and status updates of project group chats. This replaces the traditional manual operation of communication platforms and achieves automated, precise, and real-time linkage management of project collaboration and communication platforms throughout the entire lifecycle of a target project. This significantly improves project collaboration efficiency and management standardization, eliminates information gaps in project collaboration, increases R&D efficiency, and reduces management costs.

[0037] Figure 2 This is a flowchart of another data processing method provided by an embodiment of the present invention. Based on the above embodiments, this embodiment optimizes the process of "obtaining change information of project nodes in the target project and updating the project group chat according to the change information," providing an optional implementation scheme. For example... Figure 2 As shown, the method includes: S210. When it is detected that the target project has been created in the working software, obtain the product participant information and requirement information of the target project.

[0038] S220: Based on product participant information and requirements, automatically create project group chats in the work software.

[0039] S230. When a change is detected in the participant corresponding to a project node in the target project, obtain the participant change information of the target participant.

[0040] S240. If the participant change information is an addition of participant information, then the target participant will be added to the project group chat; the target participants include development participants and / or testing participants.

[0041] S250. Obtain the change information of the project nodes of the target project, and update the project group chat according to the change information.

[0042] Optionally, obtain the change information of the project nodes of the target project, and update the project group chat according to the change information, including: monitoring the project nodes of the target project to obtain the change information of the project nodes; and pushing information and updating the group chat name according to the change information.

[0043] The group chat name includes the request status and the request name.

[0044] Specifically, by monitoring the attributes, relationships, and progress status of project nodes in the target project, when a change is detected, the system automatically collects the change data, performs structured processing, and generates change information for the project node (such as changes in participants, progress, requirements, and deadlines). This change information is then automatically pushed to the project group chat, ensuring synchronization among all group members. Based on the project's progress status or stage characteristics after the node change, the system obtains the requirement status and automatically modifies the project group chat name, making it intuitively reflect the current progress of the target project nodes. This achieves precise linkage between project node changes, group chat status, and group information, ensuring that information transmission and the group chat name always match the latest progress status of the project nodes. For example, the target project's nodes include front-end development nodes and back-end development nodes. The development participants corresponding to the front-end development nodes are the front-end development participants, and the development participants corresponding to the back-end development nodes are the back-end development participants. When the front-end development node is detected as "completed," the system checks whether the back-end development node is also "completed." If so, the subsequent project testing process is triggered; otherwise, it waits for the back-end participants to update the back-end development node's status to "completed." This avoids fragmented testing, reduces redundant regression testing, improves delivery quality, and lowers collaboration costs.

[0045] Optionally, project nodes include requirement review nodes; change information includes requirement review information; correspondingly, obtain the change information of the project nodes of the target project, and update the project group chat according to the change information, including: monitoring the requirement review nodes of the target project to obtain the requirement review status information of the requirement review nodes; determining the organizational structure information based on the development participant information; determining the development department documents based on the organizational structure information; when the requirement review status information is "review completed", creating a technical solution document in the development directory of the development department documents; synchronizing the technical solution document to the project group chat and the target project, and updating the requirement status of the group chat name to "reviewed".

[0046] Among them, the requirements review node is the node where the requirements of the target project are reviewed. Requirements review status information is the status information associated with the requirements review node. Organizational structure information is the structured organizational management data of the teams to which the development participants belong. Development department documents are the development-related documents created by the departments to which the development participants belong in the working software. Technical solution documents are used to characterize the technical content of the target project.

[0047] Specifically, the system monitors the progress and results of the requirements review nodes of the target project in real time. When the status of a requirements review node changes, it automatically obtains the requirements review status information; it retrieves organizational structure information from the development participant information; based on the organizational structure information, it accurately matches and determines the development department document of the department to which the development participant belongs in the working software; when the requirements review status information is "review completed", it creates a technical solution document in the development directory of the development department document; it synchronizes the newly created technical solution document to the target project's project group chat (to achieve sharing among all members in the group) and the target project (to achieve archiving in the project database), so that each participant in the project group chat can edit the technical solution document, and automatically updates the requirements status in the group chat name (such as not reviewed or under review) to "reviewed", so that the group chat name intuitively and accurately reflects the current requirements review stage status of the target project, achieving real-time matching between the project group chat and the project node status.

[0048] Optionally, project nodes include development nodes; change information includes project repository address information; accordingly, obtain the change information of the target project's project nodes, and update the project group chat according to the change information, including: monitoring the development nodes of the target project to obtain the project repository address information of the development nodes; parsing the project repository address information to obtain the first service name, the first project path, and the first branch name and storing them in the database; when receiving a successful environment deployment message from a third-party platform, extracting the second service name, the second project path, and the second branch name from the successful environment deployment message, and matching the second service name, the second project path, and the second branch name with the first service name, the first project path, and the first branch name in the database to obtain the matching result; if the matching result is successful, pushing the first service name, the first project path, and the first branch name to the project group chat, sending test reminders to the test participants in the project group chat, and updating the requirement status of the group chat name to pending testing.

[0049] Here, "Development Node" refers to the node where software development takes place within the target project. "Project Repository Address" is the location where the target project's code is stored. "First Service Name" is the service name obtained by parsing the project repository address. "First Project Path" is the project path obtained by parsing the project repository address. "First Branch Name" is the branch name obtained by parsing the project repository address. "Second Service Name" is the service name obtained by parsing the environment deployment success message. "Second Project Path" is the project path obtained by parsing the environment deployment success message. "Second Branch Name" is the branch name obtained by parsing the environment deployment success message. "Service Name" refers to the name of the specific business service in the target project that has been developed and deployed to the test environment. "Branch Name" is the name of the code branch created for the development of a specific function or version of the target project. "Project Path" is a group directory used for categorizing and hierarchically managing the target project. "Third-Party Platform" is the platform used to deploy the target project's test environment.

[0050] Specifically, the development nodes of the target project are monitored. When the status of a development node is "complete" (e.g., both the front-end and back-end development nodes are complete), the project repository address information entered under the development node is read. The project repository address information is parsed to obtain the first service name, the first project path, and the first branch name, and the corresponding information is stored in the database. Since the target project is published through a third-party platform (e.g., a project publishing platform), when a successful environment deployment message is received from the third-party platform, the second service name, the second project path, and the second branch name are extracted from the successful environment deployment message, and the second service name is stored in the database. The system matches the second project path and the second branch name against the first service name, the first project path, and the first branch name in the database to obtain the matching results. If the matching result is successful, the first service name, the first project path, and the first branch name are automatically pushed to the project group chat, so that all participants in the group, including developers, product managers, and testers, can see the service name, project path, and branch name in real time to achieve information synchronization. At the same time, test reminders are sent to the test participants in the project group chat to remind them to start testing in a timely manner, avoiding the possibility of test participants missing due to too many group messages, ensuring that the testing phase can start in a timely manner, and automatically changing the requirement status in the group chat name to "pending testing" to improve project progress efficiency.

[0051] Optionally, project nodes include project launch nodes; change information includes launch information and rollback information; accordingly, obtain the change information of the project nodes of the target project, and update the project group chat according to the change information, including: monitoring the project launch nodes of the target project, obtaining the launch information and rollback information of the project launch nodes; pushing the launch information and rollback information to the project group chat, and updating the requirement status of the group chat name to "launched".

[0052] The project launch node is the point at which the target project's development is completed and ready for actual operation and service provision to users. Launch information includes front-end launch information and back-end launch information. Front-end launch information includes the front-end access address, etc. Back-end launch information includes the back-end access address, etc. Rollback information includes front-end rollback information and back-end rollback information. Front-end rollback information is front-end data associated with the target project's rollback. Back-end rollback information is back-end data associated with the target project's rollback.

[0053] Specifically, the system monitors the project's deployment milestones in real time (i.e., the final stage of deploying a tested project to the production environment and officially providing services to the public). It collects deployment information, including core data on the successful deployment of the project's front-end and back-end services to the production environment (such as service name, official version, production environment access point, deployment time, and participating parties), as well as rollback information (such as the image address of the stable version before deployment, one-click rollback parameters, and rollback configuration). The collected deployment and rollback information are automatically sent to the project group chat, allowing all participants in the group chat—developers, testers, and product managers—to clearly understand the complete deployment status. The group chat's status is also updated to "Deployed." If problems arise after the target project's deployment, the rollback information from the project group chat can be directly retrieved, eliminating the need for temporary debugging, significantly shortening fault recovery time, and reducing business risks in the production environment.

[0054] Optionally, project nodes include project acceptance nodes; correspondingly, they also include: obtaining the launch time when the requirement status of the group chat name is updated to "online"; determining the acceptance time based on the launch time and delay duration; if the project acceptance node is not completed after the acceptance time arrives, generating an acceptance reminder message and pushing the acceptance reminder message to the project group chat.

[0055] The launch time is the time when the project launch milestone is completed. The delay duration is a pre-set time interval for the target project's acceptance. For example, the delay duration can be thirty minutes. The acceptance time is the time when the project acceptance milestone is announced.

[0056] Specifically, the system automatically extracts the target project's launch time and combines it with a pre-set delay duration to arrive at the acceptance time. If the acceptance time arrives and the project's acceptance work is not yet complete (i.e., an incomplete project acceptance node is detected), an acceptance reminder message is automatically generated and pushed to the project group chat to urge all project participants to complete the acceptance process. This effectively prevents the acceptance phase from being missed or delayed after project launch. For example, the acceptance reminder message could be: "Project launch successful! Developers, please complete the technical health check promptly; testers and product managers, please complete the online acceptance promptly!"

[0057] This invention provides an embodiment of the invention that obtains information on changes in project nodes and updates the project group chat accordingly. This makes the project group chat an intuitive carrier of project progress and node status. All participants in the target project can learn about the latest changes in project nodes in real time through the project group chat, eliminating the need for manual notification and synchronization of project progress. This effectively eliminates information gaps between project participants, significantly improves project communication efficiency, and ensures that all participants carry out subsequent collaborative work based on a unified project schedule.

[0058] Figure 3This is a schematic diagram of a data processing device provided in an embodiment of the present invention. This embodiment is applicable to situations involving full lifecycle management and collaboration of projects. The device can be implemented in hardware and / or software, and can be configured in electronic devices with corresponding data processing capabilities, such as working software. Figure 3 As shown, the device includes: The project data acquisition module 310 is used to acquire the product participant information and requirement information of the target project when it is detected that the target project has been created in the working software. The group chat creation module 320 is used to automatically create project group chats in the working software based on product participant information and requirement information; The participant information acquisition module 330 is used to acquire participant change information of the target participant when a change is detected in the participant corresponding to a project node in the target project. The participant update module 340 is used to add the target participant to the project group chat if the participant information is changed to include new information; the target participants include development participants and / or testing participants. The group chat update module 350 is used to obtain the change information of the project nodes of the target project and update the project group chat according to the change information.

[0059] This invention deeply integrates project behaviors such as project creation, changes in participants, and changes in project nodes with the creation, member management, and status updates of project group chats. This replaces the traditional manual operation of communication platforms and achieves automated, precise, and real-time linkage management of project collaboration and communication platforms throughout the entire lifecycle of a target project. This significantly improves project collaboration efficiency and management standardization, eliminates information gaps in project collaboration, increases R&D efficiency, and reduces management costs.

[0060] Optional, group chat update module 350, including: The change information acquisition unit is used to monitor the project nodes of the target project and obtain change information of the project nodes; The group chat update unit is used to push information and update the group chat name based on changes in information.

[0061] Optionally, project milestones include requirements review milestones; change information includes requirements review information. Correspondingly, the group chat update unit includes: The requirement review information acquisition subunit is used to monitor the requirement review nodes of the target project and obtain the requirement review status information of the requirement review nodes. The organizational structure information determination sub-unit is used to determine organizational structure information based on the information of the development participants; The Development Department Documentation Determination Subunit is used to determine the development department documentation based on organizational structure information. The Technical Solution Document Creation sub-unit is used to create a technical solution document in the development directory of the development department's documents when the requirements review status information is "review completed". The first group chat update subunit is used to synchronize technical solution documents to the project group chat and the target project, and update the requirement status of the group chat name to "reviewed".

[0062] Optionally, project nodes include development nodes; change information includes project repository address information; Correspondingly, the group chat update unit includes: The address information acquisition subunit is used to monitor the development nodes of the target project and obtain the project repository address information of the development nodes. The address information parsing subunit is used to parse the project repository address information to obtain the first service name, the first project path, and the first branch name, and store them in the database; The message extraction subunit is used to extract the second service name, second project path and second branch name from the environment deployment success message sent by the third-party platform when it receives the environment deployment success message, and to match the second service name, second project path and second branch name with the first service name, first project path and first branch name in the database to obtain the matching result; The second group chat update subunit is used to push the first service name, the first project path, and the first branch name to the project group chat if the matching result is successful, send test reminders to the test participants in the project group chat, and update the requirement status of the group chat name to pending test.

[0063] Optionally, project nodes include project launch nodes; change information includes launch information and rollback information. Correspondingly, the group chat update unit includes: The online data acquisition subunit is used to monitor the online nodes of the target project and obtain the online and rollback information of the online nodes. The third group chat update subunit is used to push online and rollback information to the project group chat and update the requirement status of the group chat name to "online".

[0064] Optionally, the device also includes: a vulnerability detection module, used to: periodically detect the requirement information of the target project to obtain project vulnerability information; the project vulnerability information includes the requirement link address, requirement status and handler; and push the project vulnerability information to the project group chat.

[0065] The data processing apparatus provided in the embodiments of the present invention can execute the data processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method.

[0066] According to embodiments of the present invention, the present invention also provides an electronic device, a readable storage medium, and a computer program product.

[0067] Figure 4 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0068] like Figure 4 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0069] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0070] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as data processing methods.

[0071] In some embodiments, the data processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the data processing method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the data processing method by any other suitable means (e.g., by means of firmware).

[0072] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0073] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0075] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0076] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0077] A computing system can include clients and servers. Clients and servers are generally geographically separated and typically interact via communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product within the cloud computing service system to address the shortcomings of traditional physical hosts and virtual private servers, such as high management difficulty and weak business scalability.

[0078] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0079] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A data processing method, characterized in that, The method includes: When it is detected that the target project has been created in the working software, obtain the product participant information and requirement information of the target project; Based on the product participant information and the demand information, a project group chat is automatically created in the working software; When a change is detected in the participants corresponding to a project node in the target project, the participant change information of the target participant is obtained; If the participant change information is a participant addition, then the target participant will be added to the project group chat; the target participant includes development participants and / or testing participants; Obtain the change information of the project nodes of the target project, and update the project group chat according to the change information.

2. The method according to claim 1, characterized in that, The step of obtaining change information of project nodes of the target project and updating the project group chat according to the change information includes: The project nodes of the target project are monitored to obtain the change information of the project nodes; Based on the changes, information is pushed to the project group chat and the group chat name is updated.

3. The method according to claim 1 or 2, characterized in that, The project nodes include requirement review nodes; the change information includes requirement review information. Accordingly, obtaining the change information of the project nodes of the target project and updating the project group chat according to the change information includes: Monitor the requirement review nodes of the target project to obtain the requirement review status information of the requirement review nodes; Based on the information of the development participants, determine the organizational structure information; Based on the organizational structure information, determine the development department documents; When the requirement review status information indicates that the review has been completed, a technical solution document is created in the development directory of the development department's documents. The technical solution document is synchronized to the project group chat and the target project, and the requirement status of the group chat name is updated to "reviewed".

4. The method according to claim 1 or 2, characterized in that, The project nodes include development nodes; the change information includes project repository address information. Accordingly, obtaining the change information of the project nodes of the target project and updating the project group chat according to the change information includes: The development nodes of the target project are monitored to obtain the project repository address information of the development nodes; The project repository address information is parsed to obtain the first service name, the first project path, and the first branch name, which are then stored in the database. When a successful environment deployment message is received from a third-party platform, the second service name, the second project path, and the second branch name are extracted from the successful environment deployment message. The second service name, the second project path, and the second branch name are then matched with the first service name, the first project path, and the first branch name in the database to obtain the matching result. If the matching result is successful, the first service name, the first project path, and the first branch name will be pushed to the project group chat, a test reminder will be sent to the test participants in the project group chat, and the requirement status of the group chat name will be updated to pending test.

5. The method according to claim 1 or 2, characterized in that, The project nodes include project launch nodes; the change information includes launch information and rollback information. Accordingly, obtaining the change information of the project nodes of the target project and updating the project group chat according to the change information includes: The project launch nodes of the target project are monitored to obtain the launch information and rollback information of the project launch nodes; The launch information and rollback information are pushed to the project group chat, and the demand status of the group chat name is updated to "launched".

6. The method according to claim 1, characterized in that, The method further includes: According to a cycle, the requirement information of the target project is repeatedly checked to obtain project vulnerability information; the project vulnerability information includes the requirement link address, requirement status, and the person in charge. The vulnerability information of the project will be pushed to the project group chat.

7. A data processing apparatus, characterized in that, The device includes: The project data acquisition module is used to acquire the product participant information and requirement information of the target project when it is detected that the target project has been created in the working software; The group chat creation module is used to automatically create project group chats in the working software based on the product participant information and the requirement information. The participant information acquisition module is used to acquire participant change information of the target participant when a change is detected in the participant corresponding to a project node in the target project. The participant update module is used to add the target participant to the project group chat if the participant change information is an addition of participant information; the target participant includes development participants and / or testing participants; The group chat update module is used to obtain the change information of the project nodes of the target project and update the project group chat according to the change information.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and a memory communicatively connected to the at least one processor; The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the data processing method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the data processing method according to any one of claims 1-6.

10. A computer program product comprising a computer program that, when executed by a processor, implements the data processing method according to any one of claims 1-6.

Images