Task list creation method, apparatus, device, and medium

Abstract

Embodiments of the present disclosure disclose a task list creation method, apparatus, device, and medium. When a first user triggers a task list creation operation through a first client interface, task list related information input by the first user is obtained. Based on the obtained task list related information, a first task list is generated, and the first task list is a task container. And the first task list may exist independently without depending on other entities in the application to which the first client interface belongs. That is, according to the technical solution of the present disclosure, in the form of creating a task list, scattered tasks can be managed, and the task list can exist independently, thereby facilitating the user's operations on the task list and improving the flexibility of the operations.

Description

Technical Field

[0001] (Reference to Related Applications) This application claims priority to Chinese Patent Applications filed with the Chinese Patent Office on December 16, 2022, with application numbers 202211625719.5, invention title "Task List Creation Method, Apparatus, Device, and Medium", 202211625212.X, invention title "Information Interaction Method, Apparatus, Device, and Medium", and 202211625213.4, invention title "Task List Sharing Method, Apparatus, Device, and Medium", and all of their contents are incorporated herein by reference.

[0002] (Technical Field) The present disclosure relates to the field of computer technology, and more specifically, to a task list creation method, apparatus, device, and medium.

Background Art

[0003] In a collaboration scenario, it is common for a user to receive and process multiple tasks. Generally, multiple tasks are in a scattered state, which is difficult to manage, with low management efficiency and affecting the user experience.

Summary of the Invention

[0004] In view of this, embodiments of the present disclosure provide a task list creation method, apparatus, device, and medium to manage multiple tasks by means of a task list and improve management efficiency and user experience.

[0005] To achieve the above objective, the technical solution according to the present disclosure is as follows.

[0006] In a first aspect of the present disclosure, a task list creation method is provided, and the method includes: Receiving a task list creation operation triggered by a first user at a first client interface, and obtaining task list related information input by the first user; Generating a first task list that is a task container and does not depend on other entities in the application to which the first client interface belongs, based on the task list related information.

[0007] In a second aspect of the present disclosure, a task list creation apparatus is provided, the apparatus including: A receiving unit for receiving a task list creation operation triggered by a first user at a first client interface, and obtaining task list related information input by the first user; A generating unit for generating a first task list that is a task container and does not depend on other entities in the application to which the first client interface belongs, based on the task list related information.

[0008] In a third aspect of the present disclosure, an electronic device is provided, the device including a processor and a memory, The memory is used for storing instructions or computer programs, The processor is used for executing the instructions or computer programs in the memory to cause the electronic device to execute the method described in the first aspect.

[0009] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, instructions are stored on the computer-readable storage medium, and the instructions cause the device to execute the method described in the first aspect on the device.

[0010] In a fifth aspect of the present disclosure, a computer program product is provided, the computer program product includes a computer program / instructions, and when the computer program / instructions are executed by a processor, the method described in the first aspect is realized.

[0011] As can be seen from this, the present disclosure has the following beneficial effects.

[0012] In some embodiments of the present disclosure, when a first user triggers a task list creation operation on a first client interface, task list related information input by the first user is acquired. Based on the acquired task list related information, a first task list is generated, and the first task list is a task container. And the first task list may exist independently without depending on other entities in the application to which the first client interface belongs. That is, according to the technical solution of the present disclosure, in the form of creating a task list, discrete tasks can be managed, and the task list can exist independently, thereby facilitating the user's operations on the task list and improving the flexibility of the operations.

Brief Description of the Drawings

[0013] To more clearly explain the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments described in some embodiments of the present disclosure, and those skilled in the art can obtain other drawings based on these drawings without creative efforts.

[0014]

Figure 1

Figure 2a

Figure 2b

Figure 2c

Figure 3a

Figure 3b

Figure 4

Figure 5

Figure 6a

Figure 6b

Figure 7a

Figure 7b

Figure 7c

Figure 8

Figure 9

Figure 10a

Figure 10b

Figure 10c

Figure 11a

Figure 11b

Figure 11c

Figure 11d

Figure 12a

Figure 12b

Figure 12c

Figure 12d

Figure 13

Figure 14

Embodiments for Carrying Out the Invention

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

[0016] To facilitate the understanding of the technical solutions according to the embodiments of the present disclosure, the following description will be made with reference to the drawings.

[0017] Referring to FIG. 1, which is a flowchart of a task list creation method according to an embodiment of the present disclosure. The method may be executed by a first client, and the first client may be installed on an electronic device. Here, the electronic device may include devices having a communication function such as a mobile phone, a tablet computer, a notebook computer, a desktop computer, an in-vehicle terminal, a wearable electronic device, a multifunctional printer, a smart home device, etc., or may be a device simulated by a virtual machine or a simulator. As shown in FIG. 1, the method may include the following steps.

[0018] S1-101: Receive a task list creation operation triggered by a first user at a first client interface, and obtain task list related information input by the first user.

[0019] In some embodiments of the present disclosure, in order to create a task list, a first user can trigger a task list creation operation at a first client interface. When the first client receives the task list creation operation triggered by the first user, the first client obtains the task list related information input by the first user. Here, the task list related information may include the title of the task list, co-editors corresponding to the task list, and permissions that each co-editor has for the task list, etc.

[0020] Here, the first client is a client of an application with a task list creation function, and the first client interface is the client interface of the application. For example, the first client interface may be a task center interface, an instant messaging session interface, a collaboration space interface, or a cloud document interface, etc. That is, the first user can trigger a task list creation operation in any one of the above interfaces. Specifically, the first client may be a client of a stand-alone application, or a client of an application in a collaborative office suite application. Generally, in a collaborative office suite application, one or more of an instant messaging application and applications such as schedules, tasks, cloud documents, and audio-video conferences are integrated.

[0021] Here, receiving the task list creation operation triggered by the first user on the first client interface and obtaining the 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 the task list related information in response to the input operation triggered by the first user on the creation page. Here, regarding the creation page, the creation page may include a task list title input box and a member addition control. Here, the member addition control is an optional control. If the first user has not triggered the member addition control, members are not added immediately, and members are added further after the task list creation is completed.

[0022] For example, as shown in FIG. 2a, when the first client interface is the task center interface, the task list creation control 1-201 can be displayed in the left area of the task center interface 1-200. After the user triggers the control 1-201, the creation page 1-202 is displayed as shown in FIG. 2b. The creation page 1-202 includes a task list title input box and a member invitation control. The user can enter a title in the task list title input box and, if necessary, select whether to invite members through the member invitation control. Here, when the user enters a title in the task list title input box, if the entered title exceeds a predetermined number of characters, the user can be notified that the characters have already reached the upper limit.

[0023] Here, after the user invites a member through the member invitation control, it can be defaulted that the invited member has the first authority over the created task list. Or, the authority of the invited member can be set. Specifically, overall settings can be made for the invited member, that is, the authorities of all the invited members are the same, or authority settings can be made for each of the invited members.

[0024] S102. Generate a first task list based on the task list related information.

[0025] After obtaining the task list information, a first task list is generated based on the task list related information. Here, the first task list is a task container for accommodating tasks, and one or more tasks may be included in the first task list. In some embodiments, the task list may have a state of including zero tasks. In some embodiments of the present disclosure, tasks may be created in the task list, or existing tasks may be added to the task list. Based on the task list, management and operations may be performed on each task therein. In an embodiment of the present disclosure, the first task list may exist independently without depending on other entities in the application to which the first client interface belongs. For example, in some embodiments of the present disclosure, the task list does not depend on entities such as groups, teams, documents, meetings, collaboration spaces, departments, projects, etc. The application to which the first client interface belongs may be an application for a collaborative office, for example, an application mainly with an IM function, an application mainly with a task function, or an office suite application integrating functions such as IM, tasks, and documents.

[0026] Here, the application to which the first client interface belongs may be an independent IM application, or an independent task application, or a collaborative office suite application integrating multiple applications. Other entities refer to entities created or defined in the application. For example, other entities may be a session group, a team, a collaboration space, etc. created in the application.

[0027] After the creation is completed, the first task list can be displayed on the first client interface. For example, as shown in FIG. 2c, after the creation operation of the first task list (related to the special creativity project) is completed on the task center interface, a task list with the name "related to the special creativity project" can be displayed in the left area of the task center interface 1-200. After the user triggers the "related to the special creativity project" displayed in the left area, the information of the task list, such as the information of each task included in the task list, etc., is displayed in the right area.

[0028] As can be seen from this, when the first user triggers a task list creation operation on the first client interface, the task list-related information input by the first user is obtained. Based on the obtained task list-related information, the first task list is generated, and the first task list is a task container for managing tasks. And the first task list may exist independently without depending on other entities in the application to which the first client interface belongs. That is, according to the technical solution of the present disclosure, in the form of creating a task list, scattered tasks can be managed, and the task list can exist independently, thereby facilitating the user's operation on the task list and improving the flexibility of the operation.

[0029] When creating the first task list, different roles may be configured for the first task list, and the permissions for the first task list vary depending on the roles. For example, the roles in the first task list are divided into two roles: owner and member. The owner of the first task list has editing permission for the first task list, and the member of the first task list has editing permission or viewing permission for the first task list. Both the owner and the member have editing permission for the first task list, but their editing permissions are different.

[0030] Here, the owner's editing authority may include editing the setting information corresponding to the first task list and editing the tasks included in the first task list. Editing the setting information corresponding to the first task list includes the title of the first task list, member editing, archiving of the first task list, deletion of the first task list, etc.

[0031] Here, the member's editing authority means that not only can the first task list be viewed, but also the setting information of the first task list and the tasks included in the first task list can be edited. Here, editing the setting information corresponding to the first task list may include editing the title of the first task list, the members corresponding to the first task list, etc., but does not include archiving of the first task list and deletion of the first task list. Here, the member's viewing authority means that only viewing and / or commenting on the first task list and viewing and / or commenting on the tasks included in the first task list can be done, but the setting information of the first task list cannot be edited, tasks cannot be created or added in the first task list, and the tasks included in the first task list cannot be edited. Here, the editing authority includes the viewing authority.

[0032] Here, the first user is the creator of the first task list, that is, the owner. The editing authority regarding the first task list includes editing the tasks included in the first task list and the setting information corresponding to the first task list. Editing the setting information of the first task list includes archiving of the first task list and deletion of the first task list.

[0033] In some embodiments, the owner of a task list can transfer the ownership of the task list to another user. Specifically, in response to a transfer operation triggered by a first user for a first task list, the ownership of the first task list is transferred to a second user, and the second user becomes the owner of the first task list. Specifically, a transfer control may be displayed on an interface corresponding to the first task list, and in response to a trigger operation of the first user on the transfer control, a transfer interface is displayed. The first user may input or search for a second user who will receive the transfer in the transfer interface. After the second user is found, in response to a confirmation operation triggered by the first user in the transfer interface, the first task list is transferred to the second user, so that the second user becomes the owner of the first task list and has the permissions of the owner. After the transfer is completed, the first user may become a general member of the first task list or may directly exit from the first task list after the transfer.

[0034] Here, there may be one or more members in the first task list, and the one or more members may be added in the following forms.

[0035] One is that when creating the first task list, if member information is included in the task list-related information input by the first user, and when generating the first task list based on the task list-related information, members are added to the first task list based on the member information. That is, when creating the first task list, by adding the corresponding member information, when generating the first task list, members are added to the first task list.

[0036] One is that after generating the first task list, in response to a member addition operation triggered for the first task list, members are added to the first task list. Here, the user who triggers the member addition operation may be the owner of the first task list or may be a member who has editing permissions regarding the first task list, and this embodiment is not limited here.

[0037] One is that when creating a first task list in the instant messaging session interface, all or some members of the instant messaging session are specified as members of the first task list. That is, when creating a first task list in the instant messaging session interface, when creating the first task list, all or some members in the instant messaging session may be specified as members of the first task list. Specifically, when creating the first task list, all members of the instant messaging session may be selected all at once with one click, or the session members to be added may be selected individually by means of the check boxes corresponding to the session members.

[0038] One is that when creating a first task list in the cloud document interface, all or some co-editors of the cloud document interface are specified as members of the first task list. That is, when creating a first task list in the cloud document interface, when creating the first task list, all or some co-editors of the cloud document interface may be specified as members of the first task list. Specifically, when creating the first task list, all members of the cloud document interface may be selected all at once with one click, or the session members to be added may be selected individually by means of the check boxes corresponding to the co-editors.

[0039] Here, after the creation of the first task list is completed, tasks can be newly created or added in the first task list to manage tasks by the first task list. The interface diagram corresponding to the first task list shown in FIG. 3a can display the title of the first task list, shared controls 1-301, independent window 1-302, and task controls 1-303. The shared controls 1-301 can trigger the sharing of the first task list, the independent window 1-302 can trigger the display of the first task list in an independent window, and the task controls 1-303 can create or add new tasks in the first task list. Here, a drop-down menu in the task controls 1-303 can display an add task button. In addition, in the interface shown in FIG. 3a, other operations on tasks, such as filtering, sorting, adding subtasks, etc., can be further displayed.

[0040] In some embodiments, in response to creating or adding a target task in the first task list, permissions for the target task are set for the members of the first task list based on the permissions that the members of the first task list have with respect to the first task list. That is, when creating or adding a target task in the first task list, the permissions of the members of the first task list for the target task are configured based on the permissions that the members of the first task list have with respect to the first task list. For example, if a member of the first task list has editing permissions with respect to the first task list, and the editing permissions include the permission to edit tasks in the first task list, then the member also has editing permissions for the target task. If a member of the first task list has viewing permissions with respect to the first task list, then the member has at least viewing permissions for the target task. Here, having at least viewing permissions means that if the member originally has higher permissions for the target task, the member maintains the original higher permissions. For example, user A is a member of the first task list, has viewing permissions with respect to the first task list, and user A is originally a co-editor of the target task and has editing permissions for the target task. In this case, user A still has editing permissions for the target task added to the first task list. Here, one task can be added to multiple different task lists.

[0041] In some embodiments, the following operations may further exist.

[0042] One is that in response to a task in the first task list being deleted, the deleted task in the first task list is no longer displayed.

[0043] One is that in response to the first task list being deleted, a delete operation is not performed on the tasks in the first task list. That is, when the task list is deleted, the tasks in the task list are not deleted by default.

[0044] One is to delete the tasks without a responsible person in the first task list in response to the deletion of the first task list. That is, when the task list is deleted, the tasks without a responsible person in the task list may be deleted. Specifically, when deleting the task list, the user may be allowed to select whether to delete the tasks without a responsible person in the task list. If the user selects deletion, the tasks without a responsible person are deleted. For example, as shown in FIG. 3b, when the user triggers the deletion of a certain task list, a prompt box may be displayed, and a checkbox may be displayed in the prompt box for the user to select whether to simultaneously delete the tasks without a responsible person in the task list.

[0045] In some embodiments, when creating or adding a first task list in the first service interface, the first permission regarding the first task list is defaultly granted to the related members of the first service interface, and in response to the triggered edit operation on the first task list, the permission of the related members regarding the first task list is changed to the second permission. That is, when the user creates or adds a first task list in the first service interface, the first permission regarding the first task list may be defaultly granted to the related members of the first service interface in advance. During the creation or addition, a permission change operation may be triggered to change the permission of the related members regarding the first task list to the second permission. Or, after the creation or addition is completed, a permission change operation may be triggered to change the permission of the related members regarding the first task list to the second permission.

[0046] In some embodiments, when creating or adding a first task list in a first service interface, based on a permission setting operation, permissions regarding the first task list are granted to relevant members of the first service interface. That is, when creating or adding a first task list in the first service interface, a user may set permissions for relevant members of the first service interface. Specifically, when setting permissions, a unified permission setting may be performed for all relevant members of the first service interface, or different permissions may be set for different relevant members for each member.

[0047] Here, the first permission and the second permission are each one of no access permission, view permission, or edit permission. The first service interface may include an instant messaging session interface or a cloud document interface. When the first service interface is an instant messaging session interface, the relevant members of the first service interface are some or all of the corresponding session members. When the first service interface is a cloud document session interface, the relevant members of the first service interface are some or all of the co - editors of the corresponding cloud document.

[0048] In some embodiments, when changing the permissions regarding the first task list of one or more relevant members to no permission, in the first service interface corresponding to the one or more relevant members, first prompt information is displayed to notify that there is no permission to access the first task list. That is, after changing the permissions regarding the first task list of a relevant member from having access permission to having no access permission, the relevant member can still view the first task list in the first service interface, but cannot check the relevant content of the first task list and can only view the first prompt information.

[0049] Here, there may be multiple forms for presenting the first prompt information. One is to display the first task list according to a predetermined mode, and through the predetermined mode, for example, by graying out the color, notify the user that they do not have access rights. Another is to display the first prompt information when the mouse floats over the first task list. Still another is to display the first prompt information when a related member clicks on the first task list.

[0050] Here, for the convenience of related members to apply for access rights, a control for applying for access rights may be further displayed. In response to a trigger operation on the access right application control of the related member, an application page is displayed, and the owner of the first task list may be displayed on the application page. The related member can apply for access rights to the owner by triggering the send control on the application page.

[0051] When the first task list is deleted, on the first service interface, second prompt information for notifying that the first task list has already been deleted is displayed. That is, after the first task list is deleted, on the first service interface, the second prompt information can be displayed to notify the related members of the first service interface that the first task list has already been deleted. Here, for the form of presenting the second prompt information, reference may be made to the related description regarding the first prompt information described above.

[0052] As can be seen from FIG. 3a, a sharing operation can be further triggered for the first task list. Specifically, in response to the third user sharing the first task list with the fourth user, the permissions regarding the first task list are granted to the fourth user. Here, the permissions that the fourth user has regarding the first task list are not higher than those of the third user regarding the first task list. That is, a user can only spread the highest permissions they have for the first task list they possess. Here, the third user may be the owner of the first task list or a member of the first task list. Specifically, if user A shares a task list with user B and user A only has viewing permissions for the task list, then user B can only obtain viewing permissions for the task list through user A's sharing operation. If user A has editing permissions regarding the task list, when user A shares the task list with user B, user A may grant editing permissions to user B or only grant viewing permissions to user B.

[0053] In some embodiments, when the first task list includes a first member and a first task, the permissions that the first member has regarding the first task are target permissions, and the target permissions are the greater of the permissions corresponding to the role that the first member undertakes in the first task and the permissions that the first member has regarding the first task list granted to the first member. That is, the permissions that a user has regarding a task are equal to the greater value of {the permissions granted by the task role, the permissions granted by the task list}.

[0054] For example, User A has editing rights for Task List 1 (including editing rights for tasks in Task List 1), and at the same time, User A is a follower of Task 1. Followers of a task only have viewing rights for the task and do not have editing rights. When Task 1 is added to Task List 1, since User A has editing rights for the list, User A can edit Task 1. Further, for 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 and gives User A only viewing rights. However, since User A is the person in charge of Task 2, User A has editing rights and can edit Task 2.

[0055] Based on the embodiments of the above method, embodiments of the present disclosure provide a task list creation device and an electronic device, which will be described below with reference to the drawings.

[0056] Referring to FIG. 4, which is a structural diagram of a task list creation device according to an embodiment of the present disclosure. As shown in FIG. 4, device 1-400 includes a receiving unit 1-401 and a generating unit 1-402.

[0057] The receiving unit 1-401 is used to receive a task list creation operation triggered by a first user through a first client interface and obtain task list related information input by the first user. The generating unit 1-402 is used to generate a first task list based on the task list related 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.

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

[0059] In some embodiments, the first user is the owner of the first task list, and the owner of the first task list has editing authority regarding the first task list.

[0060] In some embodiments, the apparatus further includes a transfer unit, The transfer unit is used to transfer the ownership of the first task list to a second user in response to a transfer operation triggered by the first user on the first task list, and make the second user the owner of the first task list.

[0061] In some embodiments, the editing authority includes editing the setting information corresponding to the first task list, including archiving and / or deleting the first task list, and editing one or more of the tasks included in the first task list.

[0062] In some embodiments, there are one or more members in the first task list, and one of the members has editing authority or viewing authority regarding the first task list.

[0063] In some embodiments, the members of the first task list include member information in the task list related information. When generating the first task list based on the task list related information, members are added to the first task list based on the member information, and after generating the first task list, members are added to the first task list in response to a member addition operation triggered on the first task list. When creating the first task list in the instant messaging session interface, identifying all or some of the session members of the instant messaging session as members of the first task list; When creating the first task list in the cloud document interface, it is added in one or more forms of identifying all or some of the co - editors of the cloud document interface as members of the first task list.

[0064] In some embodiments, the editing permissions of the members include editing the setting information corresponding to the first task list, excluding archiving and deleting the first task list; editing the tasks included in the first task list, including one or more of them.

[0065] In some embodiments, the viewing permissions include viewing and / or commenting on the first task list and being unable to edit the setting information corresponding to the first task list; viewing and / or commenting on the tasks included in the first task list, being unable to create or add tasks in the first task list, and being unable to edit the tasks included in the first task list, including one or more of them.

[0066] In some embodiments, the apparatus further includes a setting unit The setting unit is used to set the permissions for the target task for the members of the first task list based on the permissions that the members of the first task list have regarding the first task list in response to newly creating or adding a target task in the first task list.

[0067] In some embodiments, if a member of the first task list has editing authority regarding the first task list, then this member has editing authority regarding the target task, and if a member of the first task list has viewing authority regarding the first task list, then this member has at least viewing authority regarding the target task.

[0068] In some embodiments, the apparatus further includes a processing unit, The processing unit is used to stop displaying the deleted task in the first task list in response to the task in the first task list being deleted. The processing unit is further used to not perform a deletion operation on the tasks in the first task list in response to the first task list being deleted. The processing unit is further used to delete tasks without a responsible person in the first task list in response to the first task list being deleted.

[0069] In some embodiments, the apparatus further includes a setting unit and a modification unit, The setting unit is used to defaultly grant a first authority regarding the first task list to related members of the first service interface when creating or adding the first task list in the first service interface, The modification unit is used to change the authority of the related members regarding the first task list to a second authority in response to an editing operation triggered for the first task list. Or, The setting unit is further used to grant the authority regarding the first task list to related members of the first service interface based on an authority setting operation when creating or adding the first task list in the first service interface.

[0070] In some embodiments, the first service interface includes an instant messaging session interface or a cloud document interface, When the first service interface is an instant messaging session interface, the related members of the first service interface are some or all of the corresponding session members, When the first service interface is a cloud document session interface, the related members of the first service interface are some or all of the corresponding cloud document co - editors.

[0071] In some embodiments, the device further includes a display unit, When the display unit changes the permission regarding the first task list of one or more of the related members without permission, it is used to display first prompt information for notifying that there is no permission to access the first task list in the first service interface corresponding to one or more of the related members, The display unit is further used to display second prompt information for notifying that the first task list has already been deleted in the first service interface when the first task list is deleted.

[0072] In some embodiments, the device further includes a setting unit, The setting unit is used to grant the fourth user the permission regarding the first task list in response to the third user sharing the first task list with the fourth user, and the permission that the fourth user has regarding the first task list is not higher than the permission that the third user has regarding the first task list.

[0073] In some embodiments, when the first task list includes a first member and a first task, the authority that the first member has with respect to the first task is a target authority, and the target authority is the greater of the authority corresponding to the role that the first member undertakes in the first task and the authority that the first member has with respect to the first task list granted to the first member.

[0074] It should be noted that for the specific implementation of each unit in this embodiment, reference may be made to the relevant descriptions in the above method embodiments. In the embodiments of the present disclosure, the division of units is exemplary and is merely a logical function division. When actually implemented, there may be other division forms. Each functional unit in the embodiments of the present disclosure may be integrated into one processing unit, each unit may physically exist alone, or two or more units may be integrated into one unit. For example, in the above embodiments, the processing unit and the sending unit may be the same unit or different units. The above integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0075] In a collaboration scenario, it is often necessary for a user to receive and process multiple tasks. Generally, since multiple tasks are distributed separately, the management efficiency is low, which affects the user experience. How to facilitate the user's management of tasks is an urgent technical problem to be solved.

[0076] To facilitate task management, tasks are managed in the form of constructing a task list. However, the form in which the user obtains the task list is relatively complex and affects the user experience. To facilitate the user's ability to examine the same task list in different sessions, embodiments of the present disclosure further provide an information interaction method. The user can add the same task list as a session tab to different sessions, and the multiple different sessions may be sessions having a first association relationship or sessions having no association relationship, thereby facilitating the user's examination of the task list.

[0077] To facilitate understanding of the technical solution according to the embodiments of the present disclosure, the following will be described with reference to the drawings.

[0078] Referring to FIG. 5, which is a flowchart of an information interaction method according to an embodiment of the present disclosure. As shown in FIG. 5, the method may be executed by an instant messaging client, and the instant messaging client may be installed on an electronic device. Here, the electronic device may include devices having a communication function such as a mobile phone, a tablet computer, a notebook computer, a desktop computer, an in-vehicle terminal, a wearable electronic device, a multifunctional printer, a smart home device, etc., or may be a device simulated by a virtual machine or a simulator. As shown in FIG. 1, the method may include the following steps.

[0079] S2-101: In response to an operation of adding a first task list as a session tab triggered at the interface of a first session, add a first session tab corresponding to the first task list at the interface of the first session.

[0080] In this embodiment, the user can trigger an operation to add a first task list as a session tab in the interface of the first session. After receiving the above operation, the instant messaging client adds a first session tab corresponding to the first task list in the interface of the first session. Here, the first task list has already been added as a session tab of the second session, and the session tab corresponding to the first task list in the interface of the second session is the second session tab, and there is no relationship between the first session and the second session, or the first session and the second session have a first relationship. That is, the user can not only add the same task list as a session tab to multiple sessions having a first relationship, but also add it to multiple sessions having no relationship.

[0081] In some embodiments of the present disclosure, the fact that there is no relationship between the first session and the second session means that there is no subordinate relationship between the first session and the second session, and neither the first session nor the second session is subordinate to the same other entity (for example, group, team, workspace, department, project, etc.). For example, it may mean that the first session and the second session are not sessions in the same team or workspace. As can be seen from this, in these embodiments, the task list can be flexibly and freely added to the session tab of any session.

[0082] In some embodiments of the present disclosure, the fact that the first session and the second session have a first relationship may mean that the first session and the second session are subordinate to the same other entity (for example, group, team, workspace, department, project, etc.).

[0083] Here, the tab name of the first session tab and the tab name of the second session tab may be the same or different. For example, when both use the title of the first task list as the tab name of the session tab, the tab name of the first session tab and the tab name of the second session tab are the same. Or, when adding the first task list as a session tab, the name of the session tab can be re-edited, and in this case, the tab name of the first session tab and the tab name of the second session tab may be different.

[0084] Here, in the interface of the first session, when triggering to add the first task list as a session tab, the first task list may be an existing task list or a task list newly created when adding a session tab. The following will explain the different cases.

[0085] If the first task list does not exist before adding the first session tab corresponding to the first task list in the interface of the first session, in response to the trigger operation on the first addition control in the interface of the first session, display the first interface for adding a session tab corresponding to the task list, create the first task list in response to the task list creation operation triggered on the first interface, and add the first session tab corresponding to the first task list in the interface of the first session.

[0086] In this embodiment, if there is no first task list before adding the first session tab in the interface of the first session, the user can trigger the first additional control in the interface of the first session, and the first additional control is used to trigger the display of the first interface, and the first interface is used to add a session tab corresponding to the task list. After the user triggers the task list creation operation on the first page, a first task list is created, and at the same time, a first session tab corresponding to the first task list is added in the interface of the first session.

[0087] If the first task list already exists before adding the first task list tab in the interface of the first session, in response to the trigger operation on the first additional control in the interface of the first session, the first interface for adding a session tab corresponding to the task list is displayed, and in response to the operation of adding the existing first task list triggered on the first interface, a first session tab corresponding to the first task list is added in the interface of the first session.

[0088] In this embodiment, if the first task list already exists before adding the first session tab in the interface of the first session, after the user performs a trigger operation on the first additional control in the interface of the first session, the first interface is displayed. After the user triggers the operation of adding the existing first task list in the first interface, a first session tab is added in the interface of the first session.

[0089] Here, in response to a trigger operation on the first additional control in the interface of the first session, displaying the first interface may include displaying a first window including a tab addition control in response to a trigger operation on the first control in the interface of the first session, displaying a second window including a task list tab addition control in response to a trigger operation on the tab addition control, displaying a second window including a task list tab addition control in response to a trigger operation on the tab addition control, and displaying the first interface in response to a trigger operation on the task list tab addition control.

[0090] Specifically, in the application scenario shown in FIG. 6a, after the user performs a trigger operation on the first control 2-201 in the interface 2-200 of the first session, the first window 2-202 is displayed, and the first window 2-202 includes a tab addition control and a management tab. In response to a trigger operation on the tab addition control by the user, the second window 2-203 is displayed, and the second window 2-203 includes a link control, a cloud document control, a task list control (task list tab addition control), and a calendar control. In response to a trigger operation on the task list control by the user, the first interface 2-204 is displayed. The first interface 2-204 may include an existing task list addition control 2-205 and a task list creation control 2-206. The user can select the trigger of the existing task list addition control 2-205 or the task list creation control 2-206 according to his own needs.

[0091] Here, the existing task list addition control and the new task list creation control in the first interface 2-204 may be displayed horizontally in the interface. As shown in FIG. 6b, the user can display the corresponding interfaces of different controls in the first interface 2-204 in a switching form.

[0092] Specifically, after the user triggers the existing task list addition control, the operation interface corresponding to the control is displayed. In the operation interface, the user can search for the existing task list to be added in the form of inputting / pasting the link of the existing task list or directly searching. At the same time, the user can further input the tab name of the first session tab on the operation page. Here, when setting the tab name, it may be set as an option. When the user does not input the tab name, the title of the searched task list is used as the tab name of the first session tab. After the user completes the operation in the operation interface, the addition control in the first interface 2-204 is clicked to add the first session tab in the interface 2-200 of the first session. Here, when the user searches for the task list, the task list with access rights can be searched, and the task list without access rights cannot be searched and received. Here, the access rights may include the editing right and the viewing right. That is, the user can add the task list with access rights as a session tab to the interface of the session.

[0093] After the user triggers the task list new creation control, an operation interface corresponding to the control is displayed. In this operation interface, the user can input the title of the newly created task list. After the input is completed, in response to the trigger operation on the user's creation control, a first task list is created, and at the same time, a first session tab is added in the interface 2-200 of the first session. In this case, the tab name of the first session tab may be the title of the first task list. Alternatively, the operation interface may further include one input box, and this input box is used for the user to define the tab name of the first session tab.

[0094] Here, the interface of the first session includes a session message display area and a non-session message display area. The first session tab is displayed in the first display area of the non-session message display area, and the second display area of the non-session message display area is used to display the basic information and / or basic function menu of the first session. Here, the basic information may include the avatar of the first session, the session name, the number of members included in the session, etc.

[0095] For example, as shown in FIG. 7a, the interface of the first session includes a session message display area 2-301 and a non-session message display area 2-302. The non-session message display area 2-302 includes a first display area 2-3021 and a second display area 2-3022 (a partial display area of the second display area). In the first display area 2-3021, additional session tabs, such as a message tab and a task list tab "Product Release Plan", can be displayed. In the second display area 2-3022, a basic function menu of the session is displayed, and the basic function menu may include a search control 2-303, a multimedia control 2-304, and a calendar control 2-305. Here, the multimedia control can realize video calls and voice calls. Note that FIG. 7a is only an example for easy understanding, and the second display area is the remaining other display area of the non-session message display area excluding the first display area.

[0096] Here, when the first session tab is displayed in the interface of the first session, a predetermined identifier corresponding to the task type can also be displayed, thereby facilitating the user to quickly recognize that the session tab is a tab of the task list by the predetermined identifier. In FIG. 7a, when the task list tab "Product Release Plan" is displayed, the corresponding predetermined identifier is displayed.

[0097] S2-102: In response to a trigger operation on the first session tab in the interface of the first session, display the first task list.

[0098] In this embodiment, after receiving a trigger operation on the first session tab in the interface of the user's first session, the instant messaging client displays the first task list so that the user can check the related information of the first task list.

[0099] Here, the task list is a task container, and one or more tasks may be included in the task list. In some embodiments, tasks can be created in the task list, existing tasks can be added to the task list, and based on the task list, management and operations can be performed on each task therein. In some embodiments, the task list may exist independently without depending on other entities in the client. For example, the task list does not depend on entities such as groups, teams, documents, meetings, collaboration spaces, departments, projects, etc. The client may be an application for a collaborative office, such as an application mainly with an IM function, an application mainly with a task function, or a suite application integrating functions such as IM, tasks, and documents.

[0100] When specifically implemented, the first task list may be displayed in the following form. Specifically, it is as follows. In response to a trigger operation on the first session tab in the interface of the first session, the first task list is displayed in the interface of the first session. That is, the related information of the first task list is displayed in the interface of the first session. Specifically, the related information of the first task list is displayed in the session message display area. Or, in response to a trigger operation on the first session tab in the interface of the first session, the first task list is displayed in a third window independent of the interface of the first session. That is, after the user triggers the first session tab, the related information of the first task list can be displayed by an independent window.

[0101] Here, as shown in FIG. 3b, the related information of the first task list can display the included tasks, the creator of each task, the deadline, and the subtasks included in each parent task, etc.

[0102] In some embodiments, in response to triggering a predetermined operation on the first session tab in the interface of the first session, a fourth window is displayed. Here, the fourth window may include one or more of an open control for opening a task list in the task center, a copy control for copying a link of the first task list, an edit control for editing the tab name of the first session tab, and a delete control for removing the first session tab from the interface of the first session. Here, the predetermined operation may be set according to the actual situation. For example, the predetermined operation may be a double-click operation, a right-click operation, or the like.

[0103] For example, as shown in FIG. 7c, after the user selects the first session tab and triggers a right-click operation, the fourth window 2-306 is displayed. The fourth window 2-306 includes an open control, a link copy control, an edit control, and a delete control.

[0104] In some embodiments, in response to adding a first session tab corresponding to the first task list in the interface of the first session, the first authority regarding the first task list is granted to all or some of the members in the first session. That is, when adding a first session tab in the interface of the first session, all or some of the session members in the first session can be added as co-editors of the first task list, and further, the first authority can be assigned to the co-editors.

[0105] Here, the first permission may be a viewing permission or an editing permission. The editing permission means that not only can the first task list be viewed, but also the setting information of the first task list can be edited and the tasks included in the first task list can be edited. Here, editing the setting information corresponding to the first task list may include editing the title of the first task list, the members corresponding to the first task list, etc., but does not include archiving the first task list and deleting the first task list. Here, the viewing permission means that only the viewing and / or commenting of the first task list and the viewing and / or commenting of the tasks included in the first task list can be performed, but the setting information of the first task list cannot be edited, tasks cannot be created or added in the first task list, and the tasks included in the first task list cannot be edited. Here, the editing permission includes the viewing permission.

[0106] Here, the first permission may be the default permission, or the permission after the user edits the default permission when adding co - editors. This embodiment is not limited thereto.

[0107] In some embodiments, before granting the first permission regarding the first task list to the members in the first session, a permission editing control is provided, and based on the operations of the user on the permission editing control, the first permission regarding the first task list is granted to all or some of the members in the first session. That is, when adding a first session tab in the interface of the first session, a permission editing control is provided to the user, and when further adding the first session tab, the first permission regarding the first task list can be granted to all or some of the members in the first session.

[0108] In some embodiments, after adding a first session tab corresponding to a first task list in the interface of the first session, in response to an edit operation triggered for the first session tab, the permissions of all or some members in the first session regarding the first task list are changed to second permissions. That is, after adding the first session tab in the interface of the first session, the permissions of all or some members in the first session regarding the first task list can be changed. For example, when adding the first session tab, the permissions regarding the first task list granted to all or some members in the first session are viewing permissions, and through an edit operation triggered for the first session tab, the permissions of all or some members in the first session regarding the first task list can be changed from viewing permissions to editing permissions.

[0109] In some embodiments, when removing the first session tab from the interface of the first session, the permissions of all or some members in the first session regarding the first task list can perform the following processing.

[0110] One is to maintain the access permissions of all or some members in the first session to the first task list when removing the first session tab from the interface of the first session.

[0111] One is to revoke the access permissions of all or some members in the first session to the first task list when removing the first session tab from the interface of the first session.

[0112] When removing the first session tab from the interface of the first session, browsing permissions for the first task list are granted to all or some of the members in the first session. In this case, mainly, before removing the first session tab, the permissions of all or some of the members in the first session regarding the first task list are editing permissions, and when removing the first session tab from the interface of the first session, it means changing the permissions of all or some of the members in the first session regarding the first task list to browsing permissions.

[0113] Embodiments of the present disclosure provide an information interaction method, apparatus, device, and medium to facilitate a user to quickly check a task list in a session by adding the task list to a session tab. As can be seen, according to the technical solution of the embodiments of the present disclosure, when receiving a trigger operation to add a first task list as a session tab triggered by the user at the interface of the first session, a first session tab corresponding to the first task list is added at the interface of the first session. Here, the first task list has already been added as a session tab of the second session, and the session tab corresponding to the first task list at the interface of the second session is the second session tab. The first session and the second session may or may not have a first association relationship. That is, the same task list can be added to the tabs of multiple sessions with or without a first association relationship. In response to a trigger operation on the first session tab at the interface of the first session, the first task list is displayed. Here, the first task list may include one or more tasks. That is, according to the embodiments of the present disclosure, one task list can be added to the tabs of multiple sessions with or without a first association relationship, thereby enabling the user to check the task list through the session tab in different sessions and enhancing the user experience.

[0114] Based on the embodiments of the above method, embodiments of the present disclosure provide an information interaction device and an electronic device, which will be described below with reference to the drawings.

[0115] Referring to FIG. 8, which is a structural diagram of an information interaction device according to an embodiment of the present disclosure. As shown in FIG. 8, the device 2-400 may include an additional unit 2-401 and a display unit 2-402.

[0116] The additional unit 2-401 is used to add a first session tab corresponding to the first task list in the interface of the first session in response to an operation of adding the first task list as a session tab triggered at the interface of the first session. Here, the first task list has already been added as a session tab of a second session, and the session tab corresponding to the first task list in the interface of the second session is a second session tab. The first session and the second session have a first association relationship or no association relationship. The display unit 2-402 is used to display the first task list in response to a trigger operation on the first session tab in the interface of the first session.

[0117] In some embodiments, the device further includes a setting unit. The setting unit is used to grant a first permission regarding the first task list to all or some members in the first session in response to adding a first session tab corresponding to the first task list in the interface of the first session.

[0118] In some embodiments, the device further includes a setting unit and a modification unit. Before granting the members in the first session the first authority regarding the first task list, the setting unit provides authority editing control and is used to grant the first authority regarding the first task list to all or some of the members in the first session based on the user's operation on the authority editing control. After adding a first session tab corresponding to the first task list in the interface of the first session, the modification unit is used to change the authority regarding the first task list of all or some of the members in the first session to a second authority in response to an editing operation triggered on the first session tab.

[0119] In some embodiments, the interface of the first session includes a session message display area and a non-session message display area. The first session tab is displayed in a first display area of the non-session message display area, and the second display area of the non-session message display area is used to display basic information and / or basic function controls of the first session.

[0120] In some embodiments, specifically, when the first task list does not exist before adding a first session tab corresponding to the first task list in the interface of the first session, the adding unit 2-401 displays a first interface for adding a session tab corresponding to the task list in response to a trigger operation on a first adding control in the interface of the first session, creates the first task list in response to a task list creation operation triggered on the first interface, and is used to add the first session tab corresponding to the first task list in the interface of the first session, or Specifically, when the first task list already exists before adding the first task list tab in the interface of the first session, the additional unit 2-401 is used to display a first interface for adding a session tab corresponding to the task list in response to a trigger operation on a first additional control in the interface of the first session, and in response to an operation of adding the existing first task list triggered on the first interface, add the first session tab corresponding to the first task list in the interface of the first session.

[0121] In some embodiments, specifically, in response to a trigger operation on a first control in the interface of the first session, the additional unit 2-401 is used to display a first window including a tab addition control, and in response to a trigger operation on the tab addition control, display a second window including a task list tab addition control, and is used to display a first interface in response to a trigger operation on the task list tab addition control.

[0122] In some embodiments, specifically, the display unit 2-402 is used to display the first task list in the interface of the first session in response to a trigger operation on the first session tab in the interface of the first session, or Specifically, the display unit 2-402 is used to display the first task list in a third window independent of the interface of the first session in response to a trigger operation on the first session tab in the interface of the first session.

[0123] In some embodiments, further, the display unit 2-402 is used to display a fourth window in response to triggering a predetermined operation on the first session tab in the interface of the first session. The fourth window includes an open control for opening the task list in the task center, a copy control for copying the link of the first task list, an edit control for editing the tab name of the first session tab, and one or more controls of a delete control for removing the first session tab from the interface of the first session.

[0124] In some embodiments, the display form of the first session tab includes a predetermined identifier corresponding to the task type.

[0125] In some embodiments, the apparatus further includes a processing unit, when the processing unit removes the first session tab from the interface of the first session, it is used to maintain the access rights of all or some members in the first session to the first task list, or when the processing unit removes the first session tab from the interface of the first session, it is used to revoke the access rights of all or some members in the first session to the first task list, or when all or some members in the first session have editing rights regarding the first task list, after the processing unit removes the first session tab from the interface of the first session, it is used to grant the viewing rights of all or some members in the first session to the first task list.

[0126] Note that for the specific implementation of each unit in this embodiment, reference may be made to the relevant descriptions in the embodiments of the above method. In the embodiments of the present disclosure, the division of units is exemplary and is merely a logical functional division. When actually implemented, there may be other division forms. Each functional unit in the embodiments of the present disclosure may be integrated into one processing unit, each unit may physically exist alone, or two or more units may be integrated into one unit. For example, in the above embodiment, the processing unit and the sending unit may be the same unit or different units. The above integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0127] In a collaboration scenario, it is common for a user to need to receive and process multiple tasks. Generally, multiple tasks are in a scattered distribution state, which is inconvenient to manage and affects the user experience. How to effectively manage tasks is a technical problem that needs to be solved urgently.

[0128] In the embodiments of the present disclosure, in order to facilitate task management, multiple tasks are managed in the form of creating a task list. Considering that many collaborations currently occur in sessions or cloud documents, in order to facilitate collaboration, by sharing the task list, in different collaboration scenarios, the task list can be viewed, and collaboration by users can be facilitated.

[0129] According to this, embodiments of the present disclosure further provide a task list sharing method. First, in response to a sharing operation triggered by a first user for a target task list, the access rights that a second user corresponding to the sharing operation has regarding the target task list are identified. After identifying the access rights that the second user has regarding the target task list, based on the access rights, in the display interface corresponding to the sharing operation of the second user, preview data corresponding to the target task list is displayed, so that the second user can directly view relevant information of the target task list through the display interface, enhancing the user experience.

[0130] To facilitate understanding of the technical solution according to the embodiments of the present disclosure, the following will be described with reference to the drawings.

[0131] Referring to FIG. 9, this figure is a flowchart of a task list sharing method according to an embodiment of the present disclosure. The method may be executed by a client, and the client may have a task list creation and / or sharing function and be installed on an electronic device. Here, the electronic device may include devices with a communication function such as a mobile phone, a tablet computer, a notebook computer, a desktop computer, an in-vehicle terminal, a wearable electronic device, a multifunction printer, a smart home device, etc., or may be a device simulated by a virtual machine or a simulator. As shown in FIG. 9, the method may include the following steps.

[0132] S3-101: In response to a sharing operation triggered by a first user for a target task list, the access rights that a second user corresponding to the sharing operation has regarding the target task list are identified.

[0133] In this embodiment, when the first user triggers a sharing operation on the target task list, the access rights that the user who is the sharing partner (the second user) has regarding the target task list are identified. Here, the first user can trigger a sharing operation on any one client interface including the target task list, for example, a task center interface, an instant messaging session interface, a collaboration space interface, a cloud document interface, and the like.

[0134] In one embodiment of the present disclosure, in response to the sharing operation triggered by the first user on the target task list, identifying the access rights that the second user corresponding to the sharing operation has regarding the target task list includes: in response to the operation of copying the link of the target task list triggered by the first user, obtaining the link of the target task list; and in response to the sharing operation triggered by the first user on the link of the target task list, identifying the access rights that the second user corresponding to the sharing operation has regarding the target task list. That is, the first user can realize the sharing of the target task list in the form of copying the link of the target task list.

[0135] Here, the access rights that the second user has regarding the target task list are not higher than the access rights that the first user has regarding the target task list. That is, when the first user shares the target task list, the spread access rights cannot exceed the access rights that the first user himself / herself has. For example, when the first user has the right to view the target task list, the second user can have the right to view the target task list; when the first user has the right to edit the target task list, the second user can have the right to view or edit the target task list; when the first user has no access rights to the target task list, the third user also has no access rights to the target task list.

[0136] Here, the access right includes an editing right and a viewing right. The editing right means that not only can the target task list be viewed, but also the setting information of the target task list can be edited and the tasks included in the target task list can be edited. Here, editing the setting information corresponding to the target task list may include editing the title of the target task list, the members corresponding to the target task list, etc. Here, the viewing right means that only the viewing and / or commenting of the target task list and the viewing and / or commenting of the tasks included in the target task list can be performed, but the setting information of the target task list cannot be edited, tasks cannot be created or added to the target task list, and the tasks included in the target task list cannot be edited. Here, the editing right includes the viewing right.

[0137] In some embodiments, when the first user has the editing right regarding the target task list, before sharing the target task list with the second user, an editing interface for editing the access right that the second user has regarding the target task list is displayed. That is, before sharing the target task list with the second user, the first user can edit the access right that the second user has regarding the target task list.

[0138] When the first user has the editing right regarding the target task list, after sharing the target task list with the second user, in response to an editing operation triggered by the first user, the access right that the second user has regarding the target task list is changed. That is, after sharing the target task list with the second user, the first user can change the access right that the second user has regarding the target task list.

[0139] That is, when the first user shares the target task list with the second user or after sharing, the second user can change the access rights they have regarding the target task list, thereby providing different operation modes for the user and enhancing the convenience of operation.

[0140] Specifically, when the first user triggers a sharing operation for the target task list, in the sharing interface, the user (the second user) who is the sharing partner can be selected, and the access rights that the second user has regarding the target task list can be edited. For the sake of easy understanding, an example will be given where the first user triggers a sharing operation in the task center interface.

[0141] Referring to FIG. 10a, a target task list with the title "Related to the Creativity Special Project" is displayed in the task center interface. The first user can display the sharing interface 3 - 300 by triggering the sharing control. In the sharing interface 3 - 300, the first user can search for information such as the user or group that is the sharing partner, or enter the selection interface 3 - 400 by triggering the "+" control. With the selection interface 3 - 400, a single user or group in the organizational architecture can be selected.

[0142] After the user identifies the sharing partner user by means of the sharing interface 3-300 or the selection interface 3-400, in the sharing interface 3-300, the user identifier of the selected second user can be displayed, and the user identifier may include a user avatar and a user name. Here, for the selected second user, default access rights to the target task list, such as viewing rights, can be granted to the second user. Alternatively, at the time of the sharing operation, the access rights that the second user has with respect to the target task list are set. For example, as shown in FIG. 10b, in the invitation box, while displaying the user identifiers of the selected plurality of second users, the access rights to the target task list of the plurality of second users can be set. In this case, the access rights corresponding to the plurality of second users are the same, specifically, they may be viewable rights or editable rights. Alternatively, as shown in FIG. 10c, the user identifiers of the selected plurality of second users are displayed in a column, and the first user can set the access rights for each of the plurality of second users, thereby setting different access rights for different second users.

[0143] After setting the access rights corresponding to each second user by means of the sharing interface 3-300, when a transmission control is triggered, the target task list is shared with the display interface corresponding to each second user.

[0144] Here, after the first user shares the target task list with the second user by means of the task center interface, the second user can check the target task list in the corresponding task center interface, and / or the second user can check the target task list in the session interface established with the first user.

[0145] S3-102: Based on the access rights, display preview data corresponding to the target task list in the display interface corresponding to the sharing operation of the second user.

[0146] After completing the sharing operation, based on the access rights, the client displays the preview data corresponding to the target task list in the display interface corresponding to the sharing operation of the second user. That is, when the second user has access rights regarding the target task list or does not have access rights, the preview data that the second user can see in the display interface is different.

[0147] Here, in the scenario where the first user shares the target task list in the first session, the display interface corresponding to the sharing operation of the second user is the interface of the first session, and both the first user and the second user are members of the first session. Or, in the scenario where the first user shares the target task list in the first cloud document, the display interface corresponding to the sharing operation of the second user is the cloud document interface of the first cloud document, and both the first user and the second user are co-editors of the first cloud document. Specifically, when the first user shares the target task list, all or some of the members in the first session can be selected for sharing, or all or some of the co-editors in the first cloud document can be selected for sharing, and this embodiment does not limit this.

[0148] In this embodiment, the task list is a task container for accommodating tasks. One or more tasks may be included in the task list. In some embodiments, the task list may have a state of including zero tasks. In some embodiments, tasks can be created in the task list, existing tasks can be added to the task list, and based on the task list, management and operations can be performed on each task therein. In some embodiments, the task list may exist independently without depending on other entities in the client. For example, the task list does not depend on entities such as groups, teams, documents, meetings, collaboration spaces, departments, projects, etc. The client may be an application for a collaborative office, such as an application mainly with an IM function, an application mainly with a task function, or an office suite application integrating functions such as IM, tasks, and documents.

[0149] In some embodiments, the user can trigger an operation to add a target task list as a session tab in the session interface. Specifically, the user can add the same task list as a session tab to multiple sessions that have no association, or add the same task list as a session tab to multiple sessions that have a specific association.

[0150] Here, the fact that there is no relationship between multiple sessions means that there is no subordinate relationship between the multiple sessions, and the multiple sessions do not belong to the same other entity (such as a group, team, workspace, department, project, etc.). For example, it may mean that the first session and the second session are not sessions in the same team or workspace. As can be seen from this, in these embodiments, the task list can be flexibly and freely added to the session tab of any session. The fact that there is a specific relationship between multiple sessions may mean that the multiple sessions belong to the same other entity (such as a group, team, workspace, department, project, etc.).

[0151] Embodiments of the present disclosure provide a task list sharing method, apparatus, device, and medium to quickly share a task list with different users, facilitate different users to check the task list, and enhance the user experience. As can be seen from this, when the first user receives a sharing operation triggered for the target task list, the access permission that the second user corresponding to the sharing operation has for the target task list is determined. Here, the second user is the user who is the sharing partner. After determining the access permission that the second user has for the target task list, based on the access permission, preview data corresponding to the target task list is displayed in the display interface corresponding to the sharing operation of the second user. That is, according to the technical solution of the embodiments of the present disclosure, the task list can be shared. When sharing, first, the access permission that the user who is the sharing partner has for the task list is determined, and further, based on the access permission, the preview data of the task list is displayed in the display interface corresponding to the user who is the sharing partner, thereby facilitating different users to check the information of the task list and enhancing the user experience.

[0152] In some embodiments, in response to a trigger operation on the target task list in the display interface of the second user, an independent window is displayed, and information in the target task list is displayed in the independent window.

[0153] Here, when the second user has access rights regarding the target task list, the preview data includes at least one or more of the title of the target task list, the owner identifier of the target task list, the co - editor identifier of the target task list, and the access right information possessed by the second user. Here, the co - editor of the target task list, that is, a member of the target task list, can view or edit the target task list. When the second user does not have access rights regarding the target task list, the preview data includes first prompt information and a first control. Here, the first prompt information is used to notify that there is no access right regarding the target task list, and the first control is used to apply for access rights.

[0154] In some embodiments, when the second user has access rights regarding the target task list and the target task list includes tasks that have passed the deadline, the preview data may include related information of the tasks that have passed the deadline. In some examples, the related information of the tasks that have passed the deadline may include the number of tasks that have passed the deadline, and / or the preview data includes related information of at least some of the tasks in the target task list, and the related information of the at least some of the tasks may include task titles, creators, due times, and the number of subtasks included in the parent task, etc.

[0155] In some embodiments, when the second user has access rights regarding the target task list, the preview data includes one or more of the following controls: a second control for opening the target task list in the task center interface; a third control for adding the target task list as a session tab of the session interface when the display interface corresponding to the second user is the session interface; and a fourth control for copying the link of the target task list.

[0156] Since the fourth control can copy the link of the target task list, the sharing operation triggered by the first user for the target task list may be performed by triggering the fourth control. Specifically, in response to the first user's trigger operation on the fourth control, the link of the target task list is obtained, and in response to the sharing operation triggered by the first user on the link of the target task list, the access rights that the second user corresponding to the sharing operation has regarding the target task list are identified. Specifically, the first user can send the link of the target task list in a form of copying the link to the same session where both the first user and the second user are located, or paste the link of the target task list into the same cloud document where both the first user and the second user are co - editors.

[0157] Here, when the client displays the preview data corresponding to the target task list in the interface corresponding to the second user's sharing operation based on the access rights, the preview data may be displayed in the form of a preview card. Specifically, in the display interface corresponding to the second user's sharing operation, a preview card of the target task list is displayed, and the preview data is carried by the preview card.

[0158] For example, as shown in FIG. 11a, in the session interface corresponding to the second user, the target task list is shared, and the preview data corresponding to the target task list is displayed on the preview card 3-300. Specifically, it includes the title of the target task list, "Go, go, go", the creator, the number of tasks past the deadline, the co-editor identifier, and relevant information of some of the included tasks. Since the second user has the permission to view the target task list, the second control 3-301, the third control 3-302, and the fourth control 3-303 can be displayed on the preview card 3-300.

[0159] In some embodiments, when the target task list is an empty task list (a task list without tasks), the display form of the preview card, as shown in FIG. 11b, displays the title of the target task list, "Go, go, go", the creator, the co-editor identifier, and the blank document icon. Since the second user has the permission to view the target task list, the second control, the third control, and the fourth control can be displayed on the preview card.

[0160] In some embodiments, when the target task list is deleted, the second prompt information for notifying that the target task list has been deleted can be displayed on the preview card. After the target task list is deleted, the display form of the preview card, as shown in FIG. 11c, can still display the viewing permission of the second user and the fourth control.

[0161] If the second user does not have access rights to the target task list, the display form of the preview card is as shown in Fig. 11d, and it displays the first prompt information "You do not have access rights", the first control 3-304, and the fourth control 3-303. Here, through the first control 3-304, the user can apply for access rights to the owner of the target task list. After the user triggers the first control 3-304, an access application interface can be displayed. As shown in Fig. 12a, in the access application interface 3-400, the user can change to apply for viewing rights or editing rights, and can further input remarks information in the input box displayed in the interface 3-400.

[0162] After the user sends an access application to the owner of the target task list, the client can send a notification message to the owner to notify the owner that there is a user who has applied for access rights to the target task list. For example, as shown in Fig. 12b, the task assistant can automatically send a notification message, and in this notification message, the user identifier of the applicant, the title of the target task list, remarks information, an approval control, and a rejection control can be displayed. Regardless of which control the owner triggers, a notification message is sent to the applicant to inform the application result. When the owner triggers the approval control, the notification message sent to the applicant is as shown in the upper figure in Fig. 12c, and when the owner triggers the rejection control, the notification message sent to the applicant is as shown in the lower figure in Fig. 12c.

[0163] In some embodiments, when a first user examines a task list preview card, a preview card of a target task list is displayed in an interface corresponding to the sharing operation of the first user, and the preview card includes a fifth control for changing the access right of a second user to the target task list. For example, as shown in FIG. 12d, when a user sharing a target task list examines the preview card of the target task list through a session interface, the fifth control 3-305 is displayed, and the access right of a member in the session to the target task list can be changed by the fifth control 3-305.

[0164] In this embodiment, the second user can further obtain a link to the target task list by triggering a fourth control displayed on the preview card of the target task list, and by re-sharing the target task list, more users can examine relevant information of the target task list.

[0165] Based on the embodiments of the above method, embodiments of the present disclosure further provide a task list sharing device and an electronic device, which will be described below with reference to the drawings.

[0166] Referring to FIG. 13, the figure is a structural diagram of a task list sharing device according to an embodiment of the present disclosure. As shown in FIG. 13, the sharing device 3-500 may include a specific unit 3-501 and a display unit 3-502.

[0167] The specific unit 3-501 is used to identify the access right that a second user corresponding to the sharing operation has regarding the target task list in response to a sharing operation triggered by a first user on the target task list. The display unit 3-502 is used to display preview data corresponding to the target task list in the display interface of the second user corresponding to the sharing operation based on the access permission.

[0168] In some embodiments, the display unit 3-502 is further used to display an independent window in response to a trigger operation on the target task list in the display interface of the second user, and to display information in the target task list in the independent window.

[0169] In some embodiments, when the second user has access permission to the target task list, the preview data includes at least one or more of the title of the target task list, the owner identifier of the target task list, the co-editor identifier of the target task list, and the access permission information of the second user; or when the second user does not have access permission to the target task list, the preview data includes first prompt information for notifying that the second user does not have access permission to the target task list and a first control for applying for access permission.

[0170] In some embodiments, the access permission includes an editing permission or a viewing permission.

[0171] In some embodiments, when the second user has access permission to the target task list and the target task list includes tasks that have expired, the preview data includes related information of the expired tasks, or the preview data includes related information of at least some of the tasks in the target task list.

[0172] In some embodiments, when the second user has access rights to the target task list, the preview data includes a second control for opening the target task list in a task center interface, and when the display interface corresponding to the second user is a session interface, a third control for adding the target task list as a session tab of the session interface, and includes one or more controls of a fourth control for copying a link of the target task list.

[0173] In some embodiments, the specific unit 3-501 is specifically used to obtain a link of the target task list in response to an operation of copying the link of the target task list triggered by the first user, and to identify the access rights that the second user corresponding to the sharing operation has regarding the target task list in response to a sharing operation triggered by the first user on the link of the target task list.

[0174] In some embodiments, the access rights that the second user has regarding the target task list are not higher than the access rights that the first user has regarding the target task list.

[0175] In some embodiments, the apparatus further includes a modification unit, and the display unit 3-501 is further used to display an editing interface for editing the access rights that the second user has regarding the target task list before sharing the target task list with the second user when the first user has editing rights regarding the target task list. When the first user has editing authority regarding the target task list, after sharing the target task list with the second user, the change unit is used to change the access authority that the second user has regarding the target task list in response to an editing operation triggered by the first user.

[0176] In some embodiments, the display unit 3-502 is specifically used to display a preview card of the target task list in a display interface corresponding to the sharing operation of the second user.

[0177] In some embodiments, the display unit 3-502 is further used to display a preview card of the target task list in an interface corresponding to the sharing operation of the first user, and the preview card includes a fifth control for changing the access authority of the second user regarding the target task list.

[0178] In some embodiments, the display unit 3-502 is further used to display second prompt information for notifying that the target task list has been deleted in the preview card when the target task list is deleted.

[0179] In some embodiments, the display interface corresponding to the sharing operation of the second user is a session interface of the first session, and both the first user and the second user are members of the first session, or the display interface corresponding to the sharing operation of the second user is a cloud document interface of the first cloud document, and both the first user and the second user are co-editors of the first cloud document.

[0180] Note that for the specific implementation of each unit in this embodiment, reference may be made to the relevant descriptions in the embodiments of the above method. In the embodiments of the present disclosure, the division of units is exemplary and merely a logical function division. When actually implemented, there may be other division forms. Each functional unit in the embodiments of the present disclosure may be integrated into one processing unit, each unit may physically exist alone, or two or more units may be integrated into one unit. For example, in the above embodiments, the processing unit and the transmission unit may be the same unit or different units. The above integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0181] Referring to FIG. 14, a schematic diagram of the structure of an electronic device 500 suitable for the implementation of the embodiments of the present disclosure is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (tablet computers), PMPs (portable media players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. The electronic device shown in FIG. 14 is merely an example and is not intended to limit the functions and usage scope of the embodiments of the present disclosure.

[0182] As shown in FIG. 14, the electronic device 1400 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 1401 that can execute various appropriate operations and processes according to a program stored in a read-only memory (ROM) 1402 or a program loaded from a storage device 1408 into a random access memory (RAM) 1403. The RAM 1403 also stores various programs and data necessary for the operation of the electronic device 1400. The processing device 1401, the ROM 1402, and the RAM 1403 are connected to each other via a bus 1404. An input / output (I / O) interface 1405 is also connected to the bus 1404.

[0183] Generally, for example, an input device 1406 including a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc., an output device 1407 including a liquid crystal display (LCD), a speaker, a vibrator, etc., a storage device 1408 including a magnetic tape, a hard disk, etc., and a communication device 1409 may be connected to the I / O interface 1405. The communication device 1409 may allow the electronic device 1400 to communicate with other devices wirelessly or wiredly to exchange data. Although FIG. 14 shows an electronic device 1400 having various devices, it should be understood that it is not necessary to implement or include all the shown devices. More devices or fewer devices may be implemented or included instead.

[0184] In particular, according to the embodiments of the present disclosure, the above-described process described with reference to the flowchart may be implemented as a computer software program. For example, the embodiments of the present disclosure include a computer program product including a computer program mounted on a non-transitory computer-readable medium including program code for executing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network by the communication device 1409, or may be installed from the storage device 1408, or may be installed from the ROM 1402. When the computer program is executed by the processing device 1401, the above-described functions limited to the method of the embodiments of the present disclosure are executed.

[0185] The electronic device according to the embodiments of the present disclosure belongs to the same inventive concept as the method according to the above embodiments. For technical details not described in detail in this embodiment, reference may be made to the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0186] The embodiments of the present disclosure provide a computer storage medium storing a computer program, and when the program is executed by a processor, the method according to the above embodiments is realized.

[0187] Note that the computer-readable medium described above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two above. The computer-readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above, but is not limited thereto. More specific examples of the computer-readable storage medium may include an electrical connection having one or more wires, a portable computer disk, a hard disk, RAM, ROM, erasable programmable read-only memory (EPROM) or flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical memory device, a magnetic memory device, or any suitable combination of the above, but is not limited thereto. In the present disclosure, the computer-readable storage medium may be any tangible medium that includes or stores a program that can be used by or in combination with an instruction execution system, apparatus, or device. On the other hand, in the present disclosure, the computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave on which a computer-readable program code is carried. Such a propagated data signal may adopt various forms, including electromagnetic signals, optical signals, or any suitable combination of the above, but is not limited thereto. Furthermore, the computer-readable signal medium may be any computer-readable medium other than the computer-readable storage medium that can transmit, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code included in the computer-readable medium may be transmitted through any suitable medium, including wires, optical cables, radio frequency (RF), etc., or any suitable combination of the above, but is not limited thereto.

[0188] In some embodiments, a client or a server can communicate using any network protocol known currently or developed in the future, such as, for example, the Hyper Text Transfer Protocol (HTTP), and can be connected to digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the World Wide Web (e.g., the Internet) and end-to-end networks (e.g., ad hoc end-to-end networks), and any network known currently or developed in the future.

[0189] The computer-readable medium may be included in the above-described electronic device, or may exist separately without being incorporated into the electronic device.

[0190] One or more programs are installed on the computer-readable medium, and when the one or more programs are executed by the electronic device, the electronic device can be caused to execute the above method.

[0191] The computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or combinations thereof, including, but not limited to, object-oriented programming languages such as Java, Smalltalk, C++, etc., and also including conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the first user's computer, partially on the first user's computer, executed as a stand-alone package, partially on the first user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the first user's computer by any type of network including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., connected via the Internet using an Internet service provider).

[0192] Flowcharts and block diagrams in the drawings illustrate the architecture, functionality, and operation that can be implemented according to systems, methods, and computer program products of various types of embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent one module, program segment, or portion of code that includes one or more executable instructions for implementing a given logic function. It should also be noted that in some alternative implementations, the functions represented within a block may occur in a different order than shown in the drawings. For example, two blocks shown in succession may actually be executed substantially in parallel, or may sometimes be executed in the reverse order depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, as well as combinations of blocks in a block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs a given function or operation, or may be implemented by a combination of dedicated hardware and computer instructions.

[0193] The units mentioned in the description of the embodiments of the present disclosure may be implemented in software or in hardware. Here, the name of a unit / module does not limit the unit itself in some cases.

[0194] The functions described above in this specification can be executed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), application specific standard products (ASSP), system on a chip (SOC), complex programmable logic devices (CPLD), and the like.

[0195] In the context of the disclosure, a machine-readable medium may be a tangible medium that includes or can store a program used by or in combination with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, 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 the machine-readable storage medium include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0196] It should be noted that each embodiment in this specification is described sequentially. What is emphasized in each embodiment is the difference from other embodiments. For the same or similar parts between each embodiment, reference may be made to each other. For the system or apparatus disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is simplified. For related parts, reference may be made to the description of the method part.

[0197] It should be understood that in some embodiments of the present disclosure, "at least one (item)" means one or more, and "a plurality" means two or more. "And / or" is for describing the relationship of related objects and indicates that three relationships can exist. For example, "A and / or B" may represent three cases where only A exists, only B exists, or both A and B exist simultaneously, where A and B may be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following items" or similar expressions mean any combination of these items, including any combination of a single item or multiple 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, b, and c", where a, b, c can be single or plural.

[0198] Note that in this specification, relational terms such as first and second are only for distinguishing one entity or operation from another entity or operation, and do not require or imply the existence of such an actual relationship or order between these entities or operations. And the term "comprising", "including" or any other variation thereof is intended to cover non-exclusive "including", so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or also includes elements inherent in such a process, method, article or device. Unless there are further limitations, for an element defined by the phrase "comprising one of...", it does not exclude the existence of other same elements in the process, method, article or device including the said element.

[0199] The steps of the method or algorithm described with reference to the embodiments disclosed in this specification may be implemented directly by hardware, by a software module executed by a processor, or by a combination of both. The software module may be disposed in a random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, register, hard disk, removable magnetic disk, CD-ROM, or any other form of storage medium well known in the art.

[0200] From the above description of the disclosed embodiments, those skilled in the art can realize or use the present disclosure. Various modifications to these embodiments are obvious to those skilled in the art, and the general principles defined in this specification can also be realized in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not limited to these embodiments shown in this specification, but should be given the widest scope consistent with the principles and novel features disclosed in this specification.

[0201] Other aspects of the present invention are described in the following numbered clauses.

[0202] 1. A method for creating a task list, comprising: receiving a task list creation operation triggered by a first user through a first client interface, and obtaining task list related information input by the first user; generating a first task list that is a task container and does not depend on other entities in the application to which the first client interface belongs, based on the task list related information.

[0203] 2. The method according to clause 1, wherein the first client interface is a task center interface, an instant messaging session interface, a collaboration space interface, or a cloud document interface.

[0204] 3. The method according to clause 1, wherein the first user is the owner of the first task list, and the owner of the first task list has editing rights regarding the first task list.

[0205] 4. The method further includes, in response to a transfer operation triggered by the first user for the first task list, transferring the ownership of the first task list to a second user and designating the second user as the owner of the first task list, as described in clause 3.

[0206] 5. The editing rights include one or more of editing the setting information corresponding to the first task list, including archiving and / or deleting the first task list, and editing the tasks included in the first task list, as described in clause 3.

[0207] 6. The method according to clause 1, wherein there is one or more members in the first task list, and one of the members has editing rights or viewing rights regarding the first task list.

[0208] 7. The members of the first task list include member information in the task list related information. When generating the first task list based on the task list related information, members are added to the first task list based on the member information, and after generating the first task list, in response to a member addition operation triggered for the first task list, members are added to the first task list. When creating the first task list in the instant messaging session interface, identifying all or some of the session members of the instant messaging session as members of the first task list; The method according to clause 6, added in one or more forms of identifying all or some of the co-editors of the cloud document interface as members of the first task list when creating the first task list in the cloud document interface.

[0209] 8. The editing permission Editing the setting information corresponding to the first task list, excluding archiving and deleting the first task list; The method according to clause 6, including one or more of editing the tasks included in the first task list.

[0210] 9. The viewing permission Viewing and / or commenting on the first task list and being unable to edit the setting information corresponding to the first task list; The method according to clause 6, including one or more of viewing and / or commenting on the tasks included in the first task list, being unable to create or add tasks in the first task list, and being unable to edit the tasks included in the first task list.

[0211] 10. The method The method according to clause 1, further including setting permissions regarding the target task for the members of the first task list based on the permissions the members of the first task list have regarding the first task list in response to newly creating or adding a target task in the first task list.

[0212] 11. If a member of the first task list has editing authority regarding the first task list, then the member has editing authority regarding the target task, The method according to clause 10, wherein if a member of the first task list has viewing authority regarding the first task list, then the member has at least viewing authority regarding the target task.

[0213] 12. The method further includes one or more of: in response to a task in the first task list being deleted, ceasing to display the deleted task in the first task list; in response to the first task list being deleted, not performing a deletion operation on the tasks in the first task list; in response to the first task list being deleted, deleting tasks in the first task list that have no responsible person, the method according to clause 1.

[0214] 13. The method When creating or adding the first task list in the first service interface, by default, grant the first authority regarding the first task list to the related members of the first service interface, and in response to an editing operation triggered on the first task list, change the authority of the related members regarding the first task list to the second authority; or When creating or adding the first task list in the first service interface, further include granting the authority regarding the first task list to the related members of the first service interface based on an authority setting operation, the method according to clause 1.

[0215] 14. The first service interface includes an instant messaging session interface or a cloud document interface, When the first service interface is an instant messaging session interface, the related members of the first service interface are some or all of the corresponding session members, When the first service interface is a cloud document session interface, the related members of the first service interface are some or all of the corresponding cloud document co - editors, in the manner described in Article 13.

[0216] 15. The method when changing the permission regarding the first task list of one or more of the related members to no permission, displays first prompt information for notifying that there is no permission to access the first task list in the first service interface corresponding to one or more of the related members; when the first task list is deleted, displays second prompt information for notifying that the first task list has already been deleted in the first service interface, further includes one or more of the above, in the manner described in Article 13.

[0217] 16. The method further includes granting the fourth user the permission regarding the first task list in response to the third user sharing the first task list with the fourth user, and the permission that the fourth user has regarding the first task list is not higher than the permission that the third user has regarding the first task list, in the manner described in Article 1.

[0218] 17. When the first task list includes a first member and a first task, the permission that the first member has regarding the first task is the target permission, and the target permission is the greater of the permission corresponding to the role that the first member undertakes in the first task and the permission that the first member has regarding the first task list granted to the first member, in the manner described in Article 1.

[0219] 18. A task list creation device, a receiving unit configured to receive a task list creation operation triggered by a first user via a first client interface and to obtain task list related information input by the first user; and a generation unit configured to generate a first task list that is a task container and does not depend on other entities in an application to which the first client interface belongs, based on the task list related information. A task list creation device comprising the above components.

[0220] 19. An electronic device including a processor and a memory, wherein the memory is used to store instructions or computer programs, and the processor is used to execute the instructions or computer programs in the memory to cause the electronic device to execute the method according to any one of clauses 1 to 17. An electronic device.

[0221] 20. A computer-readable storage medium having instructions stored thereon, and when the instructions are executed on a device, the device is caused to execute the method according to any one of clauses 1 to 17. A computer-readable storage medium.

[0222] 21. An information interaction method, in response to an operation of adding a first task list triggered by an interface of a first session as a session tab, adding a first session tab corresponding to the first task list in the interface of the first session, wherein the first task list has already been added as a session tab of a second session, and a session tab corresponding to the first task list in the interface of the second session is a second session tab, and the first session and the second session have a first association relationship or no association relationship; and In response to a trigger operation on the first session tab in the interface of the first session, displaying the first task list, an information interaction method including this.

[0223] 22. The method further includes: In response to adding a first session tab corresponding to the first task list in the interface of the first session, granting a first permission regarding the first task list to all or some of the members in the first session, the method according to clause 21.

[0224] 23. The method includes: Before granting the first permission regarding the first task list to the members in the first session, providing a permission editing control, and based on the user's operation on the permission editing control, granting the first permission regarding the first task list to all or some of the members in the first session, and After adding a first session tab corresponding to the first task list in the interface of the first session, in response to an editing operation triggered on the first session tab, changing the permission regarding the first task list of all or some of the members in the first session to a second permission, the method according to clause 22, further including one or more of these.

[0225] 24. The interface of the first session includes a session message display area and a non-session message display area. The first session tab is displayed in a first display area of the non-session message display area, and the second display area of the non-session message display area is used to display the basic information and / or basic function controls of the first session, the method according to clause 21.

[0226] In response to an operation of adding the first task list triggered by the interface of the first session as a session tab, adding the first session tab corresponding to the first task list in the interface of the first session is If the first task list does not exist before adding the first session tab corresponding to the first task list in the interface of the first session, in response to a trigger operation on the first addition control in the interface of the first session, display a first interface for adding a session tab corresponding to the task list, and in response to a task list creation operation triggered on the first interface, create the first task list and add the first session tab corresponding to the first task list in the interface of the first session, or If the first task list already exists before adding the first task list tab in the interface of the first session, in response to a trigger operation on the first addition control in the interface of the first session, display a first interface for adding a session tab corresponding to the task list, and in response to an operation of adding the existing first task list triggered on the first interface, add the first session tab corresponding to the first task list in the interface of the first session, including the method according to clause 21.

[0227] In response to a trigger operation on the first addition control in the interface of the first session, displaying the first interface is In response to a trigger operation on the first control in the interface of the first session, display a first window including a tab addition control; In response to a trigger operation on the tab addition control, display a second window including a task list tab addition control; responding to a trigger operation on the task list tab addition control, and displaying a first interface, the method according to clause 25, including.

[0228] 27. Displaying the first task list in response to a trigger operation on the first session tab in the interface of the first session is displaying the first task list in the interface of the first session in response to a trigger operation on the first session tab in the interface of the first session, or, displaying the first task list in a third window independent of the interface of the first session in response to a trigger operation on the first session tab in the interface of the first session, the method according to clause 21, including.

[0229] 28. The method is further including displaying a fourth window in response to triggering a predetermined operation on the first session tab in the interface of the first session, the fourth window is an open control for opening the task list in the task center, and a copy control for copying a link of the first task list, and an edit control for editing a tab name of the first session tab, and including one or more controls of a delete control for removing the first session tab from the interface of the first session, the method according to clause 21.

[0230] 29. The display form of the first session tab includes a predetermined identifier corresponding to a task type, the method according to clause 21.

[0231] 30. The method is When removing the first session tab from the interface of the first session, maintaining the access rights of all or some of the members in the first session to the first task list, or, When removing the first session tab from the interface of the first session, revoking the access rights of all or some of the members in the first session to the first task list, or, The method according to clause 21, further comprising, when all or some of the members in the first session have editing rights regarding the first task list, granting all or some of the members in the first session the right to view the first task list after removing the first session tab from the interface of the first session.

[0232] 31. An information interaction device, An adding unit for adding a first session tab corresponding to the first task list in the interface of the first session in response to an operation of adding the first task list as a session tab triggered at the interface of the first session, wherein the first task list has already been added as a session tab of a second session, the session tab corresponding to the first task list in the interface of the second session is a second session tab, and the first session and the second session have a first related relationship or no related relationship, A display unit for displaying the first task list in response to a trigger operation on the first session tab in the interface of the first session, the information interaction device comprising the display unit.

[0233] 32. An electronic device, comprising a processor and a memory, The memory is used for storing instructions or computer programs, The processor is an electronic device used to execute the instructions or computer programs in the memory to cause the electronic device to execute the method described in any one of Articles 21 to 30.

[0234] 33. A computer-readable storage medium, in which instructions are stored, and when the instructions are executed on a device, the device is caused to execute the method described in any one of Articles 21 to 30.

[0235] 34. A task list sharing method, identifying, in response to a sharing operation triggered by a first user for a target task list, the access rights that a second user corresponding to the sharing operation has with respect to the target task list; and based on the access rights, displaying, in a display interface corresponding to the sharing operation of the second user, preview data corresponding to the target task list.

[0236] 35. The method further includes: in response to a trigger operation on the target task list in the display interface of the second user, displaying a separate window, and displaying information in the target task list in the separate window.

[0237] 36. When the second user has access rights with respect to the target task list, the preview data includes at least one or more of the title of the target task list, the owner identifier of the target task list, the co-editor identifier of the target task list, and the access right information that the second user has. Or, If the second user does not have access rights regarding the target task list, the preview data includes first prompt information for notifying that the second user does not have access rights regarding the target task list and a first control for applying for access rights, according to the method described in clause 34.

[0238] 37. The access rights include editing rights or viewing rights, according to the method described in clause 34.

[0239] 38. If the second user has access rights regarding the target task list and the target task list includes tasks that have expired, the preview data includes related information about the expired tasks, and / or, the preview data includes related information about at least some of the tasks in the target task list, according to the method described in clause 34.

[0240] 39. If the second user has access rights regarding the target task list, the preview data includes a second control for opening the target task list in the task center interface, if the display interface corresponding to the second user is a session interface, a third control for adding the target task list as a session tab of the session interface, and / or a fourth control for copying the link of the target task list, including one or more of these controls, according to the method described in clause 34.

[0241] 40. Identifying the access rights that the second user corresponding to the shared operation has regarding the target task list in response to a shared operation triggered by the first user on the target task list is obtaining the link of the target task list in response to an operation triggered by the first user to copy the link of the target task list, In response to a sharing operation triggered by the first user for a link in the target task list, identifying the access rights that the second user corresponding to the sharing operation has with respect to the target task list, the method according to clause 34.

[0242] 41. The method according to clause 34, wherein the access rights that the second user has with respect to the target task list are not higher than the access rights that the first user has with respect to the target task list.

[0243] 42. The method includes when the first user has editing rights with respect to the target task list, displaying an editing interface for editing the access rights that the second user has with respect to the target task list before sharing the target task list with the second user; when the first user has editing rights with respect to the target task list, after sharing the target task list with the second user, changing the access rights that the second user has with respect to the target task list in response to an editing operation triggered by the first user, the method according to clause 34 further including one or more of these.

[0244] 43. Based on the access rights, in the display interface corresponding to the sharing operation of the second user, displaying preview data corresponding to the target task list includes displaying a preview card of the target task list in the display interface corresponding to the sharing operation of the second user, the method according to any one of clauses 34 to 42.

[0245] 44. The method includes The method according to clause 43, further comprising, in an interface corresponding to the sharing operation of the first user, displaying a preview card of the target task list, wherein the preview card includes a fifth control for changing the access right of the second user to the target task list.

[0246] 45. The method further comprises The method according to clause 43, further comprising, when the target task list is deleted, displaying, in the preview card, second prompt information for notifying that the target task list has been deleted.

[0247] 46. The display interface corresponding to the sharing operation of the second user is a session interface of a first session, and both the first user and the second user are members of the first session, or The display interface corresponding to the sharing operation of the second user is a cloud document interface of a first cloud document, and both the first user and the second user are co-editors of the first cloud document, the method according to clause 34.

[0248] 47. A task list sharing device, comprising An identifying unit for identifying the access right that a second user has regarding a target task list in response to a sharing operation triggered by a first user on the target task list, and A display unit for displaying preview data corresponding to the target task list in a display interface corresponding to the sharing operation of the second user based on the access right, the task list sharing device.

[0249] 48. An electronic device, comprising a processor and a memory, The memory is used for storing instructions or computer programs, The processor is an electronic device used to execute the instructions or computer programs in the memory to cause the electronic device to execute the method described in any one of clauses 34 to 46.

[0250] 49. A computer-readable storage medium having instructions stored thereon, which when executed on a device, cause the device to execute the method described in any one of clauses 34 to 46.

Claims

1. A method for creating a task list, comprising: receiving a task list creation operation triggered by a first user through a first client interface, and obtaining task list related information input by the first user; generating a first task list that is a task container and does not depend on other entities in the application to which the first client interface belongs based on the task list related information. The method for creating a task list is characterized by the above.

2. The method according to claim 1, wherein the first client interface is 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, wherein the first user is the owner of the first task list, and the owner of the first task list has editing authority regarding the first task list.

4. The method further comprises: responding to a transfer operation triggered by the first user on the first task list, transferring the ownership of the first task list to a second user, and setting the second user as the owner of the first task list. The method according to claim 3 is characterized by the above.

5. The editing authority includes: editing setting information corresponding to the first task list, including archiving and / or deleting the first task list; editing one or more of the tasks included in the first task list. The method according to claim 3 is characterized by the above.

6. The method according to claim 1, wherein there is one or more members in the first task list, and one of the members has editing authority or viewing authority regarding the first task list.

7. The members of the first task list are: when member information is included in the task list related information and generating the first task list based on the task list related information, adding members to the first task list based on the member information; after generating the first task list, adding members to the first task list in response to a member addition operation triggered on the first task list. When creating the first task list in the instant messaging session interface, identifying all or some of the session members of the instant messaging session as members of the first task list, When creating the first task list in the cloud document interface, being added in one or more forms of identifying all or some of the co - editors of the cloud document interface as members of the first task list, the method according to claim 6, characterized in that.

8. The editing authority is Editing the setting information corresponding to the first task list, not including archiving and deleting the first task list, The method according to claim 6, characterized in that it includes one or more of editing the tasks included in the first task list.

9. The viewing authority is Viewing and / or commenting on the first task list and being unable to edit the setting information corresponding to the first task list, The method according to claim 6, characterized in that it includes one or more of viewing and / or commenting on the tasks included in the first task list, being unable to create or add tasks in the first task list, and being unable to edit the tasks included in the first task list.

10. The method is Further including, in response to newly creating or adding a target task in the first task list, setting permissions regarding the target task for the members of the first task list based on the permissions that the members of the first task list have regarding the first task list, the method according to claim 1, characterized in that.

11. When one member of the first task list has editing authority regarding the first task list, that member has editing authority regarding the target task, When one member of the first task list has viewing authority regarding the first task list, that member has at least viewing authority regarding the target task, the method according to claim 10, characterized in that.

12. The method is In response to a task in the first task list being deleted, the deleted task ceases to be displayed in the first task list; In response to the first task list being deleted, no deletion operation is performed on the tasks in the first task list; The method according to claim 1, further comprising one or more of: in response to the first task list being deleted, deleting tasks in the first task list that have no responsible person.

13. The method includes: When creating or adding the first task list in the first service interface, by default, granting a first permission regarding the first task list to relevant members of the first service interface, and in response to an edit operation triggered on the first task list, changing the permission of the relevant members regarding the first task list to a second permission; Or When creating or adding the first task list in the first service interface, further comprising granting, based on a permission setting operation, a permission regarding the first task list to relevant members of the first service interface. The method according to claim 1 is characterized by this.

14. The first service interface includes an instant messaging session interface or a cloud document interface. When the first service interface is an instant messaging session interface, the relevant members of the first service interface are some or all of the corresponding session members. When the first service interface is a cloud document session interface, the relevant members of the first service interface are some or all of the corresponding cloud document co - editors. The method according to claim 13 is characterized by this.

15. The method includes: When changing the permission of one or more of the relevant members regarding the first task list to no permission, in the first service interface corresponding to one or more of the relevant members, displaying first prompt information for notifying that there is no permission to access the first task list. The method according to claim 13, further comprising one or more of the following: when the first task list is deleted, in the first service interface, displaying second prompt information for notifying that the first task list has already been deleted.

16. The method further comprises: in response to a third user sharing the first task list with a fourth user, granting the fourth user permissions regarding the first task list, wherein the permissions the fourth user has regarding the first task list are not higher than the permissions the third user has regarding the first task list. The method according to claim 1.

17. When the first task list includes a first member and a first task, the permissions the first member has regarding the first task are target permissions, and the target permissions are the greater of the permissions corresponding to the role the first member undertakes in the first task and the permissions the first member has regarding the first task list granted to the first member. The method according to claim 1.

18. A task list creation device, comprising: a receiving unit configured to receive a task list creation operation triggered by a first user through a first client interface and obtain task list related information input by the first user; and a generating unit configured to generate a first task list that is a task container and does not depend on other entities in the application to which the first client interface belongs based on the task list related information. A task list creation device characterized by the above.

19. An electronic device, comprising a processor and a memory, wherein the memory is used to store instructions or computer programs, and the processor is used to execute the instructions or computer programs in the memory to cause the electronic device to execute the method according to any one of claims 1 to 17. An electronic device characterized by the above.

20. A computer-readable storage medium, having instructions stored thereon, wherein when the instructions are executed on a device, the device is caused to execute the method according to any one of claims 1 to 17. A computer-readable storage medium characterized by the above.

21. An information interaction method, in response to an operation of adding a first task list triggered by an interface of a first session as a session tab, adding a first session tab corresponding to the first task list in the interface of the first session, wherein the first task list has already been added as a session tab of a second session, and a session tab corresponding to the first task list in the interface of the second session is a second session tab, and the first session and the second session have a first association relationship or no association relationship, and displaying the first task list in response to a trigger operation on the first session tab in the interface of the first session. The information interaction method includes the above steps.

22. The method further includes: in response to adding a first session tab corresponding to the first task list in the interface of the first session, granting a first permission regarding the first task list to all or some of the members in the first session. The method according to claim 21.

23. The method further includes: before granting a first permission regarding the first task list to a member in the first session, providing a permission editing control, and based on an operation of the user on the permission editing control, granting the first permission regarding the first task list to all or some of the members in the first session; and after adding a first session tab corresponding to the first task list in the interface of the first session, in response to an editing operation triggered on the first session tab, changing the permission regarding the first task list of all or some of the members in the first session to a second permission. The method according to claim 22 includes one or more of the above steps.

24. The interface of the first session includes a session message display area and a non-session message display area. The first session tab is displayed in the first display area of the non-session message display area, and the second display area of the non-session message display area is used to display the basic information and / or basic function controls of the first session. The method according to claim 21.

25. In response to an operation of adding a first task list triggered by the interface of the first session as a session tab, adding the first session tab corresponding to the first task list in the interface of the first session, if the first task list does not exist before adding the first session tab corresponding to the first task list in the interface of the first session, in response to a trigger operation on the first addition control in the interface of the first session, display a first interface for adding a session tab corresponding to the task list, and in response to a task list creation operation triggered on the first interface, create the first task list, and add the first session tab corresponding to the first task list in the interface of the first session, or, if the first task list already exists before adding the first task list tab in the interface of the first session, in response to a trigger operation on the first addition control in the interface of the first session, display a first interface for adding a session tab corresponding to the task list, and in response to an operation of adding the existing first task list triggered on the first interface, add the first session tab corresponding to the first task list in the interface of the first session. The method according to claim 21.

26. In response to a trigger operation on the first addition control in the interface of the first session, displaying the first interface, in response to a trigger operation on the first control in the interface of the first session, displaying a first window including a tab addition control, In response to a trigger operation on the tab addition control, displaying a second window including a task list tab addition control; The method according to claim 25, further comprising: in response to a trigger operation on the task list tab addition control, displaying a first interface.

27. Displaying the first task list in response to a trigger operation on the first session tab in the interface of the first session includes: Displaying the first task list in the interface of the first session in response to a trigger operation on the first session tab in the interface of the first session; Or The method according to claim 21, further comprising: in response to a trigger operation on the first session tab in the interface of the first session, displaying the first task list in a third window independent of the interface of the first session.

28. The method further comprises: In response to triggering a predetermined operation on the first session tab in the interface of the first session, further displaying a fourth window, The fourth window includes: An open control for opening the task list in the task center; A copy control for copying a link of the first task list; An edit control for editing a tab name of the first session tab; The method according to claim 21, further comprising one or more controls selected from a delete control for removing the first session tab from the interface of the first session.

29. The method according to claim 21, wherein a display form of the first session tab includes a predetermined identifier corresponding to a task type.

30. The method further comprises: When removing the first session tab from the interface of the first session, maintaining access rights of all or some members in the first session to the first task list, or When removing the first session tab from the interface of the first session, revoking access rights of all or some members in the first session to the first task list, or If all or some of the members in the first session have editing rights regarding the first task list, after removing the first session tab from the interface of the first session, further including granting all or some of the members in the first session viewing rights to the first task list. The method according to claim 21.

31. An information interaction device, An additional unit for adding a first session tab corresponding to the first task list in the interface of the first session in response to an operation of adding the first task list as a session tab triggered at the interface of the first session. The first task list has already been added as a session tab of a second session, and the session tab corresponding to the first task list in the interface of the second session is a second session tab. The first session and the second session have a first association relationship or no association relationship. An additional unit, A display unit for displaying the first task list in response to a trigger operation on the first session tab in the interface of the first session. An information interaction device including the display unit.

32. An electronic device including a processor and a memory, The memory is used for storing instructions or computer programs, The processor is used for executing the instructions or computer programs in the memory to cause the electronic device to execute the method according to any one of claims 21 to 30. An electronic device.

33. A computer-readable storage medium having instructions stored thereon. When the instructions are executed on a device, the device is caused to execute the method according to any one of claims 21 to 30. A computer-readable storage medium.

34. A task list sharing method, Identifying the access rights that a second user corresponding to the sharing operation has regarding a target task list in response to a sharing operation triggered by a first user on the target task list. A task list sharing method, including displaying preview data corresponding to the target task list in a display interface corresponding to the sharing operation of the second user based on the access right.

35. The method further includes, in response to a trigger operation on the target task list in the display interface of the second user, displaying a separate window and displaying information in the target task list in the separate window, according to the method described in claim 34.

36. When the second user has an access right regarding the target task list, the preview data includes at least one or more of a title of the target task list, an owner identifier of the target task list, a co-editor identifier of the target task list, and access right information of the second user. Or When the second user does not have an access right regarding the target task list, the preview data includes first prompt information for notifying that the second user does not have an access right regarding the target task list and a first control for applying for an access right, according to the method described in claim 34.

37. The access right includes an editing right or a viewing right, according to the method described in claim 34.

38. When the second user has an access right regarding the target task list and the target task list includes tasks that have passed the deadline, the preview data includes related information of the tasks that have passed the deadline. And / or The preview data includes related information of at least some tasks in the target task list, according to the method described in claim 34.

39. When the second user has an access right regarding the target task list, the preview data includes a second control for opening the target task list in a task center interface. When the display interface corresponding to the second user is a session interface, it includes a third control for adding the target task list as a session tab of the session interface. The method according to claim 34, comprising one or more controls of the fourth control for copying the link of the target task list.

40. Identifying the access rights that the second user has with respect to the target task list in response to a sharing operation triggered by the first user for the target task list Obtaining a link to the target task list in response to an operation triggered by the first user to copy the link of the target task list The method according to claim 34, comprising: identifying, in response to a sharing operation triggered by the first user for the link of the target task list, the access rights that the second user corresponding to the sharing operation has with respect to the target task list.

41. The method according to claim 34, wherein the access rights that the second user has with respect to the target task list are not higher than the access rights that the first user has with respect to the target task list.

42. The method When the first user has editing rights with respect to the target task list, displaying an editing interface for editing the access rights that the second user has with respect to the target task list before sharing the target task list with the second user The method according to claim 34, further comprising one or more of: when the first user has editing rights with respect to the target task list, changing the access rights that the second user has with respect to the target task list in response to an editing operation triggered by the first user after sharing the target task list with the second user.

43. Based on the access rights, displaying preview data corresponding to the target task list in the display interface corresponding to the sharing operation of the second user The method according to any one of claims 34 to 42, comprising displaying a preview card of the target task list in the display interface corresponding to the sharing operation of the second user.

44. The method The method according to claim 43, further comprising, in an interface corresponding to the sharing operation of the first user, displaying a preview card of the target task list, wherein the preview card includes a fifth control for changing an access right of the second user to the target task list.

45. The method further comprises when the target task list is deleted, further comprising, in the preview card, displaying second prompt information for notifying that the target task list has been deleted, the method according to claim 43.

46. The display interface corresponding to the sharing operation of the second user is a session interface of a first session, and both the first user and the second user are members of the first session, or the display interface corresponding to the sharing operation of the second user is a cloud document interface of a first cloud document, and both the first user and the second user are co-editors of the first cloud document, the method according to claim 34.

47. A task list sharing device, comprising a specifying unit for specifying an access right that a second user has with respect to a target task list in response to a sharing operation triggered by a first user on the target task list; and a display unit for displaying preview data corresponding to the target task list in a display interface corresponding to the sharing operation of the second user based on the access right, the task list sharing device.

48. An electronic device, comprising a processor and a memory, wherein the memory is used for storing instructions or computer programs, and the processor is used for executing the instructions or computer programs in the memory to cause the electronic device to execute the method according to any one of claims 34 to 46, the electronic device.

49. A computer-readable storage medium having instructions stored thereon, and when the instructions are executed on a device, causing the device to execute the method according to any one of claims 34 to 46, the computer-readable storage medium.

Images