A to-do list creation method, apparatus, device and medium

Abstract

Embodiments of the present disclosure disclose a task list creation method, device, equipment and medium. When a first user triggers a task list creation operation in a first client interface, task list related information input by the first user is obtained. A first task list is generated based on the obtained task list related information, and the first task list is a task container. Moreover, the first task list does not depend on other entities in an application to which the first client interface belongs, and can exist independently. That is, through the technical solution provided by the present disclosure, scattered tasks can be managed by creating a task list, and because the task list can exist independently, the operation of the task list by the user is facilitated, and the operation flexibility is improved.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, specifically to a method, apparatus, device, and medium for creating a task list. Background Technology

[0002] In collaborative scenarios, users often need to receive and process multiple tasks. These tasks are typically scattered and difficult to manage, leading to low management efficiency and a negative impact on the user experience. Summary of the Invention

[0003] In view of this, embodiments of the present disclosure provide a method, apparatus, device, and medium for creating a task list, so as to manage multiple tasks through a task list, thereby improving management efficiency and user experience.

[0004] To achieve the above objectives, the technical solution provided in this disclosure is as follows:

[0005] In a first aspect of this disclosure, a method for creating a task list is provided, the method comprising:

[0006] Receive the task list creation operation triggered by the first user on the first client interface, and obtain the task list related information input by the first user;

[0007] A first task list is generated based on the task list information. The first task list is a task container and does not depend on other entities in the application to which the first client interface belongs.

[0008] In a second aspect of this disclosure, a task list creation apparatus is provided, the apparatus comprising:

[0009] The receiving unit is used to receive the task list creation operation triggered by the first user on the first client interface and to obtain the task list related information input by the first user.

[0010] The generation unit is used to generate a first task list based on the task list information. The first task list is a task container and does not depend on other entities in the application to which the first client interface belongs.

[0011] In a third aspect of this disclosure, an electronic device is provided, the device comprising: a processor and a memory;

[0012] The memory is used to store instructions or computer programs;

[0013] The processor is configured to execute the instructions or computer program in the memory to cause the electronic device to perform the method described in the first aspect.

[0014] In a fourth aspect of this disclosure, a computer-readable storage medium is provided, wherein instructions are stored therein, which, when executed on a device, cause the device to perform the method described in the first aspect.

[0015] In a fifth aspect of this disclosure, a computer program product is provided, the computer program product comprising a computer program / instructions that, when executed by a processor, implement the method described in the first aspect.

[0016] Therefore, this disclosure has the following beneficial effects:

[0017] In some embodiments of this disclosure, when a first user triggers a task list creation operation on a first client interface, the task list-related information input by the first user is obtained. A first task list is generated based on the obtained task list-related information; this first task list is a task container. Furthermore, this first task list does not depend on other entities in the application to which the first client interface belongs and can exist independently. That is, through the technical solution provided by this disclosure, scattered tasks can be managed by creating task lists, and because the task lists can exist independently, it facilitates user operations on the task lists and improves operational flexibility. Attached Figure Description

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

[0019] Figure 1 A flowchart of a task list creation method provided in this embodiment of the disclosure;

[0020] Figure 2a This is a schematic diagram illustrating the creation of a task list in a task center interface, as provided in an embodiment of this disclosure.

[0021] Figure 2b A schematic diagram of page creation provided in this embodiment of the disclosure;

[0022] Figure 2c This is a schematic diagram illustrating the display of a task list in a task center interface, as provided in an embodiment of the present disclosure.

[0023] Figure 3a This is a schematic diagram illustrating the creation of a new task in a task list, as provided in an embodiment of this disclosure.

[0024] Figure 3bThis is a schematic diagram of a task deletion list provided in an embodiment of the present disclosure;

[0025] Figure 4 This is a schematic diagram of a task list creation device provided in an embodiment of the present disclosure;

[0026] Figure 5 This is a schematic diagram of an electronic device structure provided in an embodiment of the present disclosure. Detailed Implementation

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

[0028] To facilitate understanding of the technical solutions provided in the embodiments of this disclosure, the following description will be provided in conjunction with the accompanying drawings.

[0029] See Figure 1 This figure is a flowchart of a task list creation method provided in an embodiment of this disclosure. This method can be executed by a first client, which can be installed on an electronic device. The electronic device can include devices with communication functions such as mobile phones, tablets, laptops, desktop computers, in-vehicle terminals, wearable electronic devices, all-in-one machines, and smart home devices, or it can be a device simulated by a virtual machine or simulator. Figure 1 As shown, the method may include the following steps:

[0030] S101: Receive the task list creation operation triggered by the first user on the first client interface, and obtain the task list related information input by the first user.

[0031] In some embodiments of this disclosure, to create a task list, a first user can trigger a task list creation operation on a first client interface. Upon receiving the task list creation operation triggered by the first user, the first client obtains the task list-related information input by the first user. This task list-related information may include the task list title, the collaborators corresponding to the task list, and the permissions each collaborator has for the task list.

[0032] The first client is the client of an application with task list creation functionality, and its interface is the client interface of that application. For example, the first client interface could be a task center interface, an instant messaging session interface, a collaboration space interface, or a cloud document interface. That is, the first user can trigger the task list creation operation from any of these interfaces. Specifically, the first client can be a client of a standalone application or a client of an application within a collaborative office suite. Collaborative office suite applications typically integrate one or more applications such as instant messaging, calendars, tasks, cloud documents, and audio / video conferencing.

[0033] The process of receiving a task list creation operation triggered by a first user on the first client interface and obtaining task list-related information input by the first user may include: displaying a creation page in response to the task list creation operation triggered by the first user on the first client interface; and obtaining task list-related information in response to input operations triggered by the first user on the creation page. The creation page may include a task list title input box and an add member control. The add member control is optional; if the first user does not trigger the add member control, members will not be added temporarily until the task list is created.

[0034] For example, Figure 2a As shown, when the first client interface is the Task Center interface, a task list creation control 201 can be displayed in the left area of ​​the Task Center interface 200. When the user triggers the control 201, the creation page 202 is displayed, as shown below. Figure 2b As shown in the image, page 202 includes a task list title input box and an invite member control. Users can enter a title in the task list title input box and choose whether to invite members using the invite member control. If the entered title exceeds a preset character limit, the user will be prompted that the character limit has been reached.

[0035] When a user invites members via the invite member control, the invited members can be granted first-level permissions to the created task list by default. Alternatively, permissions can be set for the invited members. Specifically, permissions can be set uniformly for all invited members, or individual permissions can be set for each invited member.

[0036] S102: Generate the first task list based on the task list information.

[0037] After obtaining the task list information, a first task list is generated based on the relevant information. The first task list is a task container used to hold tasks, and may include one or more tasks. In some embodiments, the task list may also have a state containing zero tasks. In some embodiments of this disclosure, tasks can be created in the task list, or existing tasks can be added to the task list. The tasks within the task list can be managed and manipulated. In the embodiments of this disclosure, the first task list does not depend on other entities in the application to which the first client interface belongs and can exist independently. For example, in some embodiments of this disclosure, the task list does not depend on entities such as groups, teams, documents, meetings, collaboration spaces, departments, or projects. The application to which the first client interface belongs can be an application for collaborative office work, such as an application primarily focused on IM functionality, an application primarily focused on task functionality, or an office suite application integrating IM, task, and document functions.

[0038] The application belonging to the first client interface can be a standalone IM application, a standalone task application, or a collaborative office suite application that integrates multiple applications. Other entities refer to entities created or defined within the application, such as session groups, teams, and collaborative spaces created within the application.

[0039] Once created, the first task list can be displayed on the first client interface. For example, Figure 2c As shown, after completing the creation of the first task list (named "Innovation-Related Project") in the Task Center interface, a task list named "Innovation-Related Project" will be displayed in the left area of ​​the Task Center interface 200. When the user triggers the "Innovation-Related Project" task displayed in the left area, the information of the task list will be displayed in the right area, such as information about each task included in the task list.

[0040] As can be seen, when a first user triggers a task list creation operation on the first client interface, the system obtains the task list information entered by the first user. Based on the obtained task list information, a first task list is generated. This first task list serves as a task container for managing tasks. Moreover, this first task list does not depend on other entities in the application to which the first client interface belongs and can exist independently. In other words, through the technical solution provided in this disclosure, scattered tasks can be managed by creating task lists. Furthermore, because the task lists can exist independently, it facilitates user operations on the task lists and improves operational flexibility.

[0041] When creating the first task list, different roles can be configured for it, and each role has different permissions. For example, the roles in the first task list can be divided into owner and member. The owner of the first task list has edit permissions, while the member has either edit or read permissions. Although both the owner and member have edit permissions, their edit permissions differ.

[0042] The owner's editing permissions can include editing the configuration information corresponding to the first task list and editing the tasks included in the first task list. The configuration information corresponding to editing the first task list includes editing the title and members of the first task list, archiving the first task list, and deleting the first task list.

[0043] The editing permissions for members refer to their ability to not only read the first task list but also edit its configuration information and the tasks included within it. Editing the configuration information of the first task list can include editing its title and the members associated with it; however, it does not include archiving or deleting the first task list. The reading permissions for members refer to their ability to only read and / or comment on the first task list and the tasks included within it, but they cannot edit its configuration information, create or add tasks, or edit the tasks included in the first task list. Editing permissions include reading permissions.

[0044] The first user is the creator of the first task list, i.e. the owner. The editing permissions of the first task list include editing the tasks included in the first task list and the configuration information corresponding to the first task list. Editing the configuration information of the first task list includes archiving the first task list and deleting the first task list.

[0045] In some implementations, the owner of the task list can transfer ownership to another user. Specifically, in response to a transfer operation triggered by a first user on the first task list, ownership of the first task list is transferred to a second user, making the second user the owner of the first task list. Specifically, a transfer control can be displayed on the interface corresponding to the first task list. In response to the first user's triggering of the transfer control, a transfer interface is displayed. The first user can enter or search for the second user to whom they wish to transfer the task list in the transfer interface. After finding the second user, in response to the first user's confirmation operation on the transfer interface, the first task list is transferred to the second user, thus making the second user the owner of the first task list and granting them owner privileges. After the transfer is completed, the first user can either become a regular member of the first task list or exit the first task list directly after the transfer.

[0046] The first task list can contain one or more members, which can be added in the following ways:

[0047] One approach is to include member information in the task list information entered by the first user when creating the first task list. Then, when generating the first task list based on this information, members are added to the first task list according to this member information. In other words, corresponding member information is added when creating the first task list, so that members are added to the first task list when it is generated.

[0048] One approach is to add members to the first task list after it is generated, in response to a member addition operation triggered on the first task list. The user who triggers the member addition operation can be the owner of the first task list or a member with editing permissions for the first task list; this embodiment does not impose such limitations.

[0049] One approach is to create a first task list within the instant messaging session interface, then all or some members of the instant messaging session can be included in the first task list. Specifically, when creating the first task list, you can either select all members of the instant messaging session with a single click, or individually select specific session members using their corresponding checkboxes.

[0050] One approach is to create a first task list within the cloud document interface and then include all or some of the collaborators from that interface as members of the first task list. Specifically, when creating the first task list, you can select all members from the cloud document interface with a single click, or individually select specific session members using the checkboxes corresponding to each collaborator.

[0051] After creating the first task list, you can create or add tasks within it to manage them. For example... Figure 3a The interface diagram corresponding to the first task list shown can display the title of the first task list, a share control 301, a separate window 302, and a task control 303. The share control 301 can trigger sharing of the first task list, the separate window 302 can trigger the display of the first task list in a separate window, and the task control 303 can be used to create or add tasks in the first task list. The drop-down menu in the task control 303 displays an "Add Task" button. Furthermore, in... Figure 3a The interface shown can also display other operations for the task, such as filtering, sorting, adding subtasks, etc.

[0052] In some implementations, in response to creating or adding a target task in a first task list, permissions for the target task are configured for members of the first task list based on their permissions to the first task list. That is, when a target task is created or added to the first task list, the permissions of the members of the first task list for the target task are configured based on their permissions to the first task list. For example, if a member of the first task list has edit permissions for the first task list, and these edit permissions include the ability to edit tasks within the first task list, then that member also has edit permissions for the target task. If a member of the first task list has read permissions for the first task list, then that member has at least read permissions for the target task. The phrase "at least read permissions" is used because if the member originally had higher permissions for the target task, those higher permissions are retained. For example, if user A is both a member of the first task list with read permissions and was originally a collaborator on the target task with edit permissions, then user A still has edit permissions for the target task added to the first task list. A task can be added to multiple different task lists.

[0053] In some implementations, the following operations may also exist:

[0054] One approach is to remove the deleted task from the first task list in response to its deletion.

[0055] One approach is to not delete tasks in the first task list in response to its deletion. In other words, if the task list is deleted, the tasks within it are not deleted by default.

[0056] One approach is to delete unassigned tasks from the first task list in response to its deletion. In other words, when a task list is deleted, tasks without assigned personnel can be removed. Specifically, when deleting a task list, the user can choose whether to delete unassigned tasks; if the user chooses to delete, those tasks are then removed. For example, Figure 3b As shown, when a user triggers the deletion of a task list, a prompt box can be displayed with checkboxes so that the user can choose whether to delete the unresponsible tasks in the task list at the same time.

[0057] In some implementations, if a first task list is created or added in the first business interface, the associated members of the first business interface are granted first permissions for the first task list by default. In response to an edit operation triggered on the first task list, the permissions of the associated members for the first task list are modified to second permissions. That is, when a user creates or adds a first task list in the first business interface, the associated members of the first business interface can be granted first permissions for the first task list by default. A permission modification operation can be triggered during the creation or addition process to change the permissions of the associated members for the first task list to second permissions. Alternatively, a permission modification operation can be triggered after creation or addition is completed to change the permissions of the associated members for the first task list to second permissions.

[0058] In some implementations, if a first task list is created or added in the first business interface, permissions for the first task list are granted to the associated members of the first business interface according to the permission configuration operation. That is, when a first task list is created or added in the first business interface, the user can configure permissions for the associated members of the first business interface. Specifically, when configuring permissions, a unified permission configuration can be performed for all associated members of the first business interface, or different permissions can be configured for different associated members at the member granularity.

[0059] The first and second permissions are one of the following: no access permission, reading permission, or editing permission. The first business interface may include an instant messaging session interface or a cloud document interface. When the first business interface is an instant messaging session interface, its associated members are some or all of the corresponding session members. When the first business interface is a cloud document session interface, its associated members are some or all of the corresponding cloud document collaborators.

[0060] In some implementations, if the permissions of one or more associated members regarding the first task list are changed to no permissions, a first prompt message is displayed on the first business interface corresponding to the one or more associated members. This first prompt message indicates that access to the first task list is denied. That is, after changing the permissions of an associated member regarding the first task list from having access to no access, the associated member can still see the first task list in the first business interface, but cannot view the relevant content of the first task list; they can only see the first prompt message.

[0061] The presentation of the first prompt message can take several forms: one is to display the first task list in a preset mode, and use the preset mode to remind the user that they do not have permission to access it, such as by turning the color gray; another is to display the first prompt message when the mouse hovers over the first task list; and the third is to display the first prompt message when an associated member clicks on the first task list.

[0062] To facilitate access requests from associated members, an access request control can be displayed. In response to a member's triggering of the access request control, an request page can be displayed. This request page can show the owner of the first task list. Associated members can request access from the owner by triggering the send control on the request page.

[0063] If the first task list is deleted, a second notification message will be displayed on the first business interface to indicate that the first task list has been deleted. In other words, when the first task list is deleted, a second notification message can be displayed on the first business interface to inform its associated members that the first task list has been deleted. The presentation format of the second notification message can be found in the description of the first notification message above.

[0064] pass Figure 3aIt can be seen that a sharing operation can also be triggered on the first task list. Specifically, in response to a third user sharing the first task list with a fourth user, the fourth user is granted the permissions they have for the first task list. The fourth user's permissions for the first task list are no higher than the third user's permissions. That is, a user can only absolve themselves of the highest permissions they possess for the first task list. The third user can be either the owner or a member of the first task list. Specifically, if user A shares a task list with user B, and user A only has read permissions for the task list, then user B, through user A's sharing operation, can only obtain read permissions for the task list; if user A has edit permissions for the task list, then when user A shares the task list with user B, user A can grant user B edit permissions or only grant user B read permissions.

[0065] In some implementations, if the first task list includes a first member and a first task, the permissions that the first member has for the first task are target permissions. These target permissions are the greater of the permissions corresponding to the role the first member assumes in the first task and the permissions the first member is granted in the first task list. In other words, the permissions a user has for a task are equal to the greater of {the permissions granted by the task role and the permissions granted by the task list}.

[0066] For example, User A has edit permissions for Task List 1 (including edit permissions for the tasks in Task List 1), and User A is a follower of Task 1. Since followers of a task only have read permissions, not edit permissions, when Task 1 is added to Task List 1, User A can edit Task 1 because User A has edit permissions for the list. As another example, User A is the person in charge of Task 2 and can edit the task; User B adds Task 2 to Task List 2 but only grants User A read permissions. Then, User A can edit Task 2 because User A is the person in charge of Task 2 and has edit permissions.

[0067] Based on the above method embodiments, this disclosure provides a task list creation apparatus and electronic device, which will be described below in conjunction with the accompanying drawings.

[0068] See Figure 4 The figure is a structural diagram of a task list creation device provided in an embodiment of this disclosure, as shown below. Figure 4 As shown, the device 400 includes a receiving unit 401 and a generating unit 402.

[0069] The receiving unit 401 is used to receive the task list creation operation triggered by the first user on the first client interface and obtain the task list related information input by the first user.

[0070] The generation unit 402 is used to generate a first task list based on the task list information. The first task list is a task container and does not depend on other entities in the application to which the first client interface belongs.

[0071] In some implementations, the first client interface is a task center interface, an instant messaging session interface, a collaboration space interface, or a cloud document interface.

[0072] In some implementations, the first user is the owner of the first task list, and the owner of the first task list has editing permissions for the first task list.

[0073] In some embodiments, the apparatus further includes: a transfer unit;

[0074] The transfer unit is used to transfer ownership of the first task list to the second user in response to a transfer operation triggered by the first user on the first task list, so that the second user becomes the owner of the first task list.

[0075] In some implementations, the editing permissions include one or more of the following:

[0076] Edit the configuration information corresponding to the first task list, which includes archiving and / or deleting the first task list;

[0077] Edit the tasks included in the first task list.

[0078] In some implementations, the first task list has one or more members, and one of the members has editing or reading permissions for the first task list.

[0079] In some implementations, members of the first task list are added in one or more of the following ways:

[0080] The task list information includes member information. When generating a first task list based on the task list information, members are added to the first task list according to the member information.

[0081] After the first task list is generated, in response to the member addition operation triggered for the first task list, a member is added to the first task list;

[0082] If the first task list is created in the instant messaging session interface, all or part of the session members of the instant messaging session are determined as members of the first task list.

[0083] If the first task list is created in the cloud document interface, all or some of the collaborators in the cloud document interface are identified as members of the first task list.

[0084] In some implementations, the member's editing permissions include one or more of the following:

[0085] Edit the configuration information corresponding to the first task list, wherein editing the configuration information corresponding to the first task list does not include archiving or deleting the first task list;

[0086] Edit the tasks included in the first task list.

[0087] In some implementations, the reading permission includes one or more of the following:

[0088] Read and / or comment on the first task list, but do not edit the configuration information corresponding to the first task list;

[0089] You can read and / or comment on the tasks included in the first task list, but you cannot create or add tasks in the first task list or edit the tasks included in the first task list.

[0090] In some embodiments, the apparatus further includes: a configuration unit;

[0091] The configuration unit is configured to, in response to creating or adding a target task in the first task list, configure permissions for the target task for the members of the first task list based on the permissions the members of the first task list have for the first task list.

[0092] In some implementations, if a member of the first task list has editing permissions for the first task list, then that member has editing permissions for the target task; if a member of the first task list has reading permissions for the first task list, then that member has at least reading permissions for the target task.

[0093] In some embodiments, the apparatus further includes: a processing unit;

[0094] The processing unit is configured to, in response to a task being deleted from the first task list, no longer display the deleted task in the first task list;

[0095] The processing unit is further configured to, in response to the deletion of the first task list, not perform a deletion operation on the tasks in the first task list;

[0096] The processing unit is further configured to, in response to the deletion of the first task list, delete tasks in the first task list that have no responsible person.

[0097] In some embodiments, the apparatus further includes a configuration unit and a modification unit;

[0098] The configuration unit is configured to, by default, grant the associated members of the first business interface a first permission for the first task list if the first task list is created or added in the first business interface; and,

[0099] The modification unit is configured to, in response to an edit operation triggered on the first task list, modify the permissions of the associated member for the first task list to the second permission.

[0100] or,

[0101] The configuration unit is further configured to, if the first task list is created or added in the first business interface, grant permissions to the associated members of the first business interface for the first task list according to the permission configuration operation.

[0102] In some implementations, the first business interface includes: an instant messaging session interface or a cloud document interface.

[0103] When the first business interface is an instant messaging session interface, the associated members of the first business interface are some or all of the corresponding session members.

[0104] When the first business interface is a cloud document session interface, the associated members of the first business interface are some or all of the corresponding cloud document collaborators.

[0105] In some embodiments, the device further includes: a display unit;

[0106] The display unit is configured to display a first prompt message in the first business interface corresponding to one or more of the associated members if the permissions of one or more of the associated members to the first task list are modified to no permission. The first prompt message is used to indicate that there is no permission to access the first task list.

[0107] The display unit is further configured to display a second prompt message in the first business interface if the first task list is deleted, the second prompt message being used to indicate that the first task list has been deleted.

[0108] In some embodiments, the apparatus further includes: a configuration unit;

[0109] The configuration unit is configured to, in response to a third user sharing the first task list with a fourth user, grant the fourth user permissions for the first task list, wherein the fourth user's permissions for the first task list are no higher than the third user's permissions for the first task list.

[0110] In some implementations, if the first task list includes a first member and a first task, the permission that the first member has for the first task is a target permission, which is the greater of the permission corresponding to the role that the first member assumes in the first task and the permission that the first member is granted in the first task list.

[0111] It should be noted that the specific implementation of each unit in this embodiment can be found in the relevant descriptions in the above method embodiments. The division of units in this embodiment is illustrative and only represents a logical functional division; in actual implementation, there may be other division methods. The functional units in this embodiment 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. For example, in the above embodiments, the processing unit and the sending unit can be the same unit or different units. The integrated unit can be implemented in hardware or as a software functional unit.

[0112] See Figure 5 The diagram illustrates a structural schematic of an electronic device 500 suitable for implementing embodiments of the present disclosure. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0113] like Figure 5 As shown, the electronic device 500 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the electronic device 500. The processing unit 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0114] Typically, the following devices can be connected to I / O interface 505: input devices 506 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 507 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 508 including, for example, magnetic tapes, hard disks, etc.; and communication devices 509. Communication device 509 allows electronic device 500 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 5 An electronic device 500 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0115] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 509, or installed from a storage device 508, or installed from a ROM 502. When the computer program is executed by the processing device 501, it performs the functions defined in the methods of embodiments of this disclosure.

[0116] The electronic device provided in this embodiment belongs to the same inventive concept as the method provided in the above embodiments. Technical details not described in detail in this embodiment can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0117] This disclosure provides a computer storage medium storing a computer program that, when executed by a processor, implements the methods provided in the above embodiments.

[0118] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0119] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or future-developed networks.

[0120] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0121] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, enable the electronic device to perform the aforementioned methods.

[0122] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the first user's computer, partially on the first user's computer, as a standalone software package, partially on the first user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer can be connected to the first user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0123] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0124] The units described in the embodiments of this disclosure can be implemented in software or hardware. The names of the units / modules do not necessarily limit the specific unit itself.

[0125] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

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

[0127] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems or apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and relevant parts can be referred to the method section.

[0128] It should be understood that in some embodiments of this disclosure, "at least one item" refers to one or more, and "more than one" refers to two or more. "And / or" describes 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.

[0129] It should also be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0130] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0131] The above description of the disclosed embodiments enables those skilled in the art to make or use this disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for creating a task list, characterized in that, The method includes: Receive the task list creation operation triggered by the first user on the first client interface, and obtain the task list related information input by the first user; A first task list is generated based on the task list information. The first task list is a task container for holding tasks. The first task list does not depend on other entities in the application to which the first client interface belongs. The application is a collaborative office suite application that integrates multiple applications. The client corresponding to the first client interface is the client of any of the multiple applications. The other entities include one or more entities created in the collaborative office suite application, such as groups, teams, documents, meetings, collaboration spaces, departments, and projects. The first task list has one or more members, and one of the members has editing or reading permissions for the first task list. In response to creating or adding a target task in the first task list, permissions for the target task are configured for the members of the first task list based on their permissions to the first task list. In response to the deletion of the first task list, no deletion operation is performed on the tasks in the first task list; The members of the first task list are added in one or more of the following ways: The task list information includes member information. When generating a first task list based on the task list information, members are added to the first task list according to the member information. After the first task list is generated, in response to the member addition operation triggered for the first task list, a member is added to the first task list; If the first task list is created in the instant messaging session interface, all or part of the session members of the instant messaging session are determined as members of the first task list. If the first task list is created in the cloud document interface, all or some of the collaborators in the cloud document interface are identified as members of the first task list.

2. The method according to claim 1, characterized in that, The first client interface can be a task center interface, an instant messaging session interface, a collaboration space interface, or a cloud document interface.

3. The method according to claim 1, characterized in that, The first user is the owner of the first task list, and the owner of the first task list has editing permissions for the first task list.

4. The method according to claim 3, characterized in that, The method further includes: In response to the transfer operation triggered by the first user on the first task list, ownership of the first task list is transferred to the second user, making the second user the owner of the first task list.

5. The method according to claim 3, characterized in that, The editing permissions include one or more of the following: Edit the configuration information corresponding to the first task list, which includes archiving and / or deleting the first task list; Edit the tasks included in the first task list.

6. The method according to claim 1, characterized in that, The editing permissions include one or more of the following: Edit the configuration information corresponding to the first task list, wherein editing the configuration information corresponding to the first task list does not include archiving or deleting the first task list; Edit the tasks included in the first task list.

7. The method according to claim 1, characterized in that, The reading permissions include one or more of the following: Read and / or comment on the first task list, but do not edit the configuration information corresponding to the first task list; You can read and / or comment on the tasks included in the first task list, but you cannot create or add tasks in the first task list or edit the tasks included in the first task list.

8. The method according to claim 1, characterized in that, If a member of the first task list has editing permissions for the first task list, then that member has editing permissions for the target task; If a member of the first task list has reading permission for the first task list, then that member has at least reading permission for the target task.

9. The method according to claim 1, characterized in that, The method also includes one or more of the following: In response to a task being deleted from the first task list, the deleted task is no longer displayed in the first task list; In response to the deletion of the first task list, delete the tasks in the first task list that have no responsible person.

10. The method according to claim 1, characterized in that, The method further includes: If the first task list is created or added in the first business interface, the associated members of the first business interface are granted a first permission for the first task list by default; and, in response to the edit operation triggered for the first task list, the permission of the associated members for the first task list is modified to a second permission. or, If the first task list is created or added in the first business interface, the associated members of the first business interface are granted permissions for the first task list according to the permission configuration operation.

11. The method according to claim 10, characterized in that, The first business interface includes: an instant messaging session interface or a cloud document interface; When the first business interface is an instant messaging session interface, the associated members of the first business interface are some or all of the corresponding session members. When the first business interface is a cloud document session interface, the associated members of the first business interface are some or all of the corresponding cloud document collaborators.

12. The method according to claim 10, characterized in that, The method also includes one or more of the following: If the permissions of one or more of the associated members to the first task list are changed to no permission, a first prompt message is displayed in the first business interface corresponding to one or more of the associated members. The first prompt message is used to indicate that there is no permission to access the first task list. If the first task list is deleted, a second prompt message will be displayed on the first business interface. The second prompt message is used to indicate that the first task list has been deleted.

13. The method according to claim 1, characterized in that, The method further includes: In response to a third user sharing the first task list with a fourth user, the fourth user is granted permissions for the first task list, wherein the fourth user's permissions for the first task list are no greater than the third user's permissions for the first task list.

14. The method according to claim 1, characterized in that, If the first task list includes a first member and a first task, the permission that the first member has for the first task is the target permission, which is the greater of the permission corresponding to the role that the first member assumes in the first task and the permission that the first member is granted in the first task list.

15. A task list creation device, characterized in that, The device includes: The receiving unit is used to receive the task list creation operation triggered by the first user on the first client interface and to obtain the task list related information input by the first user. A generation unit is configured to generate a first task list based on the task list information. The first task list is a task container for holding tasks. The first task list does not depend on other entities in the application to which the first client interface belongs. The application is a collaborative office suite application that integrates multiple applications. The client corresponding to the first client interface is the client of any of the multiple applications. The other entities include one or more entities created in the collaborative office suite application, such as groups, teams, documents, meetings, collaboration spaces, departments, and projects. The first task list has one or more members, and one of the members has editing or reading permissions for the first task list. A configuration unit is configured to, in response to creating or adding a target task in the first task list, configure permissions for the target task for the members of the first task list based on the permissions the members of the first task list have for the first task list. The processing unit, in response to the deletion of the first task list, does not perform a deletion operation on the tasks in the first task list; The members of the first task list are added in one or more of the following ways: The task list information includes member information. When generating a first task list based on the task list information, members are added to the first task list according to the member information. After the first task list is generated, in response to the member addition operation triggered for the first task list, a member is added to the first task list; If the first task list is created in the instant messaging session interface, all or part of the session members of the instant messaging session are determined as members of the first task list. If the first task list is created in the cloud document interface, all or some of the collaborators in the cloud document interface are identified as members of the first task list.

16. An electronic device, characterized in that, The device includes: a processor and a memory; The memory is used to store instructions or computer programs; The processor is configured to execute the instructions or computer program in the memory to cause the electronic device to perform the method according to any one of claims 1-14.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on the device, cause the device to perform the method according to any one of claims 1-14.

Images