CN113988808A - Method and device for pushing task change records, electronic equipment and storage medium - Google Patents

Abstract

The embodiment of the invention relates to a method and a device for pushing task change records, electronic equipment and a storage medium, wherein whether the preset number of change items of a traversal task are changed or not is judged; if the change occurs, generating a corresponding change record according to the changed change item; pushing the change records to terminal equipment of all users associated with the task; namely, according to the embodiment of the invention, all the change items of the task are traversed in sequence, the corresponding change records are generated when the change occurs, and the change records are pushed to all related personnel of the task in real time, so that the instantaneity of the task cooperation information is improved.

Description

Method and device for pushing task change records, electronic equipment and storage medium

Technical Field

The present invention relates to the field of computers, and in particular, to a method and an apparatus for pushing a task change record, an electronic device, and a storage medium.

Background

The task is an important component of the cooperative office platform, and a group of people are connected through a task tool to complete a matter together. Therefore, in the task completion period, the task collaborative information is very necessary to be viewed immediately.

However, in the current collaborative task, all the related personnel participating in the task need to log on the task interface to check the collaborative information of the task, that is, the instantaneity of the task collaborative information is not high.

Disclosure of Invention

The invention provides a method and a device for pushing task change records, electronic equipment and a storage medium, which are used for improving the instantaneity of task collaborative information.

In a first aspect, the present invention provides a method for pushing a task change record, including: whether the preset number of changed items of the traversal task are changed or not is judged; if the change occurs, generating a corresponding change record according to the changed change item; and pushing the change records to the terminal equipment of all users associated with the task.

As an optional embodiment, whether the preset number of change items of the traversal task are changed or not includes: and circularly executing the following steps until the preset number of changed items of the task are completed in a traversal manner: selecting any change item from the change items which are not traversed by the task, and judging whether the any change item is changed or not; if so, recording the changed items which are changed, and determining the remained changed items which are not traversed by the task; and if not, determining the remained non-traversed change items of the task.

As an optional embodiment, after performing the following steps in the loop, the method further includes: determining whether the content of the recorded changed item in which the change occurred is empty; if not, updating all changed items in batch and executing the step of generating corresponding change records according to the changed items.

As an alternative embodiment, the change item includes at least one of: the task management system comprises a task total state, a task propulsion state, task basic information, task responsible persons, task collaborating persons and task related resources.

As an optional embodiment, before whether the preset number of change items of the traversal task are changed, the method further includes: and receiving a change operation of at least one change item of the task by a user, wherein the user comprises a task principal and/or a task collaborator.

As an optional embodiment, before receiving a change operation of the user on at least one change item of the task, the method further includes: the method comprises the steps of obtaining identity information of a user, and determining operation authority of the user according to the identity information of the user, wherein the operation authority is used for limiting a change item of a task change operation performed by the user.

As an optional embodiment, the obtaining identity information of the user and determining the operation authority of the user according to the identity information of the user includes: if the user is determined to be the task responsible person according to the identity information of the user, the user has operation authority over all changed items of the task; and if the user is determined to be the task collaborator according to the identity information of the user, the user has the operation authority for part of the changed items of the task.

As an optional embodiment, the receiving a change operation of the user on at least one change item of the task includes: receiving the change operation of a task responsible person on at least one of a task total state, a task propulsion state, task basic information, the task responsible person, a task collaborator and task related resources; and/or receiving the change operation of the task collaborator on at least one of the task propulsion state, the task collaborator and the task related resources.

As an optional embodiment, the method further comprises: pushing the change record to a task interface for displaying; and/or receiving a viewing request of a user for the change record of the task; and/or receiving a user export request for the change record and exporting the change record.

As an alternative embodiment, the change record includes pre-change content and post-change content.

In a second aspect, the present invention provides a task change record pushing device, including: the traversal module is used for traversing whether the change items of the preset number of the tasks are changed or not; the generating module is used for generating a corresponding change record according to the changed change item if the change occurs; and the pushing module is used for pushing the change records to terminal equipment of all users associated with the tasks.

In a third aspect, the present invention provides an electronic device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus; a memory for storing a computer program; a processor configured to implement the method for pushing a task change record according to any one of the first aspect when executing a program stored in a memory.

In a fourth aspect, the present invention provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of the method for pushing task change records according to any one of the first aspect.

According to the pushing method and device for the task change records, the electronic equipment and the storage medium, whether the preset number of change items of the tasks are changed or not is traversed; if the change occurs, generating a corresponding change record according to the changed change item; pushing the change records to terminal equipment of all users associated with the task; namely, according to the embodiment of the invention, all the change items of the task are traversed in sequence, the corresponding change records are generated when the change occurs, and the change records are pushed to all related personnel of the task in real time, so that the instantaneity of the task cooperation information is improved.

Drawings

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

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.

FIG. 1 is a diagram illustrating a task completion cycle according to an embodiment of the present invention;

fig. 2 is a flowchart illustrating a method for pushing a task change record according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating another method for pushing task change records according to an embodiment of the present invention;

fig. 4 is a flowchart illustrating a method for pushing task change records according to another embodiment of the present invention;

fig. 5 is a schematic diagram illustrating operation permissions of a user on different changed items of a task according to an embodiment of the present invention;

fig. 6 is a flowchart of a method for pushing a task change record according to an embodiment of the present invention;

fig. 7 is a pushing apparatus for task change records according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.

The task is an important component of the collaborative office platform. In the work scenario of governments, businesses, and other organizations, a task tool links a group of people to collectively complete an event. Fig. 1 is a schematic diagram of a task completion cycle according to an embodiment of the present invention, and as shown in fig. 1, the task completion cycle is divided into three phases: task assignment, task process management and task result management. In the task issuing stage, a task principal is responsible for creating a task and distributing the task to task collaborators, such as a collaborator 1, a collaborator 2 and a collaborator 3 … … collaborator n; and then entering a task process management stage, wherein the task collaborators are responsible for executing respective tasks, respective task propulsion processes and individual result feedback, the task collaborators are responsible for supervising and hastening the tasks, and after determining that the collaborators completely complete the respective tasks, the task process management stage is entered, and at the stage, the task collaborators complete the task overall result feedback, evaluation and the like. Therefore, task process coordination and management are particularly important in a task completion period, and in the process coordination and management, it is important that all related personnel of a task can timely know task coordination information.

However, in the current collaborative task, the relevant personnel participating in the task need to log in to the task processing system interface to check the current state of each task, but the relevant personnel of the task may not be able to or cannot log in to the system synchronously, which results in low instantaneity of the task collaborative information.

In view of the above technical problems, the technical idea of the present invention is as follows: by building the function of 'task propelling record', namely when the task is changed, the corresponding change record can be generated and pushed to the terminal equipment of all related personnel of the task, the effect of real-time cooperation of progress completion and cooperative personnel completion state in the task process is achieved, a bridge for synchronously completing progress by task responsible personnel and cooperative personnel in real time is built, and the cooperation efficiency is improved.

Fig. 2 is a flowchart illustrating a method for pushing a task change record according to an embodiment of the present invention. As shown in fig. 2, the method for pushing the task change record includes:

and S101, traversing whether the preset number of changed items of the task are changed or not.

The execution main body of this embodiment may be a client or a server, a task processing system is deployed on the client or the server, or a web page version of the task processing system may be logged in through the client or the server, the task processing system includes various tasks to be handled, each task includes a plurality of parameters that allow changing, that is, the change items described in this embodiment, such as task states, task basic information, task related persons, and the like. In this step, all the changed items of the current task may be traversed in sequence through the matcher deployed on the task processing system, and it is determined whether the changed items are changed.

As an alternative embodiment, the change item includes at least one of: the task management system comprises a task total state, a task propulsion state, task basic information, task responsible persons, task collaborating persons and task related resources. The task total state can describe the overall state of the task, and comprises the steps of task in-process, task overall completion, task suspension, task reopening and the like, and is managed by a task principal; the task propulsion state can describe the propulsion state of the task collaborators on the task, and comprises the states of being in propulsion, difficult to propel, completed and the like, and is managed by the task collaborators; the task basic information comprises task types, task execution time, task notices, task contents, task titles and the like, the task person in charge is used for describing the user responsible for the whole task, the task collaborator is used for describing the user responsible for the specific execution of the task, and the task related resources are data explanations, word explanations, documents or pictures and the like related to the task.

And step S102, if the change is generated, generating a corresponding change record according to the changed change item.

Specifically, the matching unit may generate a corresponding change record based on the changed change item after identifying the changed change item. If a change item with one changed item is identified, a corresponding change record is generated, and if a plurality of change items with changed items are identified, a plurality of corresponding change records are generated. Optionally, the change record includes pre-change content and post-change content.

And step S103, pushing the change records to terminal equipment of all users associated with the tasks.

Specifically, the change record may be pushed to the terminal devices of all users related to the task in real time in the form of a message, where the terminal devices may be a mobile terminal, a computer terminal, a web page terminal, or the like.

As an optional embodiment, the method further comprises: pushing the change record to a task interface for displaying; and/or receiving a user export request for the change record and exporting the change record.

Specifically, the change records can be pushed to a task interface for displaying, so that when a user logs in the task processing system through any client (a mobile terminal, a PC terminal and a WEB terminal), the user can view the push records related to the tasks, and the mobile office efficiency is improved. In addition, the task processing system can also receive a request for exporting the change record from the user, and export the corresponding change record, so that the user experience is improved.

According to the method for pushing the task change records, whether the preset number of change items of the tasks are changed or not is traversed; if the change occurs, generating a corresponding change record according to the changed change item; pushing the change records to terminal equipment of all users associated with the task; namely, according to the embodiment of the invention, all the change items of the task are traversed in sequence, the corresponding change records are generated when the change occurs, and the change records are pushed to all related personnel of the task in real time, so that the instantaneity of the task cooperation information is improved.

On the basis of the foregoing embodiment, fig. 3 is a schematic flowchart of another method for pushing task change records according to an embodiment of the present invention, and as shown in fig. 3, the method for pushing task change records includes:

step S201, selecting any change item from the change items which are not traversed by the task, and judging whether the any change item is changed.

If yes, executing step S202 and step S203, and returning to step 201; if not, executing the step S203, and returning to the step S201 until the preset number of changed items of the completed task are traversed.

Step S202, recording the changed item.

And step S203, determining the change items which are not traversed and left by the task.

Optionally, step S204 and step S205 may be further included.

Step S204, determining whether the content of the recorded changed item is empty.

If not, it indicates that the changed item has new content input, then step 205 is executed; if it is empty, the present embodiment is ended.

And step S205, updating all changed items in batch.

In step S206, a corresponding change record is generated according to the changed change item.

And step S207, pushing the change records to terminal equipment of all users associated with the tasks.

The implementation manners of step S206 and step S207 in this embodiment are similar to the implementation manners of step S102 and step S103 in the foregoing embodiment, and are not described again here.

The difference from the above embodiment is that the embodiment further defines a specific implementation manner of how to sequentially traverse the preset number of changed items of the task. In this embodiment, the following steps are executed in a loop until a preset number of changed items of the task are completed by traversal: selecting any change item from the change items which are not traversed by the task, and judging whether the any change item is changed or not; if so, recording the changed items which are changed, and determining the remained changed items which are not traversed by the task; if not, determining the remained non-traversed change items of the task; the embodiment further comprises determining whether the recorded content of the changed item is empty; if not, updating all changed items in batch and executing the step of generating corresponding change records according to the changed items.

Specifically, for the current task, the matcher firstly selects any item from the change items which are not traversed by the task, determines whether the change item is changed, records the change item if the change is generated, determines whether the change item which is not traversed exists, and directly determines whether the change item which is not traversed exists in the task if the change is not generated; if the change items which are not traversed exist, the steps 201 to 203 are executed in a loop until the matcher traverses all the change items of the task.

After the matcher finishes traversing all the changed items, determining whether the recorded changed items are empty, if not, updating all the changed items in batch, and if so, directly ending the embodiment; and after all the changed items are updated in batch, generating a change record according to the changed items and informing all related personnel.

The method for pushing the task change records provided by the embodiment of the invention circularly executes the following steps until the preset number of change items of the task are traversed and completed: selecting any change item from the change items which are not traversed by the task, and judging whether the any change item is changed or not; if so, recording the changed items which are changed, and determining the remained changed items which are not traversed by the task; if not, determining the remained non-traversed change items of the task; after the circulation execution is finished, whether the recorded content of the changed item is empty is determined; if not, updating all changed items in batch and executing the step of generating corresponding change records according to the changed items; namely, according to the embodiment of the invention, whether all the changed items of the task are changed or not is circularly traversed, the corresponding change records are generated when the changed items are changed, and the change records are pushed to all related personnel of the task in real time, so that the instantaneity of the task cooperation information is improved.

On the basis of the foregoing embodiment, fig. 4 is a schematic flowchart of a method for pushing a task change record according to another embodiment of the present invention, and as shown in fig. 4, the method for pushing a task change record includes:

step S301, receiving a change operation of at least one change item of the task by a user.

Wherein the user comprises a task responsible and/or task collaborator.

And step S302, whether the preset number of changed items of the traversal task are changed or not is judged.

In step S303, if the change is made, a corresponding change record is generated based on the changed change item.

And step S304, pushing the change records to terminal equipment of all users associated with the task.

The implementation manners of steps S302 to S304 in this embodiment are similar to the implementation manners of steps S101 to S103 in the above embodiment, and are not described herein again.

The difference from the above embodiment is that the present embodiment further defines the object of performing the project change operation on the task, and ensures the safety that only the personnel related to the task can perform the operation on the task. In the embodiment, a change operation of a user on at least one change item of a task is received, wherein the user comprises a task responsible person and/or a task collaborator. Specifically, only the task person in charge or the task collaborator can perform the change operation on the changed items of the task.

As an alternative embodiment, before step S301, the method further includes step S300: the method comprises the steps of obtaining identity information of a user, and determining operation authority of the user according to the identity information of the user, wherein the operation authority is used for limiting a change item of a task change operation performed by the user.

Optionally, step S300 includes: if the user is determined to be the task responsible person according to the identity information of the user, the user has operation authority over all changed items of the task; and if the user is determined to be the task collaborator according to the identity information of the user, the user has the operation authority for part of the changed items of the task.

Specifically, after a user logs in the task processing system, the identity information of the user login is verified, the operation authority of the user is determined, if the user is determined to be a task principal, the task principal has the operation authority of all changed items including a task total state, a task propulsion state, task basic information, a task principal, a task collaborator and task related resources, and if the user is determined to be the task collaborator, the task collaborator has the operation authority of part changed items including the task propulsion state, the task collaborator and the task related resources.

As an alternative embodiment, the step S301 includes: receiving the change operation of a task responsible person on at least one of a task total state, a task propulsion state, task basic information, the task responsible person, a task collaborator and task related resources; and/or receiving the change operation of the task collaborator on at least one of the task propulsion state, the task collaborator and the task related resources.

Specifically, if the task person in charge has the operation authority for all the changed items, the task person in charge can perform the change operation on at least one changed item in all the changed items; and if the task collaborator has the operation authority of the task part change project, the task collaborator can change at least one item in the part change project.

Fig. 5 is a schematic diagram of operation permissions of a user on different changed items of a task according to an embodiment of the present invention, where as shown in fig. 5, the changed items of the task include: the task management system comprises basic task information, a total task state, a task propulsion state, a task principal, a task collaborator and task related resources, wherein the basic task information comprises the type, time, description (notice), content, title and the like of a task, and the total task state comprises suspension, in-progress, completion, reopening and the like. As shown in fig. 5, the task person in charge may perform a change operation on all the changed items, for example, a task collaborator who performs a task may be changed, a task may be transferred to another person in charge (person in charge of change), and the like. The task collaborators concentrate on processing own tasks, can modify respective propulsion states, add or delete accessory resources related to the tasks, add other collaborators to participate in the tasks, and the like. All the changes generate corresponding change records, and the task progress can be tracked in real time.

To further understand the embodiment of the present invention, fig. 6 is a flowchart illustrating a method for pushing task change records according to an embodiment of the present invention. As shown in fig. 6, when a task needs to be modified, a task leader or a task collaborator logs in a task processing system to query a corresponding task and modify the task, and when the task is modified, the task leader has operation permissions on all changed items including a task total state, a task progress state, task basic information, the task leader, the task collaborator, and task related resources, for example, the task total state can be modified to be task complete, task stop, and the like, and the task collaborator has operation permissions on some changed items including the task progress state, the task collaborator, and task related resources, for example, the task progress state can be modified as follows: in progress, difficult, completed, etc.; after the modification is finished, the matcher inquires the current task which is modified, then traverses the changed items in sequence, determines whether one of the changed items is changed, records the changed item which is changed if the changed item is changed, and determines whether the task has the changed item which is not traversed; if not, directly entering the step of determining whether the task has an unretraversed change item, and if the task has the unretraversed change item, continuously judging whether the task has the change until the traversal of all the change items is completed; after all the change items are traversed, judging whether the recorded change items are empty, and if so, ending; if not, all the change items are updated in batch, corresponding change records are generated (all the changed change items are recorded), all relevant persons (App, Web, PC client, etc.) are notified, and the present embodiment is ended.

That is, when the total state of the task, the propulsion state of the task and the like are modified, the information is pushed to task relatives in real time through instant messages, the task is helped to master the progress information of the task, the task collaborators are helped to know the propulsion state of the fellows, the information is collaborated efficiently, and therefore the task is pushed to be completed satisfactorily; the multi-end synchronization of the task propulsion states of the mobile phone end, the computer end and the WEB end is supported, so that when any client (mobile end, PC and WEB end) is used for checking the tasks, the propulsion records related to the tasks can be conveniently seen, and the mobile office efficiency is improved; in addition, the change records can be pushed to a 'pushing record' on a task interface for displaying, so that a user can conveniently view pushing record logs of all relevant people of the task; export of task change records is also supported; in addition, the task completion rate can be linked with the performance assessment system, and the fairness of performance evaluation in governments, companies and organizations is improved.

According to the method for pushing the task change record, the identity information of the user is obtained, and the operation authority of the user is determined according to the identity information of the user, wherein the operation authority is used for limiting the change items of the task change operation performed by the user; and receiving the change operation of the user on at least one change project of the task, wherein the user comprises task accountability and/or task collaborators, so that the task can be changed only by task related personnel, and the safety of the task is guaranteed.

Fig. 7 is a pushing device for task change records according to an embodiment of the present invention, and as shown in fig. 7, the pushing device for task change records includes:

the traversal module 10 is configured to traverse whether a preset number of change items of the task are changed; a generating module 20, configured to generate a corresponding change record according to the changed change item if the change occurs; a pushing module 30, configured to push the change record to terminal devices of all users associated with the task.

As an alternative embodiment of the present invention, the traversal module 10 is specifically configured to: and circularly executing the following steps until the preset number of changed items of the task are completed in a traversal manner: selecting any change item from the change items which are not traversed by the task, and judging whether the any change item is changed or not; if so, recording the changed items which are changed, and determining the remained changed items which are not traversed by the task; and if not, determining the remained non-traversed change items of the task.

As an alternative embodiment of the present invention, the generating module 20 is further configured to determine whether the content of the recorded changed item is empty after the loop executes the following steps; if not, updating all changed items in batch and executing the step of generating corresponding change records according to the changed items.

As an alternative embodiment of the present invention, the change item includes at least one of: the task management system comprises a task total state, a task propulsion state, task basic information, task responsible persons, task collaborating persons and task related resources.

As an alternative embodiment of the present invention, the apparatus further includes a receiving module 40, where the receiving module 40 is configured to: and receiving a change operation of at least one change item of the task by a user, wherein the user comprises a task accountability and/or a task collaborator.

As an optional embodiment of the present invention, the receiving module 40 is further configured to, before the receiving user performs a change operation on at least one change item of the task, obtain identity information of the user, and determine an operation authority of the user according to the identity information of the user, where the operation authority is used to limit the change item on which the user performs the change operation on the task.

As an alternative embodiment of the present invention, the receiving module 40 is specifically configured to: if the user is determined to be the task responsible person according to the identity information of the user, the user has operation authority over all changed items of the task; and if the user is determined to be the task collaborator according to the identity information of the user, the user has the operation authority for part of the changed items of the task.

As an alternative embodiment of the present invention, the receiving module 40 is specifically configured to: receiving the change operation of a task responsible person on at least one of a task total state, a task propulsion state, task basic information, the task responsible person, a task collaborator and task related resources; and/or receiving the change operation of the task collaborator on at least one of the task propulsion state, the task collaborator and the task related resources.

As an alternative embodiment of the present invention, the pushing module 30 is further configured to: pushing the change record to a task interface for displaying; and/or receiving a user export request for the change record and exporting the change record.

As an alternative embodiment of the present invention, the change record includes pre-change content and post-change content.

The implementation principle and technical effect of the push device for task change records provided by the embodiment of the present invention are similar to those of the above embodiments, and are not described herein again.

The pushing device for the task change records provided by the embodiment of the invention is used for traversing whether the preset number of change items of the task are changed or not through the traversal module; the generating module is used for generating a corresponding change record according to the changed change item if the change occurs; the pushing module is used for pushing the change records to terminal equipment of all users associated with the tasks; namely, according to the embodiment of the invention, all the change items of the task are traversed in sequence, the corresponding change records are generated when the change occurs, and the change records are pushed to all related personnel of the task in real time, so that the instantaneity of the task cooperation information is improved.

As shown in fig. 8, an embodiment of the present invention provides an electronic device, which includes a processor 111, a communication interface 112, a memory 113, and a communication bus 114, where the processor 111, the communication interface 112, and the memory 113 complete mutual communication via the communication bus 114,

a memory 113 for storing a computer program;

in an embodiment of the present invention, the processor 111 is configured to implement the steps of the method for pushing the task change record provided in any one of the foregoing method embodiments when executing the program stored in the memory 113.

Embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the method for pushing task change records provided in any of the foregoing method embodiments.

It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (13)

1. A method for pushing task change records is characterized by comprising the following steps:

whether the preset number of changed items of the traversal task are changed or not is judged;

if the change occurs, generating a corresponding change record according to the changed change item;

and pushing the change records to the terminal equipment of all users associated with the task.

2. The method of claim 1, wherein the traversing whether the preset number of changed items of the task are changed comprises:

and circularly executing the following steps until the preset number of changed items of the task are completed in a traversal manner:

selecting any change item from the change items which are not traversed by the task, and judging whether the any change item is changed or not;

if so, recording the changed items which are changed, and determining the remained changed items which are not traversed by the task;

and if not, determining the remained non-traversed change items of the task.

3. The method of claim 2, wherein after the step of cycling, further comprising:

determining whether the content of the recorded changed item in which the change occurred is empty;

if not, updating all changed items in batch and executing the step of generating corresponding change records according to the changed items.

4. The method of any of claims 1-3, wherein the change items include at least one of:

the task management system comprises a task total state, a task propulsion state, task basic information, task responsible persons, task collaborating persons and task related resources.

5. The method of claim 4, wherein before the preset number of changed items of the traversal task are changed, the method further comprises:

and receiving a change operation of at least one change item of the task by a user, wherein the user comprises a task principal and/or a task collaborator.

6. The method of claim 5, wherein before receiving a user change operation to at least one changed item of a task, further comprising:

the method comprises the steps of obtaining identity information of a user, and determining operation authority of the user according to the identity information of the user, wherein the operation authority is used for limiting a change item of a task change operation performed by the user.

7. The method of claim 5, wherein the obtaining identity information of the user and determining the operation authority of the user according to the identity information of the user comprises:

if the user is determined to be the task responsible person according to the identity information of the user, the user has operation authority over all changed items of the task;

and if the user is determined to be the task collaborator according to the identity information of the user, the user has the operation authority for part of the changed items of the task.

8. The method of claim 7, wherein receiving a user change operation to at least one changed item of a task comprises:

receiving the change operation of a task responsible person on at least one of a task total state, a task propulsion state, task basic information, the task responsible person, a task collaborator and task related resources;

and/or receiving the change operation of the task collaborator on at least one of the task propulsion state, the task collaborator and the task related resources.

9. The method according to any one of claims 1-3, further comprising:

pushing the change record to a task interface for displaying;

and/or receiving a viewing request of a user for the change record of the task;

and/or receiving a user export request for the change record and exporting the change record.

10. The method of any of claims 1-3, wherein the change log includes pre-change content and post-change content.

11. A task change record pushing device is characterized by comprising:

the traversal module is used for traversing whether the change items of the preset number of the tasks are changed or not;

the generating module is used for generating a corresponding change record according to the changed change item if the change occurs;

and the pushing module is used for pushing the change records to terminal equipment of all users associated with the tasks.

12. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;

a memory for storing a computer program;

a processor for implementing the steps of the method for pushing a task change log according to any one of claims 1 to 10 when executing a program stored in a memory.

13. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method for pushing a task change record according to any one of claims 1 to 10.

Images