API-based task progress monitoring method, device, equipment, and medium

Abstract

The present application discloses a method, device, equipment, and medium for task progress monitoring based on an API, the method comprising: displaying multiple first fields and multiple second fields in a first request interface of a user terminal, the user terminal obtaining multiple first target fields selected by the user from the multiple first fields and multiple second fields, generating a first task progress monitoring request based on the user account and the first target field, and sending the request to a server; the server calls an API interface to parse the first task progress monitoring request, determines the first target progress information from a first database based on the parsing result, calls the API interface again to encapsulate the first target progress information into a first response, and sends the first response to the user terminal. The present application enables developers corresponding to user accounts to flexibly configure task progress monitoring requests on demand in user terminals, and achieves flexibility in task progress monitoring compared to a solution that is limited to sending requests based on a fixed task progress request template.

Description

Technical Field

[0001] The present application relates to, but is not limited to, the field of computer technology, and in particular to an API-based task progress monitoring method, device, equipment, and medium. Background Art

[0002] During the development of a software project, task management and task progress monitoring of each development task in the software project are key factors in ensuring that the software project is delivered on time. With the popularity of development models such as agile development and continuous integration, it is necessary to track the progress and status of development tasks in real time in order to quickly respond to changes in software projects. After the development tasks in the software project are assigned to developers, the existing task monitoring system can only obtain the fixed task progress parameter combination of the task execution terminal corresponding to each developer according to the task progress request template configured on the server, such as task completion amount, task execution status, etc. It is impossible to obtain additional task progress parameter combinations according to the needs of different roles (developers or administrators). The flexibility of the task monitoring system is low, which requires developers or administrators to spend more time and energy to manually filter the target task progress information, affecting the efficiency of task progress monitoring. Summary of the invention

[0003] The embodiments of the present application provide an API-based task progress monitoring method, apparatus, device, and medium, which can flexibly configure task progress data requests and improve task monitoring efficiency.

[0004] In a first aspect, an embodiment of the present application provides an API-based task progress monitoring method, which is applied to a task monitoring system, wherein the task monitoring system includes a server and a user terminal, wherein the server is preset with an API interface, and the user terminal is connected to the server in communication, and the method includes:

[0005] Displaying a plurality of first fields and a plurality of second fields in a first request interface of a user terminal, wherein the user terminal obtains a plurality of first target fields selected by a user from the plurality of first fields and the plurality of second fields, wherein different first fields are used to indicate different task progress indicator types, and different second fields are used to indicate different task identifiers;

[0006] The user terminal generates a first task progress monitoring request based on a user account and all of the first target fields, and sends the first task progress monitoring request to the server, wherein the user account is an account for logging into the user terminal;

[0007] The server calls the API interface to parse the first task progress monitoring request to obtain the user account and the first target field, and determines the corresponding first target progress information from a preset first database based on the user account and the first target field;

[0008] The server calls the API interface to encapsulate the first target progress information into a first response, and sends the first response to the user terminal.

[0009] In some embodiments, the first target field includes at least one first subfield and a second subfield, the first subfield belongs to the first field, and the second subfield belongs to the second field, and the server determines the first target progress information corresponding to all the first target fields from a preset first database, including:

[0010] Determine the first role authority corresponding to the user account;

[0011] Determine a first task progress indicator type set and a first task identifier set corresponding to the first role authority from a preset role authority mapping table, wherein the role authority mapping table is used to indicate a mapping relationship between each first role authority and a task progress indicator type and a task identifier;

[0012] When the first subfield belongs to the first task progress indicator type set, and the second subfield belongs to the first task identifier set, the corresponding first target progress information is obtained from the first database based on the first subfield and the second subfield.

[0013] In some embodiments, the user account is associated with a first reference task identifier, the first reference task identifier is used to indicate a task identifier of a development task currently executed by a user terminal corresponding to the user account, and the server determines the corresponding first target progress information from a preset first database based on the user account and the first target field, including:

[0014] In the case where the second subfield does not belong to the first task identifier set, the server determines whether there is a task dependency relationship between the second subfield and the first reference task identifier; when there is a task dependency relationship between the second subfield and the first reference task identifier, the first role authority is promoted to obtain the second role authority; when the first subfield belongs to the second task progress indicator type set corresponding to the second role authority, the corresponding first target progress information is obtained from the first database based on the first subfield and the second subfield; when there is no task dependency relationship between the second subfield and the first reference task identifier, the server calls the API interface to send a request failure message to the corresponding user terminal, wherein the second subfield is included in the second task identifier set associated with the second role authority;

[0015] In the case that the second subfield belongs to the first task identification set, the server determines whether all the first subfields belong to the first task progress indicator type set, obtains a judgment result, and obtains the corresponding first target progress information from the first database based on the judgment result, all the first subfields and the second subfield.

[0016] In some embodiments, after the server calls the API interface to parse the first task progress monitoring request to obtain the first target field, the method further includes:

[0017] When the server cannot identify the task identifier corresponding to any one of the second subfields in the first target field in the first database, calling the API interface to encapsulate all the second reference task identifiers in the first database into a second response, and sending the second response to the user terminal;

[0018] The user terminal acquires all the second reference task identifiers from the second response, and updates the second field of the first request interface based on all the second reference task identifiers;

[0019] The user terminal obtains multiple second target fields selected by the user from the multiple first fields and the multiple updated second fields, generates a second task progress monitoring request based on the user account and all the second target fields, and sends the second task progress monitoring request to the server.

[0020] In some embodiments, the user terminal generates a first task progress monitoring request based on all of the first target fields, including:

[0021] Determine the first role authority corresponding to the user account;

[0022] Determine a sensitive data inclusion flag based on the first role authority, wherein the sensitive data inclusion flag is used to indicate whether sensitive data is included in the response corresponding to the first task progress monitoring request;

[0023] Encapsulate all of the first target fields and the sensitive data flag to generate the first task progress monitoring request.

[0024] In some embodiments, after the server sends the first response to the user terminal, the method further includes:

[0025] The user terminal calls the ensemble learning algorithm encapsulated in the ensemble learning class to perform data anomaly detection on each progress sample data in the first target progress information, and obtains anomaly labels for each progress sample data, wherein the anomaly label with a value of 1 indicates that the progress sample data has no anomaly, and the anomaly label with a value of -1 indicates that the progress sample data has an anomaly;

[0026] Generate warning information based on the progress sample data corresponding to the abnormal label with a value of -1;

[0027] The warning information is sent to the server.

[0028] In some embodiments, the number of the second subfields is multiple, the first target progress information includes sub-progress information corresponding to each of the second subfields, and after the server calls the API interface to send the first response to the user terminal, the method further includes:

[0029] The user terminal configures a target priority for each task identifier corresponding to each second subfield based on each sub-progress information;

[0030] The user terminal adjusts the progress monitoring request frequency of each task identifier corresponding to the second subfield based on each of the target priorities and a preset priority threshold, wherein a higher level of the target priority corresponds to a higher progress monitoring request frequency;

[0031] The user terminal sends a third task progress monitoring request associated with each of the second subfields to the server based on each of the progress monitoring request frequencies.

[0032] In a second aspect, an embodiment of the present application provides a control device, comprising at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to execute the API-based task progress monitoring method as described in the first aspect.

[0033] In a third aspect, an embodiment of the present application further provides an electronic device, comprising the control device of the second aspect.

[0034] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the API-based task progress monitoring method as described in the first aspect.

[0035] An embodiment of the present application provides an API-based task progress monitoring method, apparatus, device, and medium, the method comprising displaying multiple first fields and multiple second fields in a first request interface of a user terminal, the user terminal obtaining multiple first target fields selected by the user from the multiple first fields and multiple second fields, wherein different first fields are used to indicate different task progress indicator types, and different second fields are used to indicate different task identifiers; the user terminal generates a first task progress monitoring request based on a user account and all of the first target fields, and sends the first task progress monitoring request to the server, wherein the user account is an account for logging into the user terminal; the server calls the API interface to parse the first task progress monitoring request to obtain the user account and the first target field, and determines the corresponding first target progress information from a preset first database based on the user account and the first target field; the server calls the API interface to encapsulate the first target progress information into a first response, and sends the first response to the user terminal. According to the solution provided in the embodiment of the present application, the developer corresponding to each first user account can flexibly configure the corresponding task progress information request on demand in the first monitoring request interface of the user terminal to obtain target progress information. Compared with the solution of only sending task progress monitoring requests according to a configured fixed task progress request template, it is possible to flexibly configure task progress monitoring requests and avoid spending time screening target information from fixed-form task progress information, thereby improving task monitoring efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 This is a flowchart of a method for monitoring task progress based on an API provided by an embodiment of the present application;

[0037] Figure 2 is a schematic diagram of a task progress monitoring method provided by another embodiment of the present application;

[0038] Figure 3 It is a structural diagram of a control device provided in another embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0040] It is understood that although the functional modules are divided in the device schematic diagram and the logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flow chart. The terms "first", "second", etc. in the specification, claims or the above drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0041] During the development of a software project, task management and task progress monitoring of each development task in the software project are key factors in ensuring that the software project is delivered on time. With the popularity of development models such as agile development and continuous integration, it is necessary to track the progress and status of development tasks in real time in order to quickly respond to changes in software projects. After the development tasks in the software project are assigned to developers, the existing task monitoring system can only obtain the fixed task progress parameter combination of the task execution terminal corresponding to each developer according to the task progress request template configured on the server, such as task completion amount, task execution status, etc. It is impossible to obtain additional task progress parameter combinations according to the needs of different roles (developers or administrators). The flexibility of the task monitoring system is low, which requires developers or administrators to spend more time and energy to manually filter the target task progress information, affecting the efficiency of task progress monitoring.

[0042] To solve the above-mentioned problems, an embodiment of the present application provides an API-based task progress monitoring method, apparatus, device, and medium, the method comprising displaying multiple first fields and multiple second fields in a first request interface of a user terminal, the user terminal obtaining multiple first target fields selected by the user from the multiple first fields and multiple second fields, wherein different first fields are used to indicate different task progress indicator types, and different second fields are used to indicate different task identifiers; the user terminal generates a first task progress monitoring request based on a user account and all of the first target fields, and sends the first task progress monitoring request to the server, wherein the user account is an account for logging into the user terminal; the server calls the API interface to parse the first task progress monitoring request to obtain the user account and the first target field, and determines the corresponding first target progress information from a preset first database based on the user account and the first target field; the server calls the API interface to encapsulate the first target progress information into a first response, and sends the first response to the user terminal. According to the solution provided in the embodiment of the present application, the developer corresponding to each first user account can flexibly configure the corresponding task progress information request on demand in the first monitoring request interface of the user terminal to obtain target progress information. Compared with the solution of only sending task progress monitoring requests according to a configured fixed task progress request template, it is possible to flexibly configure task progress monitoring requests and avoid spending time screening target information from fixed-form task progress information, thereby improving task monitoring efficiency.

[0043] The embodiments of the present application are further described below in conjunction with the accompanying drawings.

[0044] refer to Figure 1 , Figure 1 This is a flowchart of a task progress monitoring method based on an API provided by an embodiment of the present application. The embodiment of the present application provides a task progress monitoring method based on an API, which is applied to a task monitoring system. The task monitoring system includes a server and a user terminal. The server is preset with an API interface. The user terminal is connected to the server for communication. The method includes but is not limited to the following steps:

[0045] Step S10, displaying multiple first fields and multiple second fields in the first request interface of the user terminal, and the user terminal obtains multiple first target fields selected by the user from the multiple first fields and multiple second fields, wherein different first fields are used to indicate different task progress indicator types, and different second fields are used to indicate different task identifiers.

[0046] Specifically, the first request interface of this embodiment is displayed by triggering the operation of the task monitoring platform corresponding to the user terminal when the user logs in.

[0047] Specifically, the task progress monitoring of this embodiment is to monitor the progress of different development tasks in the target software project. Each development task belongs to a task plan. The target software project includes multiple task plans, and a task plan includes at least one development task.

[0048] Specifically, the user account of the logged-in user terminal is used to uniquely identify the user, and the user account belongs to the account pool of the task monitoring system. Different user accounts in the account pool have different corresponding role permissions, wherein the role permissions of this embodiment include at least a first permission and a second permission, the first permission is used to indicate the permission corresponding to the developer responsible for executing at least one development task in the target software project, and the second permission is used to indicate the permission corresponding to the person in charge of the task plan. There are differences in the task monitoring request service content corresponding to different role permissions, for example, different development tasks can request progress monitoring, or different types of progress indicators can be requested. It can be understood that, since different users have different corresponding task execution capabilities and role permissions, it is necessary to request monitoring of the task execution progress within their own authority as needed during the user's task execution process, so as to quickly adapt to changes in the software project.

[0049] Understandably, reference Figure 2 After each user logs in to the task monitoring platform corresponding to the user terminal, he can select fields in the first request interface displayed by the user terminal to customize the private task progress monitoring request service on demand. The first request interface includes multiple optional first fields (1, 2, ..., n) and multiple optional second fields (1, 2, ..., n), wherein different second fields correspond to different task identifiers, and different first fields correspond to different task progress indicator types. For example, the first field 1 of this embodiment is the task completion status field ("completed" or "in progress"), the first field 2 is the task completion amount field (task completion percentage), the first field 3 is the task overdue status field ("overdue task identifier", "overdue duration"), the first field 4 is the task total amount field, and so on. Different second fields correspond to different task identifiers. For example, the second field 1 of this embodiment corresponds to task identifier 1, the second field 2 corresponds to task identifier 2, and so on. Based on the user's autonomous selection on the first request interface, such as Figure 2As shown, the user selects the first field 1, the first field 2, and the second field 2. The first request interface responds to the field selection operation to obtain the task progress indicator type and task identifier corresponding to the first field 1, the first field 2, and the second field 2, respectively, to provide an effective data basis for the subsequent generation of the first task progress monitoring request. That is to say, the first task progress monitoring request is generated by the user selecting the first target field on the first request interface on demand. This step is customized by each user, and the user-defined task progress monitoring response is implemented through a private request configuration service, thereby improving the flexibility of task progress monitoring, so that the task progress monitoring service is no longer limited to fixed templates. Each user can request to monitor the execution progress of the development task on demand to adapt to different task progress monitoring needs, without spending more time and energy manually filtering target information from the progress information obtained from the fixed template, thereby improving the efficiency of task progress monitoring.

[0050] Step S20: the user terminal generates a first task progress monitoring request based on the user account and all the first target fields, and sends the first task progress monitoring request to the server, wherein the user account is the account for logging into the user terminal.

[0051] Specifically, refer to Figure 2 As described in the above embodiment, the user selects the first field 1, the first field 2, and the second field 2 on the first request interface, triggering the user terminal to obtain the first field 1, the first field 2, and the second field 2, determine the first field 1, the first field 2, and the second field 2 as the first target field, and generate a first task progress monitoring request based on the first field 1, the first field 2, and the second field 2. The current first task progress monitoring request indicates the task completion status and task completion amount of the development task corresponding to the requested task identifier 1; since the task progress information of each development task of the target software project in this embodiment is stored in the first database of the server, after the user terminal generates the first task progress monitoring request, it is necessary to send the request to the server to request the required target progress information.

[0052] It should be noted that, in the embodiment of the present application, the specific method for the user terminal to send the first task progress monitoring request to the server may be to send the first task progress monitoring request to the server through the POST method or the get method. Specifically, by creating a request class, the request class encapsulates a request sending function, and assigning values ​​to the url parameter and the params parameter of the request sending function to call the request sending function, thereby sending a POST request (i.e., the first task progress monitoring request) to the url address corresponding to the url parameter. The params parameter is used to indicate the first target field of the above embodiment. The present embodiment does not limit the specific data format of the params parameter, which may be a JSON data format, and those skilled in the art may adjust it according to actual needs. In addition, the request sending function of the present embodiment also has the function of processing request responses. When the request fails, the status code information indicating the request failure is returned to the user terminal. When the request succeeds, the first target progress information of the response is returned. The data format of the first target progress information of the response is the same as the data format of the params parameter.

[0053] In some embodiments, Figure 1 In step S20, the user terminal generates a first task progress monitoring request based on all target fields, including but not limited to the following steps:

[0054] Step S21, determining the first role authority corresponding to the user account;

[0055] Step S22, determining a sensitive data inclusion flag based on the first role authority, wherein the sensitive data inclusion flag is used to indicate whether the response corresponding to the first task progress monitoring request contains sensitive data;

[0056] Step S23: Encapsulate all first target fields and the sensitive data flag to generate a first task progress monitoring request.

[0057] Specifically, the value corresponding to the sensitive data inclusion flag includeSensitiveData of this embodiment includes two types of True and False, which are used to indicate whether sensitive data is included in the response corresponding to the first task progress monitoring request. When the sensitive data inclusion flag is True, the response corresponding to the first task progress monitoring request includes sensitive data. When the sensitive data inclusion flag is False, the response corresponding to the first task progress monitoring request does not include sensitive data. Different first role permissions correspond to their own sensitive data inclusion flags. The specific corresponding relationship can be adjusted by technicians in this field according to actual conditions. For example, the sensitive data inclusion flag corresponding to the user account with a high first role permission level is True, and the sensitive data inclusion flag corresponding to the user account with a low first role permission level is False. In the scenario of this embodiment, sensitive data can be the identity authentication and authorization information of the user account initiating the request, the system configuration information of the task monitoring system, etc. This embodiment encapsulates the sensitive data inclusion flag and the first target field to generate a first task progress monitoring request, so as to control whether to respond to the sensitive data involved in the task progress request according to the first role permission, thereby effectively enhancing the data security of the task monitoring system.

[0058] Step S30: The server calls an API interface to parse the first task progress monitoring request to obtain a user account and a first target field, and determines corresponding first target progress information from a preset first database based on the user account and the first target field.

[0059] Specifically, the API interface of this embodiment is a functional module inside the server, which is responsible for parsing and responding to the first task progress monitoring request from the user terminal, thereby providing support for data exchange and information sharing between the user terminal and the server.

[0060] Specifically, the first database of this embodiment belongs to the server, and the first database stores the target progress information of each development task in the target software project. In this embodiment, the source of each target task progress information stored in the first database is as follows: the administrator logs in to the server, and selects multiple first fields and multiple second fields in the second request interface displayed by the server, and the development task corresponding to each second field is pre-assigned to each user account. The server generates each second task progress monitoring request based on the selected first field, second field and corresponding user account, and sends the second task progress information request to the user terminal bound to each user account by calling the API interface. The server calls the API interface to parse the second target progress information responded by each user terminal, and stores the second target progress information in the first database.

[0061] Specifically, the number of target development tasks corresponding to the first target progress information is determined according to the actual situation of the first task progress request sent by the user terminal. For example, when developer 1 selects the first field 1 and the second field 2 in the first request interface of the user terminal, the corresponding number of target development tasks is 2.

[0062] It can be understood that after the server's API interface parses the first task progress monitoring request sent by the user terminal to obtain the first target field and user account, the server matches the corresponding first target progress information in the first database based on the user account and the first target field, and calls the API interface again to feed back to the corresponding user terminal, which can provide effective support for the user who logs in to the user terminal to perform development task progress monitoring.

[0063] In a specific embodiment, the first target field includes at least a first subfield and a second subfield, the first subfield belongs to the first field, and the second subfield belongs to the second field. Figure 1 Step S30 includes but is not limited to the following steps:

[0064] Step S31, determining the first role authority corresponding to the user account;

[0065] Step S32, determining a first task progress indicator type set and a first task identifier set corresponding to the first role authority from a preset role authority mapping table, wherein the role authority mapping table is used to indicate a mapping relationship between each first role authority and a task progress indicator type and a task identifier;

[0066] Step S33: when the first subfield belongs to the first task progress indicator type set and the second subfield belongs to the first task identifier set, the corresponding first target progress information is obtained from the first database based on the first subfield and the second subfield.

[0067] Specifically, the role permission mapping table of this embodiment is preset in the first database of the server, indicating the mapping relationship between each role permission and the progress indicator type and task identifier, and is used to determine whether the two parameters involved in each received first task progress monitoring request (the requested development task, and the requested task progress indicator type) are compliant.

[0068] It can be understood that this embodiment first determines the first role authority corresponding to the user account in the first task progress monitoring request, and determines the first task progress indicator type set and the first task identifier set corresponding to the first role authority from the role authority mapping table. The first task progress indicator type set and the first task identifier set here respectively correspond to the task progress indicator type that can be accessed under the authority of the user account, and the development task object that can be accessed under the authority of the user account. After obtaining this information, the first subfield is matched with the data in the first task progress indicator type set, and the task identifier corresponding to the second subfield is matched with the data in the first task identifier set. Based on the matching result, it is determined whether to execute the extraction of the target progress information corresponding to the request from the first database. In this way, the role authority mapping table plays the role of authority identification in this process, ensuring the data security when the user terminal requests the server to access the task progress data.

[0069] In addition, referring to the description of the above embodiment, when the user account is associated with a first reference task identifier, the first reference task identifier is used to indicate the task identifier of the development task currently executed by the user terminal corresponding to the user account, Figure 1 Step S30 includes but is not limited to the following steps:

[0070] Step S34, when the second subfield does not belong to the first task identifier set, the server determines whether there is a task dependency relationship between the second subfield and the first reference task identifier; when there is a task dependency relationship between the second subfield and the first reference task identifier, the first role authority is upgraded to obtain the second role authority; when the first subfield belongs to the second task progress indicator type set corresponding to the second role authority, the corresponding first target progress information is obtained from the first database based on the first subfield and the second subfield; when there is no task dependency relationship between the second subfield and the first reference task identifier, the server calls the API interface to send a request failure message to the corresponding user terminal, wherein the second task identifier set associated with the second role authority contains the second subfield;

[0071] Step S35, when the second subfield belongs to the first task identification set, the server determines whether all the first subfields belong to the first task progress indicator type set, obtains a judgment result, and obtains the corresponding first target progress information from the first database based on the judgment result, all the first subfields and the second subfields.

[0072] Specifically, this embodiment does not limit the number of first reference task identifiers associated with a user account. The user account is assigned at least one first reference task identifier, and the first reference task identifier is used to indicate the task identifier of the development task currently executed by the user terminal corresponding to the user account. That is to say, the user account in this embodiment corresponds to the role of developer, and the developer is assigned at least one development task.

[0073] Specifically, referring to the description of the above embodiment, since the first task progress indicator type set and the first task identifier set respectively correspond to the task progress indicator types that can be accessed under the authority of the user account sending the request, and the development task objects that can be accessed under the authority of the user account, when the second subfield does not belong to the first task identifier set, it means that the server has detected that the user account has initiated a task progress monitoring request content that exceeds its own role authority. When the second subfield corresponds to development task A, the user account does not have the authority to monitor the progress of development task A. At this time, the server determines whether there is a task dependency relationship between development task A and the development task that the developer corresponding to the user account needs to execute. For example, the first reference task identifier corresponding to the user account initiating the request is development task B. It is detected whether there is a sequence dependency, data dependency or interaction dependency between development task A and development task B. When it is determined that there is a task dependency relationship (indicating that the execution of development task B depends on the completion or result of another development task A), the server determines that the request of the user account is reasonable, and enhances the first role authority of the user account to obtain the second role authority, that is, enhances the authority level of the user account, and provides effective support for obtaining the progress information corresponding to development task A. When it is determined that there is a task dependency, when the first subfield belongs to the second task progress indicator type set corresponding to the second role authority, it means that the task progress monitoring request parameters initiated by the user account are reasonable, and the server obtains the corresponding first target progress information from the first database based on the first subfield and the second subfield; when the first subfield does not belong to the second task progress indicator type set corresponding to the second role authority, the server obtains the corresponding progress information in the first database based on the second subfield and the second task progress indicator type set, and generates a prompt message based on the failed matching result of the first subfield and the second task progress indicator type set, and calls the API interface to return the progress information and prompt message to the user terminal; when it is determined that there is no task dependency, the server calls the API interface to send request failure information to the corresponding user terminal.

[0074] It can be understood that, in the case where the second subfield belongs to the first task identification set, the server determines whether all the first subfields belong to the first task progress indicator type set, obtains a judgment result, and obtains the corresponding first target progress information from the first database based on the judgment result, all the first subfields and the second subfields. Specifically, when the judgment result indicates that all the first subfields belong to the first task progress indicator type set, the server obtains the corresponding first target progress information in the first database based on all the second subfields and all the first subfields, and calls the API interface to return the first target progress information to the user terminal; when the judgment result indicates that the first subfield does not fully belong to the first task progress indicator type set, the server obtains the corresponding first target progress information in the first database based on the second subfield and part of the first subfields belonging to the first task progress indicator type set (shielding part of the first subfield that does not belong to the first task progress indicator type set), and calls the API interface to return the first target progress information and the request failure prompt information generated based on the part of the first subfield that does not belong to the first task progress indicator type set to the user terminal.

[0075] It is understandable that, in the process of feeding back target progress information, this embodiment considers whether the user role permissions are compliant and the task dependency between the development tasks performed by the developer himself and the development tasks requested to be monitored, thereby improving the system's task progress monitoring experience.

[0076] In addition, Figure 1 After the server in step S30 calls the API interface to parse the first task progress monitoring request to obtain the first target field, the API-based task progress monitoring method of the embodiment of the present application further includes but is not limited to the following steps:

[0077] Step S36, when the server cannot identify the task identifier corresponding to any second subfield in the first target field in the first database, the server calls the API interface to encapsulate all second reference task identifiers in the first database into a second response, and sends the second response to the user terminal;

[0078] Step S37, the user terminal obtains all second reference task identifiers from the second response, and updates the second field of the first request interface based on all second reference task identifiers;

[0079] Step S38, the user terminal obtains multiple second target fields selected by the user from multiple first fields and multiple updated second fields, generates a second task progress monitoring request based on the user account and all second target fields, and sends the second task progress monitoring request to the server.

[0080] Specifically, the second reference task identifier of this embodiment is used to indicate the task identifier having task progress information stored in the first database of the server.

[0081] It can be understood that after the server calls the API interface to parse the first task progress monitoring request to obtain the first target field, if the task identifier corresponding to any second subfield in the first target field cannot be identified in the first database, it means that the task progress monitoring object requested in the first task progress monitoring request is incorrect. The server calls the API interface to encapsulate the correct second reference task identifier that can accept the request into a second response, and sends the second response to the user terminal, so that the user terminal updates the second field in the first request interface, and provides the user with a service to re-initiate a new task progress monitoring request, namely, the second task progress monitoring request. Specifically, reference Figure 2 The user terminal obtains multiple second target fields selected by the user from multiple first fields and multiple updated second fields, generates a second task progress monitoring request based on the user account and all the second target fields, and sends the second task progress monitoring request to the server, thereby improving the user experience of the task monitoring system.

[0082] Step S40: The server calls the API interface to encapsulate the first target progress information into a first response, and sends the first response to the user terminal.

[0083] It can be understood that according to the solution provided in the embodiment of the present application, the developer corresponding to each first user account can flexibly configure the corresponding task progress information request on demand in the first monitoring request interface of the user terminal to obtain target progress information. Compared with the solution of only sending task progress monitoring requests according to a configured fixed task progress request template, it is possible to flexibly configure task progress monitoring requests and avoid spending time screening target information from fixed forms of task progress information, thereby improving task monitoring efficiency.

[0084] In addition, when executing Figure 1 After step S40, the API-based task progress monitoring method of the embodiment of the present application further includes but is not limited to the following steps:

[0085] Step S41: the user terminal calls the ensemble learning algorithm encapsulated in the ensemble learning class to perform data anomaly detection on each progress sample data in the first target progress information, and obtains anomaly labels for each progress sample data, wherein an anomaly label with a value of 1 indicates that the progress sample data has no anomaly, and an anomaly label with a value of -1 indicates that the progress sample data has an anomaly;

[0086] Step S42, generating warning information based on the progress sample data corresponding to the abnormal label with a value of -1;

[0087] Step S43, sending the alarm information to the server.

[0088] It is understandable that in the implementation Figure 1 After step S40, the user terminal receives the first response corresponding to the first task progress monitoring request, and extracts the corresponding first target progress information from the first response. Before the user terminal of this embodiment performs task progress monitoring based on the first target progress information, it first performs data anomaly detection on the first target progress information, thereby ensuring the accuracy of the task progress monitoring of the user terminal.

[0089] Specifically, the ensemble learning algorithm of this embodiment can be an Isolation Forest algorithm, which simultaneously performs model fitting and prediction through the fit_predict method to obtain a prediction model. In a specific embodiment, when the first target progress information includes multiple progress sample data, the user terminal calls the prediction model corresponding to the Isolation Forest algorithm to perform data anomaly detection on each progress sample data, and obtains an abnormal label for each progress sample data; based on the progress sample data corresponding to the abnormal label with a value of -1, an alarm message is generated and sent to the server, so that the server can take countermeasures in time for the alarm message, and the user terminal determines the progress sample data corresponding to the abnormal label with a value of 1 as reliable progress data for subsequent task progress monitoring, which further ensures the reliability of the system's task progress monitoring.

[0090] In addition, in some embodiments, the number of the second subfields is multiple, and the first target progress information includes sub-progress information corresponding to each second subfield. Figure 1 After the server in step S40 calls the API interface to send the first response to the user terminal, the API-based task progress monitoring method of the embodiment of the present application further includes but is not limited to the following steps:

[0091] Step S44, the user terminal configures a target priority for each task identifier corresponding to each second subfield based on each sub-progress information;

[0092] Step S45, the user terminal adjusts the progress monitoring request frequency of each task identifier corresponding to the second subfield based on each target priority and a preset priority threshold, wherein the higher the target priority level, the higher the corresponding progress monitoring request frequency;

[0093] Step S46: The user terminal sends a third task progress monitoring request associated with each second subfield to the server based on each progress monitoring request frequency.

[0094] Specifically, the specific method in which the user terminal configures the target priority for the task identifier corresponding to each second subfield based on each sub-progress information is that the user terminal configures the first task priority for the task identifier corresponding to each second subfield based on each sub-progress information, and displays the first task priority associated with each second subfield in the first request interface, and displays the task priority input box associated with each selected second subfield in the first request interface, the user terminal obtains the second task priority entered by the user in the task priority input box, and calculates the average of the first task priority and the second priority as the target priority of the development task corresponding to the second subfield.

[0095] Next, the user terminal adjusts the progress monitoring request frequency of the task identifier corresponding to each second subfield based on each target priority and the preset priority threshold, and sends the third task progress monitoring request associated with each second subfield to the server based on each progress monitoring request frequency, wherein the higher the target priority level is, the higher the corresponding importance of the development task is, and the higher the target priority level is, the higher the corresponding progress monitoring request frequency is. In this way, the monitoring parameters are continuously optimized according to historical data and user feedback, thereby ensuring the accuracy of task progress monitoring.

[0096] In addition, this Figure 1 After the server in step S40 calls the API interface to send the first response to the user terminal, the API-based task progress monitoring method of the embodiment of the present application also includes visually displaying the first target progress information in the first response in the first request interface of the user terminal. This embodiment does not limit the specific method of visualization, and the first target progress information may be grouped and counted based on different task identifiers as grouping conditions. For example, the progress indicators in the first target progress information include task completion status, task overdue status, etc. The task identifier of this embodiment is also associated with the corresponding developer identifier (i.e., user account). The information obtained by these grouping statistics (for example, including multiple groups of task identifiers-associated user accounts-task completion status-task overdue status) is visualized in the first request interface through a preset icon template for easy viewing by project managers.

[0097] like Figure 3 As shown, Figure 3 : is a structural diagram of a control device provided by an embodiment of the present application. The present invention also provides a control device 300, including:

[0098] The processor 310 may be implemented by a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0099] The memory 320 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 320 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 320, and the processor 310 calls and executes the API-based task progress monitoring method of the embodiment of this application;

[0100] Input / output interface 330, used to implement information input and output;

[0101] Communication interface 340, used to realize communication interaction between the apparatus and other devices, which can be realized by wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.);

[0102] bus 350 , which transmits information between the various components of the device (e.g., processor 310 , memory 320 , input / output interface 330 , and communication interface 340 );

[0103] The processor 310 , the memory 320 , the input / output interface 330 and the communication interface 340 are connected to each other in communication within the device via the bus 350 .

[0104] In addition, an embodiment of the present application further provides an electronic device, including the control device 300 of the above embodiment.

[0105] In addition, an embodiment of the present application further provides a storage medium, which is a computer-readable storage medium and stores a computer program. When the computer program is executed by a processor, the above-mentioned API-based task progress monitoring method is implemented.

[0106] As a non-transient computer-readable storage medium, the memory can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage devices. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof. The device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and are implemented to be located in one place, or may also be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment.

[0107] It will be appreciated by those skilled in the art that all or some of the steps and systems in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or transient medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically include computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0108] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above-mentioned implementation mode. Technical personnel familiar with the field can also make various equivalent deformations or substitutions under the shared conditions without violating the spirit of the present invention. These equivalent deformations or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A task progress monitoring method based on API, characterized in that: Applied to a task monitoring system, the task monitoring system includes a server and a user terminal, the server is preset with an API interface, the user terminal is connected to the server in communication, and the method includes: Displaying a plurality of first fields and a plurality of second fields in a first request interface of a user terminal, wherein the user terminal obtains a plurality of first target fields selected by a user from the plurality of first fields and the plurality of second fields, wherein different first fields are used to indicate different task progress indicator types, and different second fields are used to indicate different task identifiers; The user terminal generates a first task progress monitoring request based on a user account and all of the first target fields, and sends the first task progress monitoring request to the server, wherein the user account is an account for logging into the user terminal; The server calls the API interface to parse the first task progress monitoring request to obtain the user account and the first target field, and determines the corresponding first target progress information from a preset first database based on the user account and the first target field; The server calls the API interface to encapsulate the first target progress information into a first response, and sends the first response to the user terminal; The first target field includes at least one first subfield and a second subfield, the first subfield belongs to the first field, the second subfield belongs to the second field, and the server determines from a preset first database that the first target progress information corresponding to all the first target fields includes: Determine the first role authority corresponding to the user account; Determine a first task progress indicator type set and a first task identifier set corresponding to the first role authority from a preset role authority mapping table, wherein the role authority mapping table is used to indicate a mapping relationship between each first role authority and a task progress indicator type and a task identifier; When the first subfield belongs to the first task progress indicator type set, and the second subfield belongs to the first task identifier set, obtaining the corresponding first target progress information from the first database based on the first subfield and the second subfield; The user account is associated with a first reference task identifier, the first reference task identifier is used to indicate a task identifier of a development task currently executed by a user terminal corresponding to the user account, and the server determines corresponding first target progress information from a preset first database based on the user account and the first target field, including: In the case where the second subfield does not belong to the first task identifier set, the server determines whether there is a task dependency relationship between the second subfield and the first reference task identifier; when there is a task dependency relationship between the second subfield and the first reference task identifier, the first role authority is promoted to obtain the second role authority; when the first subfield belongs to the second task progress indicator type set corresponding to the second role authority, the corresponding first target progress information is obtained from the first database based on the first subfield and the second subfield; when there is no task dependency relationship between the second subfield and the first reference task identifier, the server calls the API interface to send a request failure message to the corresponding user terminal, wherein the second subfield is included in the second task identifier set associated with the second role authority; In the case that the second subfield belongs to the first task identification set, the server determines whether all the first subfields belong to the first task progress indicator type set, obtains a judgment result, and obtains the corresponding first target progress information from the first database based on the judgment result, all the first subfields and the second subfield.

2. The API-based task progress monitoring method according to claim 1, characterized in that: After the server calls the API interface to parse the first task progress monitoring request to obtain the first target field, the method further includes: When the server cannot identify the task identifier corresponding to any one of the second subfields in the first target field in the first database, calling the API interface to encapsulate all the second reference task identifiers in the first database into a second response, and sending the second response to the user terminal; The user terminal acquires all the second reference task identifiers from the second response, and updates the second field of the first request interface based on all the second reference task identifiers; The user terminal obtains multiple second target fields selected by the user from the multiple first fields and the multiple updated second fields, generates a second task progress monitoring request based on the user account and all the second target fields, and sends the second task progress monitoring request to the server.

3. The API-based task progress monitoring method according to claim 1, characterized in that: The user terminal generates a first task progress monitoring request based on all the first target fields, including: Determine the first role authority corresponding to the user account; Determine a sensitive data inclusion flag based on the first role authority, wherein the sensitive data inclusion flag is used to indicate whether sensitive data is included in the response corresponding to the first task progress monitoring request; Encapsulate all of the first target fields and the sensitive data including the flag to generate the first task progress monitoring request.

4. The API-based task progress monitoring method according to claim 1, characterized in that: After the server sends the first response to the user terminal, the method further includes: The user terminal calls the ensemble learning algorithm encapsulated in the ensemble learning class to perform data anomaly detection on each progress sample data in the first target progress information, and obtains anomaly labels for each progress sample data, wherein the anomaly label with a value of 1 indicates that the progress sample data has no anomaly, and the anomaly label with a value of -1 indicates that the progress sample data has an anomaly; Generate warning information based on the progress sample data corresponding to the abnormal label with a value of -1; The warning information is sent to the server.

5. The API-based task progress monitoring method according to claim 1, characterized in that: The number of the second subfields is multiple, the first target progress information includes sub-progress information corresponding to each of the second subfields, and after the server calls the API interface to send the first response to the user terminal, the method further includes: The user terminal configures a target priority for each task identifier corresponding to each second subfield based on each sub-progress information; The user terminal adjusts the progress monitoring request frequency of each task identifier corresponding to the second subfield based on each of the target priorities and a preset priority threshold, wherein a higher level of the target priority corresponds to a higher progress monitoring request frequency; The user terminal sends a third task progress monitoring request associated with each of the second subfields to the server based on each of the progress monitoring request frequencies.

6. A control device, characterized in that: It includes at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to execute the API-based task progress monitoring method as described in any one of claims 1 to 5.

7. An electronic device, characterized in that: Includes the control device as claimed in claim 6.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the API-based task progress monitoring method as described in any one of claims 1 to 5.

Images