Method and device for processing task management elements in collaborative drawing board

Abstract

The invention provides a processing method and device for task management elements in a collaborative drawing board. The method comprises the following steps: receiving a task management element creation instruction sent by a first collaborative drawing board client, and determining at least one second collaborative drawing board client needing collaborative creation of task management elements based on collaborative object identity information; determining element attribute setting items corresponding to the first collaborative drawing board client and the second collaborative drawing board client according to the collaborative object permission information; sending a corresponding element attribute setting instruction to the first collaborative drawing board client and at least one second collaborative drawing board client, wherein the element attribute setting instruction comprises a corresponding element attribute setting item; and receiving attribute information returned by the first collaborative drawing board client and the at least one second collaborative drawing board client based on the element attribute setting item, and creating a target task management element according to the attribute information. The method can improve the flexibility of creating the target task management element.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a method and apparatus for processing task management elements in a collaborative drawing board. Background Technology

[0002] In today's highly interconnected and information-driven environments, team collaboration is a crucial work method. Task management systems serve as effective tools for managing team collaboration, enhancing team efficiency and collaboration levels. Task management, built upon project management principles, involves planning, organizing, assigning, and evaluating a series of tasks.

[0003] Task management based on collaboration boards allows multiple collaborators to work together to arrange and create tasks within the collaboration board interface, which can improve the efficiency of project task creation.

[0004] However, in related technologies, the creation methods for task management elements in collaborative whiteboards are relatively simple and lack flexibility. Summary of the Invention

[0005] This disclosure provides a method and apparatus for processing task management elements in a collaborative canvas. The method for processing task management elements in a collaborative canvas can improve the flexibility of creating target task management elements.

[0006] According to one aspect of this disclosure, a method for processing task management elements in a collaborative canvas is provided, the method comprising:

[0007] Receive a task management element creation instruction sent by the first collaborative canvas client. The task management element creation instruction includes collaborative object information, which includes collaborative object identity information and collaborative object permission information.

[0008] Based on the identity information of the collaborating object, at least one second collaborative canvas client is determined to collaborate in creating the task management element, and based on the permission information of the collaborating object, the element attribute settings corresponding to the first collaborative canvas client and the second collaborative canvas client are determined.

[0009] Send corresponding element attribute setting instructions to the first collaborative canvas client and the at least one second collaborative canvas client, wherein the element attribute setting instructions include the corresponding element attribute setting items;

[0010] Receive attribute information returned by the first collaborative canvas client and the at least one second collaborative canvas client based on the element attribute settings, and create a target task management element according to the attribute information.

[0011] A second aspect of this disclosure provides a processing apparatus for task management elements in a collaborative canvas, the apparatus comprising:

[0012] The first instruction receiving unit is used to receive the task management element creation instruction sent by the first collaborative canvas client. The task management element creation instruction includes collaborative object information, which includes collaborative object identity information and collaborative object permission information.

[0013] The collaborative canvas client determination unit is used to determine at least one second collaborative canvas client that needs to collaborate in creating task management elements based on the identity information of the collaborative object, and to determine the element attribute settings corresponding to the first and second collaborative canvas clients based on the permission information of the collaborative object.

[0014] The instruction sending unit is used to send corresponding element attribute setting instructions to the first collaborative artboard client and at least one second collaborative artboard client. The element attribute setting instructions include corresponding element attribute setting items.

[0015] The element creation unit is used to receive attribute information returned by the first collaborative artboard client and at least one second collaborative artboard client based on the element attribute settings, and to create the target task management element according to the attribute information.

[0016] Optionally, in some embodiments, the element creation unit includes:

[0017] The attribute information receiving module is used to receive attribute information returned by the first collaborative artboard client and at least one second collaborative artboard client based on element attribute settings.

[0018] The permission confirmation module is used to send the attribute information returned by at least one second collaborative drawing board client to the first collaborative drawing board client if it is determined from the permission information of the collaborative object that the collaboration permission of the first collaborative drawing board client is greater than the collaboration permission of at least one second collaborative drawing board client.

[0019] The attribute confirmation module is used to receive an attribute confirmation instruction sent by the first collaborative canvas client based on the attribute information returned by at least one second collaborative canvas client.

[0020] The element creation module is used to create target task management elements based on attribute confirmation instructions, attribute information returned by the first collaborative canvas client, and attribute information returned by at least one second collaborative canvas client.

[0021] Optionally, in some embodiments, the element creation module includes:

[0022] The attribute modification submodule is used to modify the attribute information returned by at least one second collaborative canvas client based on the attribute modification information.

[0023] The element creation submodule is used to create target task management elements based on the modified attribute information returned by at least one second collaborative artboard client and the attribute information returned by the first collaborative artboard client.

[0024] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0025] The second instruction receiving unit is used to receive an element relationship setting instruction sent by the first collaborative canvas client or any second collaborative canvas client. The element relationship setting instruction includes element hierarchy information.

[0026] The sorting unit is used to process and sort multiple target task management elements according to element hierarchy information.

[0027] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0028] An association response unit is used to display multiple target task management elements on a first collaboration canvas or a second collaboration canvas, and responds to a first association operation on any target task management element.

[0029] The hierarchy determination unit is used to determine the associated management element associated with any target task management element among multiple target task management elements according to the first association operation, and to determine the hierarchy relationship between the associated management element and any target management element.

[0030] The first information generation unit is used to generate element hierarchy information based on the hierarchical relationship and the associated hierarchy information of the associated management elements.

[0031] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0032] The display unit is used to display multiple target task management elements on the first collaborative canvas or the second collaborative canvas. In response to the trigger operation of the attribute modification control corresponding to any target task management element, the hierarchical attribute modification interface is displayed. The hierarchical attribute modification interface includes the setting area of ​​the parent element and the setting area of ​​the child element.

[0033] The setting item determination unit is used to determine the setting item of the parent element in response to a first operation on the setting area of ​​the parent element, and to determine the setting item of the child element in response to a second operation on the setting area of ​​the child element.

[0034] The second information generation unit is used to generate element hierarchy information based on the target task management elements corresponding to the upper-level element settings and the target task management elements corresponding to the lower-level element settings.

[0035] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0036] The grouping unit performs grouping operations on multiple target task management elements based on element grouping instructions and element hierarchy information sent by the first collaborative canvas client or at least one second collaborative canvas client, and obtains element grouping data.

[0037] The group data sending unit is used to send element group data corresponding to the target task management element to the first collaborative canvas client and at least one second collaborative canvas client.

[0038] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0039] The status data acquisition unit is used to acquire the completion status data of all target task management elements in the same group based on the element grouping data.

[0040] The completion progress calculation unit is used to calculate the task completion progress of the corresponding group based on the completion status data, and send the task completion progress to the first collaborative canvas client and at least one second collaborative canvas client.

[0041] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0042] The classification unit is used to classify the progress of all target task management elements according to the progress classification instructions sent by the first collaborative canvas client or any second collaborative canvas client and the completion status data of the target task management elements.

[0043] The classification data sending unit is used to generate classification data based on the progress classification results and send the classification data to the first collaborative canvas client and any second collaborative canvas client. The classification data includes progress categories and the target task management elements corresponding to the progress categories.

[0044] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0045] The third instruction receiving unit is used to receive attribute change instructions sent by the first collaborative drawing board client. The attribute change instructions include element identifiers and attribute change information.

[0046] The attribute change unit is used to change the attributes of the target task management element corresponding to the element identifier based on the attribute change information.

[0047] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0048] A client determination unit is used to determine at least one task processing client based on the identity information of the processing object.

[0049] The time difference calculation unit is used to determine whether the time difference between the current date and the deadline is within a preset time difference range, and then sends processing prompt data to the task processing client.

[0050] The third aspect of this disclosure provides a storage medium storing a computer program that, when executed by a processor, implements a method for processing task management elements in a collaborative canvas as described in the first aspect.

[0051] The fourth aspect of this disclosure provides a computer device including a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement a method for processing task management elements in a collaborative drawing board as described in the first aspect.

[0052] The fifth aspect of this disclosure provides a computer program product comprising a computer program that is read and executed by a processor of a computer device, causing the computer device to perform a processing method for task management elements in a collaborative whiteboard as described in the first aspect.

[0053] The method for processing task management elements in a collaborative canvas provided in this embodiment of the present disclosure includes: receiving a task management element creation instruction sent by a first collaborative canvas client, the task management element creation instruction including collaborative object information, including collaborative object identity information and collaborative object permission information; determining at least one second collaborative canvas client that needs to collaboratively create a task management element based on the collaborative object identity information, and determining element attribute setting items corresponding to the first and second collaborative canvas clients based on the collaborative object permission information; sending corresponding element attribute setting instructions to the first collaborative canvas client and at least one second collaborative canvas client, the element attribute setting instructions including corresponding element attribute setting items; receiving attribute information returned by the first collaborative canvas client and at least one second collaborative canvas client based on the element attribute setting items, and creating a target task management element based on the attribute information.

[0054] This embodiment of the disclosure determines the element attribute settings corresponding to the first and second collaborative drawing board clients through the permission information of the collaborating objects, enabling the first and second collaborative drawing board clients to set different task attributes. Thus, based on the attribute information returned by the first and second collaborative drawing board clients according to their corresponding element attribute settings, multiple users can collaboratively create target task management elements online. Compared to the method of creating task management elements by a single collaborating object in related technologies, this embodiment of the disclosure can achieve collaborative creation by multiple collaborating objects, thereby improving the flexibility of task creation and making the created target task management elements more suitable for the actual processing needs of different collaborating objects.

[0055] Other features and advantages of this disclosure will be set forth in the following description and will be apparent in part from the description or may be learned by practicing the disclosure. The objectives and other advantages of this disclosure may be realized and obtained by means of the structures particularly pointed out in the description, claims and drawings. Attached Figure Description

[0056] The accompanying drawings are provided to further understand the technical solutions of this disclosure and constitute a part of the specification. They are used together with the embodiments of this disclosure to explain the technical solutions of this disclosure and do not constitute a limitation on the technical solutions of this disclosure.

[0057] Figure 1 A system architecture diagram is shown for the method of processing task management elements in a collaborative whiteboard according to an embodiment of this disclosure.

[0058] Figures 2A to 2D This is a schematic diagram of the scenario interface for creating target task management elements provided in this disclosure;

[0059] Figure 3 A flowchart illustrating the method for handling task management elements in the collaborative canvas provided in this disclosure;

[0060] Figure 4 A schematic diagram of the first collaborative drawing board client display interface provided in this disclosure;

[0061] Figure 5A This is a schematic diagram of the display interface of the second collaborative whiteboard client provided in this disclosure;

[0062] Figure 5B A schematic diagram of the first collaborative drawing board client display interface provided in this disclosure;

[0063] Figure 6 A schematic diagram of the first collaborative drawing board client display interface provided in this disclosure;

[0064] Figure 7This is a schematic diagram of the display interface of the second collaborative whiteboard client provided in this disclosure;

[0065] Figure 8 A schematic diagram of the display interface of the first collaborative drawing board client and the second collaborative drawing board client provided in this disclosure;

[0066] Figure 9 This is a schematic diagram of the interface displayed by the first and second collaborative drawing board clients provided in this disclosure based on the processing and sorting results;

[0067] Figure 10 A schematic diagram of the first associated operation provided in this disclosure;

[0068] Figure 11 A schematic diagram of the display interface of the first collaborative drawing board client and the second collaborative drawing board client in response to the first associated operation provided in this disclosure;

[0069] Figure 12A A schematic diagram showing multiple target task management elements in the first and second collaborative canvas clients provided in this disclosure;

[0070] Figure 12B A schematic diagram showing the "Functional Test - Hierarchical Attribute Modification" interface for the first or second collaborative drawing board client provided in this disclosure;

[0071] Figure 13 This is a schematic diagram of the display interface of the first collaborative drawing board client and the second collaborative drawing board client after the grouping operation provided in this disclosure;

[0072] Figure 14 This is a schematic diagram of the display interface of the first collaborative canvas client and the second collaborative canvas client after progress classification provided in this disclosure;

[0073] Figure 15 A schematic diagram of the content attribute modification interface displayed in the first collaborative canvas client provided in this disclosure;

[0074] Figure 16 This is a flowchart illustrating the specific process for handling task management elements in the collaborative whiteboard provided in this disclosure.

[0075] Figure 17 A schematic diagram of the structure of the processing device for task management elements in the collaborative whiteboard provided in this embodiment of the disclosure;

[0076] Figure 18 This is a terminal structure diagram for implementing various methods according to an embodiment of the present disclosure;

[0077] Figure 19 This is a server structure diagram illustrating the implementation of various methods according to an embodiment of the present disclosure. Detailed Implementation

[0078] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit the scope of this disclosure.

[0079] In related technologies, task management systems can be used to create and manage tasks. However, the interfaces of these task management systems are typically spreadsheets or other formats. When using spreadsheets, tasks can be manually entered. However, the limited real-time updates and collaboration capabilities of spreadsheets make this method unsuitable for teams seeking immediate task information. Other formats are complex and have high learning curves, making them unsuitable for rapid task arrangement. Furthermore, while collaborative canvas-based task creation simplifies interface design, it involves a single object setting the attributes of the task to be created within the canvas interface, thus creating corresponding task management elements. This means that collaborative canvas-based methods only allow for task creation by a single object, resulting in a limited and inflexible approach. Therefore, this disclosure provides a method for processing task management elements in a collaborative canvas to improve the flexibility of task creation.

[0080] System architecture and scenario description of the embodiments disclosed herein

[0081] Figure 1 This is a system architecture diagram applied to the method for processing task management elements in a collaborative whiteboard according to embodiments of the present disclosure. It includes a terminal 140, an Internet 130, a gateway 120, a server 110, etc.

[0082] Terminal 140 includes various device forms with display screens, such as desktop computers, laptops, PDAs (personal digital assistants), mobile phones, vehicle terminals, home theater terminals, dedicated terminals, intelligent voice interaction devices, smart home appliances, or aircraft. Furthermore, it can be a single device or a collection of multiple devices. Terminal 140 can communicate with the Internet 130 via wired or wireless means to exchange data. In this embodiment, the terminal 140 can deploy an Internet application corresponding to a task management system.

[0083] Server 110 refers to a computer system capable of providing certain services to terminal 140. Compared to ordinary terminal 140, server 110 has higher requirements in terms of stability, security, and performance. Server 110 can be a single high-performance computer in a network platform, a cluster of multiple high-performance computers, a portion of a single high-performance computer (e.g., a virtual machine), or a combination of portions of multiple high-performance computers (e.g., virtual machines). In this embodiment of the disclosure, server 110 can specifically be a server corresponding to an Internet application.

[0084] Gateway 120, also known as an internetwork connector or protocol converter, is a computer system or device that acts as a translator, enabling network interconnection at the transport layer. It bridges the gap between two systems using different communication protocols, data formats, languages, or even completely different architectures. Gateways can also provide filtering and security functions. Messages sent from terminal 140 to server 110 are forwarded to the corresponding server 110 via gateway 120. Messages sent from server 110 to terminal 140 are also forwarded to the corresponding terminal 140 via gateway 120.

[0085] The method for processing task management elements in the collaborative whiteboard of this disclosure can be executed by an electronic device, which can be a terminal 140 or a server 110. That is, the method for processing task management elements in the collaborative whiteboard can be executed by the terminal 140 or the server 110, or it can be executed by both the terminal 140 and the server 110.

[0086] The embodiments disclosed herein can be applied to various scenarios, such as... Figures 2A to 2D The task management element creation scenario is shown.

[0087] like Figure 2A As shown, the task creation interface 210 can be displayed for the first collaborative canvas client. After collaborative object A clicks the "Create" control 201, the task creation interface 210 can display the settings interface 202. In the settings interface 202, collaborative object A can configure the collaborative object in the collaborative object settings area 203 and configure the operation content of the collaborative object and itself in the collaborative permission settings area 204. For example, based on the settings of collaborative object A in the collaborative object settings area 203, it can be determined that the collaborative objects include collaborative object A and collaborative object B. Based on the settings of collaborative object A in the collaborative permission settings area 204, it can be determined that collaborative object A needs to collaboratively set the task name of the task to be created, and collaborative object B needs to collaboratively set the task description of the task to be created. After collaborative object A completes the settings in the collaborative object settings area 203 and the collaborative permission settings area 204, it can click the "Finish" control 205. At this time, the first collaborative canvas client corresponding to collaborative object A can display as shown. Figure 2B As shown in interface 220, the second collaborative canvas client corresponding to collaborative object B can display as follows: Figure 2C The interface shown is 230.

[0088] like Figure 2D As shown, collaborating object A is in Figure 2B After the task name is set on interface 220 as shown, and the collaborating object B is... Figure 2C After completing the task description settings on interface 230, the first collaborative canvas client corresponding to collaborative object A and the second collaborative canvas client corresponding to collaborative object B can display as shown below. Figure 2D The interface shown is 240. In Figure 2D The interface 240 shown displays a target task management element named "Functional Test". Within the content area 206 of this target task management element, the specific details of the task description set by collaborating object B can be displayed in detail or in a simplified format. It is understood that the interfaces of the first and second collaborative canvas clients are in canvas format. Compared to the fixed formats such as spreadsheets and swimlanes in related technologies, this embodiment simplifies the interface and enables flexible task arrangement. Furthermore, compared to the method of creating tasks by a single object in related technologies, this embodiment allows multiple collaborating objects to collaboratively create tasks, thereby improving the flexibility of task creation.

[0089] General Description of Embodiments in this Disclosure

[0090] According to one embodiment of this disclosure, a method for processing task management elements in a collaborative canvas is provided. For example... Figure 3 The diagram shown is a flowchart illustrating a method for processing task management elements in a collaborative canvas provided in this disclosure. This method can be applied to a device for processing task management elements in a collaborative canvas, which can be integrated into a computer device, specifically a terminal. The method for processing task management elements in a collaborative canvas may include:

[0091] Step 310: Receive the task management element creation instruction sent by the first collaborative canvas client. The task management element creation instruction contains collaborative object information, including collaborative object identity information and collaborative object permission information.

[0092] In this embodiment, the first collaborative canvas client can refer to a client used to generate task management element creation instructions, and the first collaborative canvas client can be a client corresponding to the task management system. The task management element creation instruction can refer to an instruction to create a task management element. The task management element can refer to an element corresponding to the task to be created, and an element can refer to a component in the interface used to provide information, functions, and interaction. Thus, the task management element can be any form such as an image, label, or table, and this embodiment does not specifically limit this. The object logged into the first collaborative canvas client is designated as collaborative object A. The interface displayed by the first collaborative canvas client can be in canvas form. The first collaborative canvas client can respond to the operation of collaborative object A on the canvas interface and generate task management element creation instructions. Collaborative object information can refer to the information of the object that needs to collaboratively create the task management element. Collaborative object information can include collaborative object identity information and collaborative object permission information. Collaborative object identity information can refer to information used to uniquely identify the collaborative object, such as the collaborative object's login account, employee number, IP address, etc. on the client. Collaborative object permission information can be used to indicate the collaborative object's operation permissions for creating task management elements.

[0093] Step 320: Determine at least one second collaborative canvas client that needs to collaboratively create task management elements based on the identity information of the collaborative object, and determine the element attribute settings corresponding to the first and second collaborative canvas clients based on the permission information of the collaborative object.

[0094] In this embodiment, the second collaborative canvas client can refer to the client corresponding to the identity information of the collaborative object. The second collaborative canvas client is similar to the first collaborative canvas client, except that the identity information of the collaborative object corresponding to the first and second collaborative canvas clients is different. For example, when the login object of the first collaborative canvas client is collaborative object A, the identity information of the collaborative object corresponding to the first collaborative canvas client is the identity information of collaborative object A. When the login object of the second collaborative canvas client is collaborative object B, the identity information of the collaborative object corresponding to the second collaborative canvas client is the identity information of collaborative object B. Thus, the second collaborative canvas client can be determined from multiple collaborative canvas clients corresponding to the task management system based on the collaborative object identity information. Element attribute settings can refer to options used to set the attributes of task management elements. The attributes of a task management element can include task name, task description, etc. The task description can be used to describe relevant information about the task. The collaborative permission information can include element attribute settings corresponding to the first and second collaborative canvas clients. It is understood that, depending on actual needs, the attributes of task management elements may also include the type of task management element (such as ordinary tasks, milestone tasks, subtasks, etc.), and this application embodiment does not specifically limit this.

[0095] For example, the first collaborative canvas client can display something like this: Figure 4 The canvas interface 410 shown can include multiple collaboration object setting areas 203 and multiple collaboration permission setting areas 204. Based on the collaboration permission setting area 204 corresponding to each collaboration object setting area 203, the element attribute settings that the collaboration object needs to have configured in the collaboration object setting area 203 can be determined, that is, the element attribute settings corresponding to the collaboration canvas client of the collaboration object can be determined. For example, according to... Figure 4 The interface 410 shown indicates that the element attribute setting for the first collaborative canvas client of collaborative object A is the task name. The element attribute setting for the second collaborative canvas client of collaborative object B is the task description. It is understood that the number of collaborative objects can be adjusted adaptively according to actual needs; collaborative object A and collaborative object B are merely illustrative examples.

[0096] Step 330: Send the corresponding element attribute setting instruction to the first collaborative artboard client and at least one second collaborative artboard client. The element attribute setting instruction contains the corresponding element attribute setting item.

[0097] In this embodiment, a corresponding element attribute setting instruction is generated based on the element attribute setting items corresponding to the first collaborative drawing board client and sent to the first collaborative drawing board client. Similarly, a corresponding element attribute setting instruction is generated based on the element attribute setting items corresponding to the second collaborative drawing board client and sent to the second collaborative drawing board client. For example, the element attribute setting instruction sent to the first collaborative drawing board client of collaborative object A includes the task name. The element attribute setting instruction sent to the second collaborative drawing board client of collaborative object B includes the task description.

[0098] Step 340: Receive attribute information returned by the first collaborative artboard client and at least one second collaborative artboard client based on the element attribute settings, and create the target task management element according to the attribute information.

[0099] In this embodiment of the disclosure, the first collaborative canvas client and the second collaborative canvas client can display corresponding interfaces according to the received element attribute setting instructions. By responding to the operations of the collaborative objects on the corresponding interfaces, attribute information corresponding to the element attribute setting items can be obtained. For example, the first collaborative canvas client of collaborative object A can display as follows: Figure 2B The interface shown includes a settings area for the element attribute "Task Name". The first collaborative canvas client can respond to the operation of collaborative object A on this settings area, obtaining attribute information corresponding to the "Task Name", such as the attribute information "Functional Test". The second collaborative canvas client of collaborative object B can display, as shown... Figure 5A The interface 510 shown may include a setting area for the element attribute setting item "Task Description". The second collaborative canvas client of collaborating object B can respond to collaborating object B's operations on these three setting areas to obtain attribute information corresponding to the "Task Description", such as attribute information "X1X1X1", "X2X2X2", and "X3X3X3". Here, "X1X1X1" represents the specific content of the test objective, "X2X2X2" represents the specific content of the test environment, and "X3X3X3" represents the specific content of the test standard. It is understood that... Figures 2B to 2D , Figures 4 to 5A The interface shown is merely exemplary, and this disclosure does not impose any specific limitations on it.

[0100] The system receives attribute information returned by the first collaboration board client of collaboration object A and the second collaboration board client of collaboration object B. Based on this attribute information, it creates corresponding task management elements to obtain the target task management element. For example, it can create a target task management element named "Functional Test," with test objective X1X1X1, test environment X2X2X2, and test standard X3X3X3.

[0101] In one implementation, step 340 may include the following sub-steps:

[0102] Receive attribute information returned by the first collaborative artboard client and at least one second collaborative artboard client based on element attribute settings;

[0103] If it is determined from the permission information of the collaborating object that the collaboration permission of the first collaborative canvas client is greater than the collaboration permission of at least one second collaborative canvas client, the attribute information returned by at least one second collaborative canvas client is sent to the first collaborative canvas client.

[0104] Receive an attribute confirmation command sent by the first collaborative artboard client based on attribute information returned by at least one second collaborative artboard client;

[0105] Create a target task management element based on the attribute confirmation instruction, the attribute information returned by the first collaborative canvas client, and the attribute information returned by at least one second collaborative canvas client.

[0106] It is understandable that in some embodiments, when multiple collaborating objects exist, these objects can have different permissions. For example, a collaborating object with higher permissions can view the settings of a collaborating object with lower permissions through its corresponding collaboration board client, and can modify and confirm these settings. This method can provide security for collaborative task management elements, reduce data transmission volume, and improve collaboration efficiency. Applied to the collaboration board client, this means that the interface of the collaboration board client for a collaborating object with higher permissions is different from the interface of the collaboration board client for a collaborating object with lower permissions. This method will be explained below.

[0107] In this embodiment, the collaboration permissions of the first and second collaborative canvas clients can be determined based on the collaboration object permission information. Collaboration permissions indicate whether the collaboration object corresponding to the collaborative canvas client has certain operational permissions, such as whether it has permission to view the settings of other collaboration objects and whether it has permission to perform final confirmation of task management elements. Thus, the first and second collaborative canvas clients can be controlled to display different interfaces based on the collaboration permissions. When the collaboration permissions of the first collaborative canvas client are determined to be greater than those of the second collaborative canvas client based on the collaboration object permission information, it indicates that collaboration object A has permission to view the settings of collaboration object B and permission to perform final confirmation of the target task management element. At this time, the attribute information returned by the second collaborative canvas client can be sent to the first collaborative canvas client. For example, the specific content of the test objective (X1X1X1), the specific content of the test environment (X2X2X2), and the specific content of the test standard (X3X3X3) can be sent to the first collaborative canvas client corresponding to collaboration object A. Thus, the first collaborative canvas client corresponding to collaboration object A can display... Figure 5B The interface 520 shown is illustrated. It is understood that, to clearly indicate which collaborative object set the attribute information, the identity information of the corresponding collaborative object can also be sent to the first collaborative canvas client. Thus, the first collaborative canvas client can display content such as "Operation Object: Collaboration Object B" in the corresponding attribute information area based on the collaborative object's identity information. It is understood that the display format of "Setting Object: Collaboration Object B" is exemplary, and different display formats can be set according to actual needs; this embodiment does not specifically limit this.

[0108] The attribute confirmation command indicates whether attribute information needs to be modified. When the command indicates no modification is needed, the target task management element can be created based on the command, the attribute information returned by the first collaborative canvas client, and the attribute information returned by the second collaborative canvas client. When the command indicates modification is needed, the attribute information returned by the second collaborative canvas client can be modified according to the command, and the target task management element can be created based on the modified attribute information and the attribute information returned by the first client. The following explains the case where the attribute confirmation command indicates modification is required.

[0109] In this embodiment of the disclosure, the attribute confirmation instruction includes attribute modification information. Creating a target task management element based on the attribute confirmation instruction, the attribute information returned by the first collaborative artboard client, and the attribute information returned by at least one second collaborative artboard client includes:

[0110] Modify the attribute information returned by at least one second collaborative canvas client based on the attribute modification information;

[0111] Create a target task management element based on the modified attribute information returned by at least one second collaborative canvas client and the attribute information returned by the first collaborative canvas client.

[0112] In this embodiment, when the attribute confirmation instruction carries attribute modification information, it indicates that modification is required. When the attribute confirmation instruction does not carry attribute modification information, it indicates that modification is not required. Attribute modification information can refer to information that modifies the attribute information returned by the second collaborative canvas client. For example, the attribute modification information can be in the form of an array of (modification position, modification information). Based on the modification position, the previously received attribute information returned by the second collaborative canvas client can be searched, and the attribute information corresponding to the modification position can be modified to obtain the new attribute information, thereby realizing the modification operation of attribute information during the creation stage. It is understood that the modification position can be in coordinate form, content form, etc., and this embodiment does not specifically limit this. The coordinate form can refer to the specific coordinates of the attribute to be modified in the canvas interface, and the content form can refer to the content of the attribute to be modified. Taking the content form as an example, when the attribute modification information is (X1X1X1, X4X4X4), it indicates that the test objective needs to be modified from X1X1X1 to X4X4X4. Based on the new attribute information and the previously received attribute information returned by the first collaborative canvas client, the target task management element can be created.

[0113] The embodiments of this disclosure enable high-privilege collaborative objects to modify attribute information during the task management element creation stage through the above-described method.

[0114] In this embodiment of the disclosure, the first collaborative whiteboard client can display as follows: Figure 6 The interface 610 shown includes element attribute settings such as a due date setting and a processing object setting. The attribute information includes the deadline corresponding to the due date setting and the processing object identity information corresponding to the processing object setting. The processing object identity information can refer to the information of the object handling the task corresponding to the target task management element. The deadline can refer to the final deadline for completing the task corresponding to the target task management element. For example, if collaboration object C needs to collaboratively set a due date setting and a processing object setting, the second collaboration canvas client corresponding to collaboration object C can display as follows: Figure 7 The canvas interface 710 is shown. In response to the operation of collaborating object C in the settings area 701 of the processing object settings, the processing object's identity information can be obtained. In response to the operation of collaborating object C in the settings area 702 of the due date settings, the due date can be obtained.

[0115] Thus, after the target task management element is created, task reminders can be sent to the corresponding processing objects based on the deadline of the target task management element, thereby improving the effectiveness of task management. Specifically, after receiving attribute information returned by the first collaborative canvas client and at least one second collaborative canvas client based on the element attribute settings, and creating the target task management element based on the attribute information, the process also includes:

[0116] At least one task processing client is identified based on the identity information of the processing object;

[0117] Once the time difference between the current date and the deadline is within the preset time difference range, a processing prompt data is sent to the task processing client.

[0118] It is understood that the identity information of the processing object is similar to that of the collaboration object, and the identity information of the processing object may include client login account, employee number, IP address, etc. It is understood that the client login account may refer to the login account of the client corresponding to the task management system, or the login account of other clients associated with the task management system. For example, the client login account may be the login account of instant messaging software. This instant messaging software login account may be associated with the task management system, or the client corresponding to the task management system may be logged in based on the instant messaging software login account. The client corresponding to the processing object's identity information is used as the task processing client. For example, if the processing object is processing object D, the client of the instant messaging software logged in with the account information of processing object D is used as the task processing client. It is understood that there may be one or more processing objects, and the same processing object may correspond to one or more task processing clients; this embodiment of the present disclosure does not specifically limit this.

[0119] Obtain the current date and calculate the time difference between the current date and the deadline. When the time difference is within the preset time difference range, it indicates that the final processing deadline for the task corresponding to the target task management element is approaching. At this point, processing prompt data can be sent to the task processing client. The processing prompt data can refer to data prompting the processing object to complete the corresponding task. It is understood that the preset time difference range can be adaptively set according to actual needs, and this public example does not specifically limit it.

[0120] The advantage of sending processing prompt data to the task processing client in the above-described manner according to the embodiments of this disclosure is that it can improve the effectiveness of task management and reduce task processing delays.

[0121] It is understood that, according to the method disclosed in the above embodiments, multiple target task management elements can be created, such as a target task management element named "Development and Debugging", a target task management element named "Functional Testing", and a target task management element named "Project Launch". Correspondingly, the collaboration board client corresponding to collaboration object A, collaboration object B, and collaboration object C can display as follows: Figure 8 The interface 810 shown is based on the characteristic that the collaborative whiteboard client interface of this embodiment is in whiteboard form. The three target task management elements, namely "functional testing", "development and debugging" and "project launch", can be displayed in any area of ​​the interface, thereby improving the flexibility of subsequent processing of the target task management elements.

[0122] Understandably, processing operations on multiple target task management elements can include task orchestration, which involves sorting multiple target task management elements to set dependencies between them. This allows us to determine which tasks need to be completed before others and which tasks can be executed in parallel. Task orchestration is explained in detail below.

[0123] In this embodiment of the disclosure, after receiving attribute information returned by a first collaborative canvas client and at least one second collaborative canvas client based on element attribute settings, and creating a target task management element according to the attribute information, the method further includes:

[0124] Receive element relationship setting instructions sent by the first collaborative artboard client or any second collaborative artboard client. The element relationship setting instructions include element hierarchy information.

[0125] Multiple target task management elements are processed and sorted based on element hierarchy information.

[0126] In this embodiment, the element relationship setting instruction can refer to an instruction used to set the dependency relationship between multiple target task management elements. The element relationship setting instruction can be generated by a first collaborative canvas client or a second collaborative canvas client; that is, the element relationship setting instruction can be triggered by any collaborative object. It is understood that, depending on actual needs, only collaborative canvas clients corresponding to collaborative objects with certain permissions can generate the element relationship setting instruction. That is, the first or second collaborative canvas client capable of generating the element relationship setting instruction can be determined based on the collaborative object's permission information. Element hierarchy information can refer to the corresponding hierarchy between different target task management elements, or the parent-child relationship information between different target task management elements. Based on the element hierarchy information, multiple target task management elements can be processed and sorted, thereby determining which target task management element's corresponding task should be processed first and which target task management element's corresponding task can be processed later, thus achieving task orchestration. For example, based on the element hierarchy information, multiple target task management elements can be processed and sorted. Figure 8 The three target task management elements shown are processed and sorted. The processing and sorting results are sent to the first collaborative canvas client and the second collaborative canvas client. The first and second collaborative canvas clients can display the processing and sorting results as shown below. Figure 9 The interface shown is 910. In Figure 9 In the interface 910 shown, multiple target task management elements can be connected using lines, arrows, etc., to indicate that the connected target task management elements have dependencies. For example, in... Figure 9 In the interface 910 shown, the target task management elements for "Development and Debugging," "Functional Testing," and "Project Deployment" have dependencies on each other. These three target task management elements can belong to the same project or the same group. Within these three target task management elements, the "Development and Debugging" task can be processed first, followed by the "Functional Testing" task, and finally the "Project Deployment" task. It is understandable that... Figure 9 As shown, assume that a target task management element named "PPP" is also created. Figure 9 It can be seen that there is no dependency relationship between the "PPP" task and other tasks. Therefore, the "PPP" task may belong to other projects or other groups, or it may be a task whose dependency relationship has not yet been confirmed.

[0127] In one embodiment of this disclosure, the process by which the first collaborative artboard client or the second collaborative artboard client obtains element hierarchy information may include:

[0128] Display multiple target task management elements on the first or second collaboration canvas, responding to a first association operation on any target task management element;

[0129] Based on the first association operation, determine the association management element that is associated with any one of the multiple target task management elements, and determine the hierarchical relationship between the association management element and any target management element.

[0130] Generate element hierarchy information based on hierarchical relationships and the associated hierarchy information of related management elements.

[0131] In this embodiment of the disclosure, the first collaborative canvas can refer to the canvas interface corresponding to the first collaborative client, and the second collaborative canvas can refer to the canvas interface corresponding to the second collaborative canvas client. The first collaborative canvas client can display, for example, the received target task management elements on the first collaborative canvas. Figure 9 The interface shown is 910. Similarly, the second collaboration board client can also display on the second collaboration board as shown. Figure 9 The interface shown is 910. The first association operation can refer to the operation of associating any two target task management elements. For example... Figure 10 As shown, the first association operation can refer to a collaborating object (i.e., collaborating object A, collaborating object B, or collaborating object C) dragging the target task management element corresponding to "Development and Debugging" along the dotted line path to the vicinity of the target task management element corresponding to "Functional Testing" in the corresponding collaboration canvas client interface 1010. It is understandable that... Figure 10 The dashed path shown is merely exemplary, and this embodiment does not specifically limit the drag path. It is understood that the operation form of the first associated operation can also be adaptively set according to actual needs, and this embodiment does not specifically limit it. For example, the first associated operation can also be an operation of simultaneously or at preset intervals touching the target task management element corresponding to "Development and Debugging" and the target task management element corresponding to "Functional Testing".

[0132] It is understandable that the associated management element can refer to the target task management element determined based on the first association operation. For example, based on... Figure 10 The drag-and-drop operation shown identifies the associated management element as the target task management element corresponding to "Functional Testing". The hierarchical relationship refers to the processing order between the associated management element and the target task management element that triggered the first associated operation. For example, the hierarchical relationship could refer to the processing order between the target task management element corresponding to "Functional Testing" and the target task management element corresponding to "Development and Debugging". It can be understood that when the first associated operation represents a drag-and-drop operation, the processing order can be determined based on the coordinates of the drag endpoint and the coordinates of the associated management element. Figure 10As shown, the drag endpoint is point Q. Since the Y-axis coordinate of point Q is greater than the Y-axis coordinate of the target task management element corresponding to "Functional Testing," the hierarchical relationship between the "Development and Debugging" task and the "Functional Testing" task is that the "Development and Debugging" task is processed first, followed by the "Functional Testing" task. When the first associated operation represents a touch operation, such as touching the target task management elements corresponding to "Development and Debugging" and "Functional Testing" at preset intervals, the target task management element touched first can be processed first, and the target task management element touched later can be processed later. It is understandable that, as... Figure 11 As shown in interface 1110, either the first collaborative canvas client or the second collaborative canvas client can respond to the first association operation and connect the target task management element corresponding to "Development and Debugging" with the target task management element corresponding to "Functional Testing".

[0133] Association hierarchy information can be used to represent the hierarchy of associated management elements. It's understandable that before the first association operation, each target task management element is independent, and its hierarchy can be either level 0 or level 1. When any two target task management elements are associated based on the first association operation, the hierarchy will change because the processing order can be determined by the first association operation. For example, before the first association operation, the target task management elements corresponding to the "Functional Testing," "Development and Debugging," and "Project Deployment" tasks are all at level 1. When... Figure 10 After the drag-and-drop operation on interface 1010 associates the "Functional Testing" task with the "Development and Debugging" task, the hierarchy of the target task management element corresponding to the "Development and Debugging" task is level 1, and the hierarchy changes from level 1 to level 2. Furthermore, when the "Project Deployment" task is associated with the "Functional Testing" task according to the first association operation, the hierarchy of the target task management element corresponding to the "Project Deployment" task changes from level 1 to level 3. Thus, the element hierarchy information can be determined based on the hierarchy corresponding to different target task management elements after association.

[0134] It is understood that the scenario described in the above embodiments can be a case where a single collaborating object performs a first associated operation on a corresponding collaborative canvas client. In some embodiments, when the first associated operation represents a touch operation, the first associated operation can also be performed on multiple collaborative canvas clients. For example, collaborating object A touches the target task management element of the "Development and Debugging" task on the corresponding first collaborative canvas client. Within a preset time interval, collaborating object B touches the target task management element of the "Functional Testing" task on the corresponding second collaborative canvas client. In this way, the processing order of the "Development and Debugging" task and the "Functional Testing" task can be realized. Therefore, the embodiments of this disclosure can also realize the collaborative setting of task processing order by multiple collaborating objects. When the number of target task management elements is large, this collaborative setting processing order method can improve the processing order efficiency.

[0135] In another embodiment of this disclosure, the process of the first collaborative artboard client or the second collaborative artboard client obtaining element hierarchy information may include:

[0136] Multiple target task management elements are displayed on the first or second collaborative canvas. In response to the trigger operation of the attribute modification control corresponding to any target task management element, a hierarchical attribute modification interface is displayed, which includes the setting area of ​​the parent element and the setting area of ​​the child element.

[0137] The parent element setting item is determined in response to a first operation on setting a region for a parent element, and the child element setting item is determined in response to a second operation on setting a region for a child element.

[0138] Generate element hierarchy information based on the target task management elements corresponding to the parent element settings and the target task management elements corresponding to the child element settings.

[0139] In the embodiments disclosed herein, such as Figure 12A As shown in interface 1210, the first collaborative canvas client corresponding to the first collaborative canvas or the second collaborative canvas client corresponding to the second collaborative canvas can display multiple target task management elements. Each target task management element can be equipped with an attribute modification control 1201. The first collaborative canvas client can respond to the trigger operation of the attribute modification control 1201 by the corresponding collaborative object and display the corresponding hierarchical attribute modification interface. Alternatively, the second collaborative canvas client can respond to the trigger operation of the attribute modification control 1201 by the corresponding collaborative object and display the corresponding hierarchical attribute modification interface. The hierarchical attribute modification interface can be used to modify the hierarchy of the corresponding target task management element. For example, when responding to the trigger operation of the target task management element "Functional Testing", the following can be displayed: Figure 12BThe "Functional Testing - Hierarchical Attribute Modification" interface 1220 is shown. This interface includes a parent element setting area 1202 and a child element setting area 1203. The parent element setting area 1202 is used to set parent element settings. After setting, the hierarchy of the target task management element corresponding to the parent element setting is higher than the hierarchy of the target task management element corresponding to the trigger operation. For example, the hierarchy of the target task management element corresponding to the parent element setting is higher than the hierarchy of the target task management element in "Functional Testing". The child element setting area 1203 is used to set child element settings. After setting, the hierarchy of the target task management element corresponding to the child element setting is lower than the hierarchy of the target task management element corresponding to the trigger operation. For example, the hierarchy of the target task management element corresponding to the child element setting is lower than the hierarchy of the target task management element in "Functional Testing". Thus, element hierarchy information can be determined based on the target task management elements corresponding to the parent and child element settings. For example, when the target task management element corresponding to the parent element setting is "Development and Debugging", and the target task management element corresponding to the child element setting is "Project Deployment", if the level of "Development and Debugging" is 0, then the element level information includes "Development and Debugging" level 0, "Functional Testing" level 1, and "Project Deployment" level 2. If the level of "Development and Debugging" is 1, then the element level information includes "Development and Debugging" level 1, "Functional Testing" level 2, and "Project Deployment" level 3.

[0140] It is understood that when the element hierarchy information refers to the parent-child relationship information between different target task management elements, the upper-level element setting area can refer to the area where target task management elements with parent node attributes are set, and the lower-level element setting area can refer to the area where target task management elements with child node attributes are set, or can be adjusted adaptively according to the actual situation. This disclosure embodiment does not make specific limitations on this.

[0141] The first operation can refer to determining the setting item for a parent element, and the second operation can refer to determining the setting item for a child element. For example, when each target task management element has a unique element identifier, the first operation can refer to entering the element identifier in the parent element setting area 1202, and the second operation can refer to entering the element identifier in the child element setting area 1203. Alternatively, when both the parent element setting area 1202 and the child element setting area 1203 have candidate options for target task management elements, the first and second operations can refer to selecting a candidate option from multiple candidate options. In this case, the candidate option selected in the first operation is taken as the parent element setting item, and the candidate option selected in the second operation is taken as the child element setting item.

[0142] It is understandable that processing operations on multiple target task management elements can also include grouping operations. Grouping operations refer to dividing multiple target task management elements into a single element group based on element hierarchy information. The following is a detailed explanation of grouping operations.

[0143] In this embodiment of the disclosure, after receiving attribute information returned by a first collaborative canvas client and at least one second collaborative canvas client based on element attribute settings, and creating a target task management element according to the attribute information, the method further includes:

[0144] Based on the element grouping instructions and element hierarchy information sent by the first collaborative canvas client or at least one second collaborative canvas client, multiple target task management elements are grouped to obtain element grouping data.

[0145] Send element grouping data corresponding to the target task management element to the first collaborative canvas client and at least one second collaborative canvas client.

[0146] The first or second collaborative drawing board client can respond to the touch operation of the corresponding collaborative object and generate an element grouping instruction. The element grouping instruction can indicate a grouping of multiple target task management elements with dependencies. Based on the element hierarchy information, it can be confirmed whether multiple target task management elements have dependencies. Therefore, grouping operations can be performed based on the element hierarchy information, that is, dividing multiple target task management elements with dependencies into the same element group, obtaining element grouping data. Element grouping data can include the name of the element group and the target task management elements included in the element group. For example, for a new website development project, the method described in the above embodiments can construct the following target task management elements: designing the website architecture, designing the website interface, developing backend services, developing the frontend interface, writing unit tests, and performing integration tests. Furthermore, the method described in the above embodiments can confirm that designing the website structure and designing the website interface have dependencies, developing backend services and developing the frontend interface have dependencies, and writing unit tests and performing integration tests have dependencies. After the grouping operation, the first and second collaborative drawing board clients can display as follows: Figure 13 The interface 1310 shown includes three element groups. The first element group can be named the "Design Group," which may include target task management elements for designing the website architecture and for designing the website interface. The second element group can be named the "Development Group," which may include target task management elements for developing backend services and for developing the frontend interface. The third element group can be named the "Test Group," which may include target task management elements for writing unit tests and for writing integration tests.

[0147] This disclosure embodiment can group multiple target task management elements with dependencies through grouping operations, thereby enabling group management of multiple tasks and facilitating resource allocation.

[0148] In this embodiment of the disclosure, after sending the element grouping data corresponding to the target task management element to the first collaborative canvas client and at least one second collaborative canvas client, the method further includes:

[0149] Retrieve completion status data for all target task management elements within the same group based on element grouping data;

[0150] Calculate the task completion progress of the corresponding group based on the completion status data, and send the task completion progress to the first collaborative canvas client and at least one second collaborative canvas client.

[0151] Completion status data refers to the completion status of the task corresponding to the target task management element. This data can include "completed," "incomplete," or "completed percentage," etc. Completion status data can be set by the processing object corresponding to the target task management element, or it can be obtained from the processing software of the task corresponding to the target task management element. For example, the processing software may have a transmission interface through which the completion status data of the corresponding task can be obtained. It is understood that the first and second collaborative canvas clients can display the completion status data on the interface. Figure 13 As shown, the display format can be the text "Completed" shown in area 1301, or the percentage "70%" shown in area 1302, or a progress bar, pie chart, etc. This embodiment of the disclosure does not specifically limit the format.

[0152] The system retrieves the completion status data of all target task management elements within the same element group. For example, it retrieves the completion status data of "Design Website Architecture" and "Design Website Interface" within the "Design Group." Based on the completion status data and the number of target task management elements included in the element group, it calculates the task completion progress for the corresponding element group. Taking the "Design Group" as an example, if the completion status data of "Design Website Architecture" is "Completed" and the completion status data of "Design Website Interface" is "Unprocessed," then the task completion progress of the "Design Group" is 50%. The completion status data is sent to the first and second collaborative drawing board clients, which can then display the progress in the corresponding element group based on the task completion progress. Similarly, the progress display format can be text, percentage, progress bar, pie chart, etc., which are not specifically limited in this embodiment. Figure 13As shown, the task completion progress of the "Design Group" can be displayed as "50%" in area 1303, indicating that the tasks of this group have been 50% completed.

[0153] The embodiments of this disclosure use a method for calculating task completion progress based on completed status data, which can intuitively display the task completion status of each element group, thereby facilitating task management.

[0154] It is understandable that processing operations on multiple target task management elements can also include classification operations. Classification operations refer to the operation of dividing multiple target task management elements into a single progress category based on completion status data. The following is a detailed explanation of classification operations.

[0155] In this embodiment of the disclosure, after receiving attribute information returned by a first collaborative canvas client and at least one second collaborative canvas client based on element attribute settings, and creating a target task management element according to the attribute information, the method further includes:

[0156] Based on the progress classification instructions sent by the first collaborative canvas client or any of the second collaborative canvas clients, and the completion status data of the target task management elements, classify the progress of all target task management elements.

[0157] Based on the progress classification results, classification data is generated and sent to the first collaborative canvas client and any second collaborative canvas client. The classification data includes progress categories and the target task management elements corresponding to the progress categories.

[0158] The first or second collaborative canvas client can respond to touch operations of the corresponding collaborative object and generate progress categorization instructions. Progress categorization instructions can instruct the grouping of target task management elements with the same or similar progress into one category. The current progress of the target task management elements can be determined based on completion status data, thus allowing for progress categorization. After progress categorization, categorization data is obtained. The categorization data can include the name of the progress category and the target task management elements included in each progress category. The first and second collaborative canvas clients can then display corresponding information based on the categorization data. For example, based on... Figure 13After categorizing the completion status data of the various target task management elements shown, three progress categories can be obtained. The first progress category can be named "Unprocessed," and this category can include target task management elements corresponding to website interface design, backend service development, and frontend interface development. The second progress category can be named "In Progress," and this category can include target task management elements corresponding to website architecture design and integration testing. The third progress category can be named "Completed," and this category can include target task management elements corresponding to unit test writing. Based on these three progress categories and the target task management elements included in each category, the first and second collaborative canvas clients can display as follows: Figure 14 The interface shown is 1410.

[0159] This embodiment of the disclosure uses a method of classifying progress based on completion status data, which can intuitively display the completion status of the task corresponding to each target task management element, thereby facilitating task management.

[0160] It is understood that in some embodiments, the completion status and delay status of the task can be determined based on the completion status data of the target task management element. Relevant analysis can be performed based on this data to provide a basis for subsequent task management decision changes such as attribute information modification.

[0161] It is understood that, in some embodiments, multiple target task management elements can be displayed in a timeline format based on the deadline of each target task management element, so as to intuitively visualize the relationship between the target task management elements and the deadline.

[0162] It is understandable that, in some embodiments, after the target task management element is created, its attribute information can be changed to adapt to new task management requirements. The method for modifying attribute information is described in detail below.

[0163] In this embodiment of the disclosure, after receiving attribute information returned by a first collaborative canvas client and at least one second collaborative canvas client based on element attribute settings, and creating a target task management element according to the attribute information, the method further includes:

[0164] Receive attribute change instructions sent by the first collaborative artboard client. The attribute change instructions include element identifier and attribute change information.

[0165] Modify the attributes of the target task management element corresponding to the element identifier based on the attribute change information.

[0166] Attribute change instructions can specify commands to modify the attribute information of a target task management element. An element identifier can be a unique identifier used to represent a target task management element. After creating a target task management element, an element identifier corresponding to the target task management element can be generated and sent to the first and second collaborative artboard clients. Attribute change information can refer to new attribute information. It is understood that, while creating a target task management element, its attribute information can be stored, and this attribute information can be mapped to the element identifier of that target task management element. Thus, the attribute information of different stored target task management elements can be searched based on the element identifier, and then the found attribute information can be modified based on the attribute change information.

[0167] The first collaborative canvas client can respond to the triggered operation of the corresponding collaborative object and generate attribute change instructions for the corresponding target task management element. Specifically, the process of the first collaborative canvas client obtaining attribute change instructions includes:

[0168] Multiple target task management elements are displayed on the first collaborative canvas. In response to the trigger operation of the attribute modification control corresponding to any target task management element, the content attribute modification interface is displayed. The content attribute modification interface includes a modification type selection area and an attribute display area. The modification type selection area provides candidate options for the target modification type.

[0169] In response to the selection operation of the target modification type, determine the attribute change information from the attribute display area;

[0170] Generate an attribute change instruction based on the attribute change information and the element identifier corresponding to any target task management element.

[0171] like Figure 12A As shown, the first collaborative canvas client corresponding to the first collaborative canvas or the second collaborative canvas client corresponding to the second collaborative canvas can display multiple target task management elements. Each target task management element can be equipped with an attribute modification control 1201. The first collaborative canvas client can respond to the triggering operation of the attribute modification control 1201 by the corresponding collaborative object and display the corresponding content attribute modification interface. Figure 15As shown, the content attribute modification interface 1510 may include a modification type selection area 1501 and an attribute display area 1502. The modification type selection area 1501 refers to the area for selecting modification types, and it provides candidate modification types such as Type 1 and Type 2. Type 1 and Type 2 can represent different modification types. For example, Type 1 can represent an incremental change type, i.e., modifying only some attributes. Type 2 can represent a batch change type, i.e., modifying all or more attributes. It is understood that the specific modification types represented by Type 1 and Type 2 can be set according to actual needs, and this embodiment does not specifically limit this. The attribute display area 1502 refers to the area that displays the attribute information of the corresponding target task management element. For example, for the target task management element "functional testing," the attribute display area 1502 can display the task name, test purpose, test environment, test standards, processing object and deadline of functional module X, processing object and deadline of functional module Y, etc.

[0172] Type 1 can be used as the target modification type. In response to the collaborating object's selection of Type 1 in the modification type selection area 1501, the modified attribute information and the new attribute information after modification are determined from the attribute display area 1502, thus obtaining attribute change information. For example, the attribute change information could indicate that the test environment has been changed from X2X2X2 to X4X4X4, meaning X4X4X4 is the new attribute information. The first collaboration canvas client can generate attribute change instructions based on the attribute change information and the element identifier of the target task management element corresponding to "Functional Test".

[0173] Upon receiving an attribute change instruction, the attribute information corresponding to "functional test" can be found from the attribute information of multiple target task management elements stored based on the element identifier. Based on the attribute change information, the X2X2X2 representing the test environment in the "functional test" attribute information can be changed to X4X4X4. Therefore, in this embodiment of the present disclosure, the first collaborative whiteboard client can transmit only the changed attribute information (i.e., attribute change information), thereby reducing the amount of change data transmitted and improving attribute change efficiency.

[0174] It is understood that, depending on actual needs, a second collaborative canvas client can also be set to respond to the trigger operation of the property modification control, or the permissions can be restricted to which collaborative canvas clients can respond to the trigger operation of the property modification control. That is, the embodiments of this disclosure do not specifically limit the collaborative canvas clients that trigger property modification.

[0175] The method for processing task management elements in a collaborative canvas provided in this embodiment of the present disclosure includes: receiving a task management element creation instruction sent by a first collaborative canvas client, the task management element creation instruction including collaborative object information, including collaborative object identity information and collaborative object permission information; determining at least one second collaborative canvas client that needs to collaboratively create a task management element based on the collaborative object identity information, and determining element attribute setting items corresponding to the first and second collaborative canvas clients based on the collaborative object permission information; sending corresponding element attribute setting instructions to the first collaborative canvas client and at least one second collaborative canvas client, the element attribute setting instructions including corresponding element attribute setting items; receiving attribute information returned by the first collaborative canvas client and at least one second collaborative canvas client based on the element attribute setting items, and creating a target task management element based on the attribute information.

[0176] This embodiment of the disclosure determines the element attribute settings corresponding to the first and second collaborative drawing board clients through the permission information of the collaborating objects, enabling the first and second collaborative drawing board clients to set different task attributes. Thus, based on the attribute information returned by the first and second collaborative drawing board clients according to their corresponding element attribute settings, multiple users can collaboratively create target task management elements online. Compared to the method of creating task management elements through a single object in related technologies, this embodiment of the disclosure can achieve collaborative creation by multiple collaborating objects, thereby improving the flexibility of task creation and making the created target task management elements more suitable for the actual processing situations of different collaborating objects.

[0177] This disclosure provides a detailed description of embodiments in conjunction with specific application scenarios.

[0178] like Figure 16 The diagram shown is a flowchart illustrating a method for processing task management elements in a collaborative canvas provided in this disclosure. This embodiment will provide a detailed description of the method for processing task management elements in a collaborative canvas, focusing on the executing entities of each step. The method specifically includes the following steps:

[0179] Step 1601: The server receives a task management element creation instruction sent by the first collaborative canvas client. The task management element creation instruction includes collaborative object information, which includes collaborative object identity information and collaborative object permission information.

[0180] The first collaborative artboard client can display, for example: Figure 6 As shown in the interface, the first collaborative canvas client responds to the operation of the corresponding collaborative object, obtaining the collaborative object information and its permission information. Based on the collaborative object information and its permission information, the first collaborative canvas client generates a task management element creation instruction. The server receives this task management element creation instruction.

[0181] Step 1602: The server determines at least one second collaborative canvas client based on the identity information of the collaborating object, and determines the element attribute settings corresponding to the first collaborative canvas client and at least one second collaborative canvas client based on the permission information of the collaborating object.

[0182] like Figure 6 As shown, the server can determine the second collaborative canvas client corresponding to collaborative object B and the second collaborative canvas client corresponding to collaborative object C based on the identity information of the collaborative objects. Based on the collaboration permission information, the server determines that the element attribute setting of the first collaborative canvas client (i.e., the collaborative canvas client corresponding to collaborative object A) is the task name, the element attribute setting of the second collaborative canvas client corresponding to collaborative object B is the task description, and the element attribute setting of the second collaborative canvas client corresponding to collaborative object C is the processing object and the due date.

[0183] Step 1603: The server sends corresponding element attribute setting instructions to the first collaborative artboard client and at least one second collaborative artboard client. The element attribute setting instructions include the corresponding element attribute setting items.

[0184] The server sends the element attribute settings to the corresponding collaborative artboard client. Correspondingly, the first collaborative artboard client can display the following based on the element attribute settings: Figure 2B As shown in the interface, the second collaborative canvas client corresponding to collaborative object B can display, according to the element attribute settings, such as... Figure 2C The interface shown allows the second collaborative canvas client corresponding to collaboration object C to display, based on element attribute settings, as follows: Figure 7 The interface shown.

[0185] Step 1604: The server receives attribute information returned by the first collaborative artboard client and at least one second collaborative artboard client based on the element attribute settings. The server then creates the target task management element based on the attribute information.

[0186] The first collaborative canvas client can determine the collaboration partner A's... Figure 2B The operations shown on the interface will yield attribute information corresponding to the task name (e.g., "Functional Test"). The second collaborative canvas client can then determine the attributes of the collaborative object B based on their settings. Figure 2C The interface shown allows you to obtain attribute information corresponding to the task description (such as specific details regarding the test objective, test environment, and test standards). The third collaborative whiteboard client can then determine the collaborative object C based on... Figure 7The operations shown on the interface yield attribute information corresponding to the processing object and due date. The server receives attribute information returned by the first, second, and third collaborative canvas clients. Based on this attribute information, the server creates a target task management element, such as creating a target task management element named "Functional Test".

[0187] Step 1605: The server receives an element relationship setting instruction sent by the first collaborative artboard client or any of the second collaborative artboard clients. The element relationship setting instruction includes element hierarchy information.

[0188] The server can create multiple target task management elements using the method described above. For example... Figure 10 As shown, the first or second collaborative canvas client can display multiple target task management elements. The first or second collaborative canvas client can respond to, for example... Figure 10 The drag-and-drop operation shown defines the element hierarchy information between the target task management elements of "Development and Debugging" and "Functional Testing," and generates element relationship setting instructions based on this hierarchy information. The server receives these element relationship setting instructions.

[0189] Step 1606: The server processes and sorts multiple target task management elements according to the element hierarchy information.

[0190] like Figure 11 As shown, the server can sort and process the target task management elements of "Development and Debugging" and "Functional Testing" based on element hierarchy information. For example, linking the target task management elements of "Development and Debugging" and "Functional Testing" creates a dependency between them. The sorted processing indicates that the "Development and Debugging" task should be processed before the "Functional Testing" task.

[0191] Step 1607: The server performs grouping operations on multiple target task management elements according to the element grouping instructions and element hierarchy information sent by the first collaborative canvas client or at least one second collaborative canvas client, and obtains element grouping data.

[0192] The first or second collaborative canvas client can respond to the operations of the corresponding collaborative object and generate element grouping instructions. The server receives these element grouping instructions and, based on element hierarchy information, groups multiple target task management elements (such as target task management elements corresponding to website architecture design, website interface design, unit test writing, integration test writing, backend service development, and frontend service development), resulting in the following: Figure 13The three element groups shown are the design group, the testing group, and the development group. The element grouping data includes the element group name and the target task management elements included in the element group.

[0193] Step 1608: The server sends element grouping data corresponding to the target task management element to the first collaborative canvas client and at least one second collaborative canvas client.

[0194] The server sends element grouping data to the first and second collaborative canvas clients. The first and second collaborative canvas clients can then display the element grouping data as follows: Figure 13 The interface shown.

[0195] Step 1609: The server retrieves the completion status data of all target task management elements in the same group based on the element grouping data.

[0196] For example, the server retrieves the completion status data of the target task management elements corresponding to the design of the website architecture and the design of the website interface in the design group.

[0197] Step 1610: The server calculates the task completion progress of the corresponding group based on the completion status data, and sends the task completion progress to the first collaborative canvas client and at least one second collaborative canvas client.

[0198] The server can calculate the task completion progress of a given element group based on its completion status data and the number of target task management elements within that group. For example, if an element group contains four target task management elements, and only one of these elements is completed while the other three are unprocessed, then the task completion progress for that element group is 1 / 4 = 25%. The server sends this task completion progress to both the first and second collaborative drawing board clients, who can then display the corresponding progress data on their interfaces.

[0199] Step 1611: The server performs progress classification on all target task management elements based on the progress classification instructions sent by the first collaborative canvas client or any second collaborative canvas client and the completion status data of the target task management elements.

[0200] The first or second collaborative canvas client can respond to the actions of the corresponding collaborative object and generate a progress classification instruction. The server receives this progress classification instruction and classifies the progress of all target task management elements based on the completion status data of the target task management elements. For example... Figure 14 As shown, target task management elements can be divided into three categories: unprocessed, in progress, and completed.

[0201] Step 1612: The server generates classification data based on the progress classification results and sends the classification data to the first collaborative canvas client and the second collaborative canvas client. The classification data includes progress categories and the target task management elements corresponding to the progress categories.

[0202] The server can send categorized data to the first collaborative canvas client and the second collaborative canvas client. The first and second collaborative canvas clients can then display the categorized data as follows: Figure 14 The interface shown.

[0203] Step 1613: The server determines at least one task processing client based on the object's identity information.

[0204] The server can determine the client that handles the processing task corresponding to the processing object based on the object's identity information.

[0205] Step 1614: The server determines that the time difference between the current date and the deadline is within the preset time difference range, and sends processing prompt data to the task processing client.

[0206] The server can calculate the time difference based on the current date and the deadline of the corresponding target task management element. When the time difference is within the preset time difference range, the server can send processing prompt data to the task processing client to reduce the possibility of task delays.

[0207] Description of apparatus and devices according to embodiments of this disclosure

[0208] It is understood that although the steps in the above flowcharts are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated in this embodiment, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the above flowcharts may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps.

[0209] It should be noted that in the various specific embodiments of this disclosure, when processing data related to the characteristics of the collaborating object, such as its identity information or attribute information set, is required, the permission or consent of the collaborating object will be obtained first. Furthermore, the collection, use, and processing of this data will comply with the relevant laws, regulations, and standards of the relevant regions. In addition, when embodiments of this disclosure require obtaining the identity information of a collaborating object, separate permission or consent from the collaborating object will be obtained through pop-up windows or redirection to a confirmation page. Only after obtaining the separate permission or consent of the collaborating object will the necessary target object-related data for the normal operation of the embodiments of this disclosure be obtained.

[0210] Figure 17 A schematic diagram of the structure of a processing device 1700 for task management elements in a collaborative whiteboard provided in this embodiment of the disclosure. The device includes:

[0211] The first instruction receiving unit 1701 is used to receive a task management element creation instruction sent by the first collaborative canvas client. The task management element creation instruction includes collaborative object information, which includes collaborative object identity information and collaborative object permission information.

[0212] The collaborative canvas client determination unit 1702 is used to determine at least one second collaborative canvas client that needs to collaboratively create task management elements based on the identity information of the collaborative object, and to determine the element attribute settings corresponding to the first collaborative canvas client and the second collaborative canvas client based on the permission information of the collaborative object.

[0213] The instruction sending unit 1703 is used to send a corresponding element attribute setting instruction to a first collaborative canvas client and at least one second collaborative canvas client. The element attribute setting instruction includes a corresponding element attribute setting item.

[0214] The element creation unit 1704 is used to receive attribute information returned by the first collaborative canvas client and at least one second collaborative canvas client based on the element attribute settings, and to create the target task management element according to the attribute information.

[0215] Optionally, in some embodiments, the element creation unit includes:

[0216] The attribute information receiving module is used to receive attribute information returned by the first collaborative artboard client and at least one second collaborative artboard client based on element attribute settings.

[0217] The permission confirmation module is used to send the attribute information returned by at least one second collaborative drawing board client to the first collaborative drawing board client if it is determined from the permission information of the collaborative object that the collaboration permission of the first collaborative drawing board client is greater than the collaboration permission of at least one second collaborative drawing board client.

[0218] The attribute confirmation module is used to receive an attribute confirmation instruction sent by the first collaborative canvas client based on the attribute information returned by at least one second collaborative canvas client.

[0219] The element creation module is used to create target task management elements based on attribute confirmation instructions, attribute information returned by the first collaborative canvas client, and attribute information returned by at least one second collaborative canvas client.

[0220] Optionally, in some embodiments, the element creation module includes:

[0221] The attribute modification submodule is used to modify the attribute information returned by at least one second collaborative canvas client based on the attribute modification information.

[0222] The element creation submodule is used to create target task management elements based on the modified attribute information returned by at least one second collaborative artboard client and the attribute information returned by the first collaborative artboard client.

[0223] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0224] The second instruction receiving unit is used to receive an element relationship setting instruction sent by the first collaborative canvas client or any second collaborative canvas client. The element relationship setting instruction includes element hierarchy information.

[0225] The sorting unit is used to process and sort multiple target task management elements according to element hierarchy information.

[0226] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0227] An association response unit is used to display multiple target task management elements on a first collaboration canvas or a second collaboration canvas, and responds to a first association operation on any target task management element.

[0228] The hierarchy determination unit is used to determine the associated management element associated with any target task management element among multiple target task management elements according to the first association operation, and to determine the hierarchy relationship between the associated management element and any target management element.

[0229] The first information generation unit is used to generate element hierarchy information based on the hierarchical relationship and the associated hierarchy information of the associated management elements.

[0230] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0231] The display unit is used to display multiple target task management elements on the first collaborative canvas or the second collaborative canvas. In response to the trigger operation of the attribute modification control corresponding to any target task management element, the hierarchical attribute modification interface is displayed. The hierarchical attribute modification interface includes the setting area of ​​the parent element and the setting area of ​​the child element.

[0232] The setting item determination unit is used to determine the setting item of the parent element in response to a first operation on the setting area of ​​the parent element, and to determine the setting item of the child element in response to a second operation on the setting area of ​​the child element.

[0233] The second information generation unit is used to generate element hierarchy information based on the target task management elements corresponding to the upper-level element settings and the target task management elements corresponding to the lower-level element settings.

[0234] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0235] The grouping unit performs grouping operations on multiple target task management elements based on element grouping instructions and element hierarchy information sent by the first collaborative canvas client or at least one second collaborative canvas client, and obtains element grouping data.

[0236] The group data sending unit is used to send element group data corresponding to the target task management element to the first collaborative canvas client and at least one second collaborative canvas client.

[0237] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0238] The status data acquisition unit is used to acquire the completion status data of all target task management elements in the same group based on the element grouping data.

[0239] The completion progress calculation unit is used to calculate the task completion progress of the corresponding group based on the completion status data, and send the task completion progress to the first collaborative canvas client and at least one second collaborative canvas client.

[0240] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0241] The classification unit is used to classify the progress of all target task management elements according to the progress classification instructions sent by the first collaborative canvas client or any second collaborative canvas client and the completion status data of the target task management elements.

[0242] The classification data sending unit is used to generate classification data based on the progress classification results and send the classification data to the first collaborative canvas client and any second collaborative canvas client. The classification data includes progress categories and the target task management elements corresponding to the progress categories.

[0243] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0244] The third instruction receiving unit is used to receive attribute change instructions sent by the first collaborative drawing board client. The attribute change instructions include element identifiers and attribute change information.

[0245] The attribute change unit is used to change the attributes of the target task management element corresponding to the element identifier based on the attribute change information.

[0246] Optionally, in some embodiments, the processing apparatus for task management elements in the collaborative whiteboard provided in this disclosure further includes:

[0247] A client determination unit is used to determine at least one task processing client based on the identity information of the processing object.

[0248] The time difference calculation unit is used to determine whether the time difference between the current date and the deadline is within a preset time difference range, and then sends processing prompt data to the task processing client.

[0249] In this disclosure, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0250] Reference Figure 18 , Figure 18 The structural block diagram of a portion of the terminal 140 used to implement the task management element processing method in the collaborative whiteboard according to an embodiment of this disclosure includes: a radio frequency (RF) circuit 1810, a memory 1815, an input unit 1830, a display unit 1840, a sensor 1850, an audio circuit 1860, a wireless fidelity (WiFi) module 1870, a processor 1880, and a power supply 1890, among other components. Those skilled in the art will understand that... Figure 18The terminal 140 structure shown does not constitute a limitation on a mobile phone or computer, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0251] The RF circuit 1810 can be used to receive and transmit signals during information transmission or calls. In particular, it receives downlink information from the base station and processes it with the processor 1880; in addition, it transmits uplink data to the base station.

[0252] The memory 1815 can be used to store software programs and modules. The processor 1880 executes various terminal functions and document editing by running the software programs and modules stored in the memory 1815.

[0253] The input unit 1830 can be used to receive input numeric or character information, and to generate key signal inputs related to the terminal's settings and function control. Specifically, the input unit 1830 may include a touch panel 1831 and other input devices 1832.

[0254] The display unit 1840 can be used to display input or provided information, as well as various menus of the terminal. The display unit 1840 may include a display panel 1841.

[0255] Audio circuitry 1860, speaker 1861, and microphone 1862 provide an audio interface.

[0256] In this embodiment, the processor 1880 included in the terminal 140 can execute the processing method of the task management element in the collaborative canvas of the previous embodiment.

[0257] The terminal 140 in this disclosure includes, but is not limited to, mobile phones, computers, smart voice interaction devices, smart home appliances, vehicle terminals, aircraft, etc.

[0258] Figure 19This is a partial structural block diagram of a server 110 for implementing the task management element processing method in a collaborative whiteboard according to embodiments of the present disclosure. The server 110 can vary significantly due to different configurations or performance, and may include one or more central processing units (CPUs) 1922 (e.g., one or more processors) and storage devices 1932, and one or more storage media 1930 (e.g., one or more mass storage devices) for storing application programs 1942 or data 1944. The storage devices 1932 and storage media 1930 may be temporary or persistent storage. The program stored in the storage media 1930 may include one or more modules (not shown in the figure), each module including a series of instruction operations on the server 110. Furthermore, the CPU 1922 may be configured to communicate with the storage media 1930 and execute the series of instruction operations in the storage media 1930 on the server 110.

[0259] Server 110 may also include one or more power supplies 1926, one or more wired or wireless network interfaces 1950, one or more input / output interfaces 1958, and / or one or more operating systems 1941, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0260] The central processing unit 1922 in server 110 can be used to execute the processing method of task management elements in the collaborative canvas of this disclosure embodiment.

[0261] This disclosure also provides a storage medium for storing program code, which is used to execute the processing methods of task management elements in the collaborative canvas of the foregoing embodiments.

[0262] This disclosure also provides a computer program product comprising a computer program. A processor of a computer device reads and executes the computer program, causing the computer device to perform the processing method for implementing the task management elements in the collaborative whiteboard described above.

[0263] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in this disclosure and the foregoing drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “including,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatuses.

[0264] It should be understood that in this disclosure, "at least one item" means one or more, and "more than one" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0265] It should be understood that in the description of the embodiments of this disclosure, "multiple" means two or more, "greater than", "less than", "exceeding" etc. are understood to exclude the number itself, and "above", "below", "within" etc. are understood to include the number itself.

[0266] In the several embodiments provided in this disclosure, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0267] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0268] Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0269] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0270] It should also be understood that the various implementation methods provided in this disclosure can be combined arbitrarily to achieve different technical effects.

[0271] The above is a detailed description of the embodiments of this disclosure. However, this disclosure is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this disclosure. All such equivalent modifications or substitutions are included within the scope defined by the claims of this disclosure.

Claims

1. A method for processing task management elements in a collaborative canvas, characterized in that, The method includes: Receive a task management element creation instruction sent by the first collaborative canvas client. The task management element creation instruction includes collaborative object information, which includes collaborative object identity information and collaborative object permission information. Based on the identity information of the collaborating object, at least one second collaborative canvas client is determined to collaborate in creating the task management element, and based on the permission information of the collaborating object, the element attribute settings corresponding to the first collaborative canvas client and the second collaborative canvas client are determined. Send corresponding element attribute setting instructions to the first collaborative canvas client and the at least one second collaborative canvas client, wherein the element attribute setting instructions include the corresponding element attribute setting items; Receive attribute information returned by the first collaborative canvas client and the at least one second collaborative canvas client based on the element attribute settings, and create a target task management element according to the attribute information.

2. The method according to claim 1, characterized in that, The step of receiving attribute information returned by the first collaborative canvas client and the at least one second collaborative canvas client based on the element attribute settings, and creating a target task management element according to the attribute information, includes: Receive attribute information returned by the first collaborative canvas client and the at least one second collaborative canvas client based on the element attribute settings; If it is determined, based on the permission information of the collaborating object, that the collaboration permission of the first collaborative drawing board client is greater than the collaboration permission of the at least one second collaborative drawing board client, the attribute information returned by the at least one second collaborative drawing board client is sent to the first collaborative drawing board client. Receive an attribute confirmation instruction sent by the first collaborative canvas client based on the attribute information returned by the at least one second collaborative canvas client; The target task management element is created based on the attribute confirmation instruction, the attribute information returned by the first collaborative drawing board client, and the attribute information returned by at least one second collaborative drawing board client.

3. The method according to claim 2, characterized in that, The attribute confirmation instruction includes attribute modification information. The step of creating a target task management element based on the attribute confirmation instruction, the attribute information returned by the first collaborative canvas client, and the attribute information returned by at least one second collaborative canvas client includes: Modify the attribute information returned by the at least one second collaborative drawing board client according to the attribute modification information; The target task management element is created based on the modified attribute information returned by at least one second collaborative drawing board client and the attribute information returned by the first collaborative drawing board client.

4. The method according to claim 1, characterized in that, After receiving attribute information returned by the first collaborative canvas client and the at least one second collaborative canvas client based on the element attribute settings, and creating a target task management element according to the attribute information, the method further includes: Receive an element relationship setting instruction sent by a first collaborative artboard client or any of the second collaborative artboard clients, wherein the element relationship setting instruction includes element hierarchy information; Multiple target task management elements are processed and sorted according to the element hierarchy information.

5. The method according to claim 4, characterized in that, The process of obtaining the element hierarchy information includes the following steps: Multiple target task management elements are displayed on a first or second collaborative canvas, in response to a first association operation on any one of the target task management elements; Based on the first association operation, determine the association management element associated with any one of the target task management elements from among the multiple target task management elements, and determine the hierarchical relationship between the association management element and the any one target management element; The element hierarchy information is generated based on the hierarchical relationship and the association hierarchy information of the associated management elements.

6. The method according to claim 4, characterized in that, The process of obtaining the element hierarchy information includes the following steps: Multiple target task management elements are displayed on a first collaborative canvas or a second collaborative canvas. In response to the triggering operation of the attribute modification control corresponding to any target task management element, a hierarchical attribute modification interface is displayed, which includes a parent element setting area and a child element setting area. In response to a first operation on the setting area of ​​the parent element, a setting item for the parent element is determined; and in response to a second operation on the setting area of ​​the child element, a setting item for the child element is determined. The element hierarchy information is generated based on the target task management element corresponding to the parent element setting item and the target task management element corresponding to the child element setting item.

7. The method according to any one of claims 4 to 6, characterized in that, After receiving attribute information returned by the first collaborative canvas client and the at least one second collaborative canvas client based on the element attribute settings, and creating a target task management element according to the attribute information, the method further includes: Based on the element grouping instruction sent by the first collaborative drawing board client or the at least one second collaborative drawing board client and the element hierarchy information, the multiple target task management elements are grouped to obtain element grouping data; Send the element grouping data corresponding to the target task management element to the first collaborative canvas client and the at least one second collaborative canvas client.

8. The method according to claim 7, characterized in that, After sending the element grouping data corresponding to the target task management element to the first collaborative canvas client and the at least one second collaborative canvas client, the method further includes: Based on the element grouping data, obtain the completion status data of all target task management elements in the same group; Calculate the task completion progress of the corresponding group based on the completion status data, and send the task completion progress to the first collaborative drawing board client and the at least one second collaborative drawing board client.

9. The method according to claim 1, characterized in that, After receiving attribute information returned by the first collaborative canvas client and the at least one second collaborative canvas client based on the element attribute settings, and creating a target task management element according to the attribute information, the method further includes: Based on the progress classification instruction sent by the first collaborative drawing board client or any of the second collaborative drawing board clients, and the completion status data of the target task management elements, the progress of all target task management elements is classified. Based on the progress classification results, classification data is generated and sent to the first collaborative canvas client and any one of the second collaborative canvas clients. The classification data includes progress categories and the target task management element corresponding to the progress category.

10. The method according to claim 1, characterized in that, After receiving attribute information returned by the first collaborative canvas client and the at least one second collaborative canvas client based on the element attribute settings, and creating a target task management element according to the attribute information, the method further includes: Receive an attribute change instruction sent by the first collaborative canvas client, wherein the attribute change instruction includes an element identifier and attribute change information; Based on the attribute change information, change the attributes of the target task management element corresponding to the element identifier; The process of obtaining attribute change instructions includes the following steps: Multiple target task management elements are displayed on the first collaborative canvas. In response to the trigger operation of the attribute modification control corresponding to any target task management element, a content attribute modification interface is displayed. The content attribute modification interface includes a modification type selection area and an attribute display area. The modification type selection area provides candidate options for the target modification type. In response to a selection operation on the target modification type, attribute change information is determined from the attribute display area; The attribute change instruction is generated based on the attribute change information and the element identifier corresponding to any target task management element.

11. The method according to claim 1, characterized in that, The element attribute settings include an expiration date setting and a processing object setting. The attribute information includes the expiration date corresponding to the expiration date setting and the processing object identity information corresponding to the processing object setting. After receiving attribute information returned by the first collaborative canvas client and the at least one second collaborative canvas client based on the element attribute settings, and creating a target task management element according to the attribute information, the method further includes: At least one task processing client is identified based on the identity information of the processing object; Once the time difference between the current date and the deadline is determined to be within a preset time difference range, processing prompt data is sent to the task processing client.

12. A processing device for task management elements in a collaborative canvas, characterized in that, The device includes: The first instruction receiving unit is used to receive a task management element creation instruction sent by the first collaborative canvas client. The task management element creation instruction includes collaborative object information, which includes collaborative object identity information and collaborative object permission information. The collaborative canvas client determining unit is used to determine at least one second collaborative canvas client that needs to collaboratively create the task management element based on the identity information of the collaborative object, and to determine the element attribute setting items corresponding to the first collaborative canvas client and the second collaborative canvas client according to the permission information of the collaborative object. The instruction sending unit is used to send a corresponding element attribute setting instruction to the first collaborative canvas client and the at least one second collaborative canvas client, wherein the element attribute setting instruction includes the corresponding element attribute setting item; An element creation unit is used to receive attribute information returned by the first collaborative canvas client and the at least one second collaborative canvas client based on the element attribute settings, and to create a target task management element according to the attribute information.

13. A storage medium storing a computer program, characterized in that, When a computer program is executed by a processor, it implements the method for processing task management elements in a collaborative canvas according to any one of claims 1 to 11.

14. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that, The processor executes a computer program to implement the method for processing task management elements in a collaborative drawing board as described in any one of claims 1 to 11.

15. A computer program product comprising a computer program that is read and executed by a processor of a computer device, causing the computer device to perform the processing method for task management elements in a collaborative canvas according to any one of claims 1 to 11.

Images