CN116016420A - Task list sharing method, device, equipment and medium - Google Patents

Abstract

The embodiment of the disclosure discloses a task list sharing method, device, equipment and medium, wherein when a sharing operation triggered by a first user on a target task list is received, access rights of a second user corresponding to the sharing operation on the target task list are determined. Wherein the second user is a shared user. And after the access right of the second user to the target task list is determined, 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. That is, by the technical scheme provided by the embodiment of the disclosure, the task list can be shared, and the access right of the shared user to the task list is determined during sharing, so that preview data of the task list is displayed on the display interface corresponding to the shared user according to the access right, thereby being convenient for different users to check information of the task list and improving user experience.

Description

Task list sharing method, device, equipment and medium

Technical Field

The embodiment of the disclosure relates to the technical field of computers, in particular to a task list sharing method, device, equipment and medium.

Background

Often encountered in collaborative scenarios, users need to receive and process multiple tasks. In general, multiple tasks are in a scattered distribution state, so that management is inconvenient, and the use experience of a user is affected. How to effectively manage the tasks is a technical problem to be solved.

Disclosure of Invention

In view of this, embodiments of the present disclosure provide a task list sharing method, device, equipment, and medium, so as to enable different users to view task lists conveniently by sharing task lists to different users rapidly, and improve user experience.

In order to achieve the above object, the technical solution provided by the embodiments of the present disclosure is as follows:

in a first aspect of embodiments of the present disclosure, a task list sharing method is provided, where the method includes:

responding to a sharing operation triggered by a first user on a target task list, and determining the access right of a second user corresponding to the sharing operation for the target task list;

and 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.

In a second aspect of the embodiments of the present disclosure, there is provided a task list sharing apparatus, including:

The determining unit is used for responding to the sharing operation triggered by the first user on the target task list and determining the access right of the second user corresponding to the sharing operation on the target task list;

and the display unit is used 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.

In a third aspect of embodiments of the present disclosure, there is provided an electronic device, the device comprising: a processor and a memory;

the memory is used for storing instructions or computer programs;

the processor is configured to execute the instructions or the computer program in the memory, so that the electronic device performs the method according to the first aspect.

In a fourth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium having instructions stored therein which, when executed on a device, cause the device to perform the method of the first aspect.

In a fifth aspect of embodiments of the present disclosure, a computer program product is provided, comprising a computer program/instruction which, when executed by a processor, implements the method of the first aspect.

It can be seen that the embodiments of the present disclosure have the following beneficial effects:

in the embodiment of the disclosure, when a sharing operation triggered by a first user on a target task list is received, an access right of a second user corresponding to the sharing operation for the target task list is determined. Wherein the second user is a shared user. And after the access right of the second user to the target task list is determined, 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. That is, by the technical scheme provided by the embodiment of the disclosure, the task list can be shared, and the access right of the shared user to the task list is determined during sharing, so that preview data of the task list is displayed on the display interface corresponding to the shared user according to the access right, thereby being convenient for different users to check information of the task list and improving user experience.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments described in the embodiments of the present disclosure, and other drawings may be obtained according to these drawings without inventive effort to a person having ordinary skill in the art.

FIG. 1 is a flowchart of a task list sharing method according to an embodiment of the present disclosure;

FIG. 2a is a schematic diagram of trigger sharing according to an embodiment of the present disclosure;

FIG. 2b is a schematic view of editing a second user access rights provided by an embodiment of the present disclosure;

FIG. 2c is a schematic diagram of another editing second user access rights provided by an embodiment of the present disclosure;

FIG. 3a is a schematic diagram of a preview card of a task list displayed in a session according to an embodiment of the present disclosure;

FIG. 3b is a schematic diagram of a preview card corresponding to a blank task list according to an embodiment of the present disclosure;

FIG. 3c is a schematic diagram of a preview card with a task list deleted according to an embodiment of the present disclosure;

fig. 3d is a schematic diagram of a preview card corresponding to no access rights according to an embodiment of the present disclosure;

FIG. 4a is a schematic diagram of an application access rights interface provided by an embodiment of the present disclosure;

FIG. 4b is a schematic diagram of a notification message sent to an owner provided by an embodiment of the present disclosure;

FIG. 4c is a schematic diagram of a notification message sent to an applicant according to an embodiment of the present disclosure;

FIG. 4d is a schematic diagram of another task list preview card in a session display provided by an embodiment of the present disclosure;

FIG. 5 is a block diagram of a task list sharing device according to an embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the disclosure.

Detailed Description

In order that those skilled in the art will better understand the embodiments of the present disclosure, a technical solution in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only a part of embodiments of the present disclosure, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the disclosed embodiments, are within the scope of the disclosed embodiments.

In embodiments of the present disclosure, to facilitate managing tasks, multiple tasks are managed by way of creating a task list. Considering that most of the collaboration occurs in a session or cloud document at present, task lists can be shared for facilitating the collaboration, so that the task lists can be browsed under different collaboration scenes, and the user collaboration is facilitated.

Based on this, the embodiment of the disclosure provides a task list sharing method, firstly, in response to a sharing operation triggered by a first user on a target task list, determining an access right of a second user corresponding to the sharing operation for the target task list. After the access authority of the second user to the target task list is determined, displaying preview data corresponding to the target task list in a display interface corresponding to the sharing operation of the second user according to the access authority, so that the second user can directly browse related information of the target task list through the display interface, and user experience is improved.

In order to facilitate understanding of the technical solutions provided by the embodiments of the present disclosure, the following description will be given with reference to the accompanying drawings.

Referring to fig. 1, a flowchart of a task list sharing method provided by an embodiment of the present disclosure may be executed by a client, where the client may have a task list creation and/or sharing function and be installed in an electronic device. The electronic device may include a mobile phone, a tablet computer, a notebook computer, a desktop computer, a vehicle-mounted terminal, a wearable electronic device, an integrated machine, an intelligent home device, or a virtual machine or a simulator. As shown in fig. 1, the method may include the steps of:

s101: and responding to the sharing operation triggered by the first user on the target task list, and determining the access right of the second user corresponding to the sharing operation for the target task list.

In this embodiment, when the first user triggers the sharing operation on the target task list, the access right of the shared user (second user) for the target task list is determined. The first user may trigger a sharing operation at any 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.

In one embodiment of the present disclosure, in response to a sharing operation triggered by a first user on a target task list, determining an access right of a second user corresponding to the sharing operation for the target task list includes: responding to the operation of copying the link of the target task list triggered by the first user, and acquiring the link of the target task list; and responding to the sharing operation triggered by the link of the first user to the target task list, and determining the access right of the second user corresponding to the sharing operation for the target task list. That is, the first user may share the target task request by copying the link of the target task list.

The second user has access right to the target task list which is not higher than that of the first user. That is, the first user cannot exceed the access rights possessed by the first user when sharing the target task list. For example, when the first user has read rights to the target task list, the second user may have read rights to the target task list; when the first user has editing rights to the target task list, the second user can have reading rights or editing rights of the target task list; when the first user has no access to the target task list, the third user has no access to the target task list.

The access rights include editing rights and reading rights, wherein the editing rights refer to not only reading the target task list, but also editing configuration information of the target task list and editing tasks included in the target task list. The configuration information corresponding to the editing target task list may include a title of the editing target task list, a member corresponding to the editing target task list, and the like. The reading authority refers to only reading and/or commenting the target task list and reading and/or commenting the tasks included in the target task list, but cannot edit configuration information of the target task list, cannot create or add tasks in the target task list and cannot edit the tasks included in the target task list. Wherein the editing rights include reading rights.

In some embodiments, if the first user has editing rights to the target task list, before sharing the target task list to the second user, an editing interface is displayed, where the editing interface is used to edit the access rights of the second user to the target task list. That is, the first user may edit the access rights that the second user has to the target task list before sharing the target task list to the second user.

If the first user has editing authority on the target task list, after the target task list is shared to the second user, the access authority of the second user on the target task list is modified in response to editing operation triggered by the first user. That is, the first user may modify the access rights that the second user has to the target task list after sharing the target task list to the second user.

That is, the first user may modify the access right of the second user to the target task list when sharing the target task list to the second user, or after sharing, so as to provide different operation modes for the user, thereby improving operation convenience.

Specifically, when the first user triggers the sharing operation for the target task list, a user to be shared (the second user) may be selected on the sharing interface, and the access right of the second user for the target task list may be edited. For ease of understanding, the first user is illustrated as triggering a sharing operation at the task center interface.

Referring to fig. 2a, a target task list entitled "innovation related" is displayed on the task center interface, and the first user displays the sharing interface 300 by triggering the sharing control. The first user in the sharing interface 300 may search for information about the user, group, etc. to be shared, or enter the selection interface 400 by triggering the "+" control. Individual users or groups in an organization architecture may be selected through selection interface 400.

After the user determines the user to share through the sharing interface 300 or the selection interface 400, a user identification of the selected second user may be displayed in the sharing interface 300, which may include a user avatar and a user name. Wherein for the selected second user, the second user may be given default access rights, e.g. read rights, for the target task list. Or during sharing operation, setting the access right of the second user to the target task list. For example, as shown in fig. 2b, user identifiers of the selected plurality of second users are displayed in the invitation frame, and access rights of the plurality of second users to the target task list may be set. In this case, the access rights corresponding to the plurality of second users are the same, and may specifically be readable rights or editable rights. Or, as shown in fig. 2c, the user identifiers of the selected multiple second users are displayed in a row, and the first user can set access rights of the multiple second users respectively, so as to set different access rights for different second users.

After the access rights corresponding to the second users are set through the sharing interface 300, the sending control is triggered, and the target task list is shared to the display interface corresponding to the second users.

After the first user shares the target task list with the second user through the task center interface, the second user can view the target task list on the corresponding task center interface, and/or the second user can view the target task list on a session interface established by the second user and the first user.

S102: and 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.

After the sharing operation is completed, the client displays 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. That is, when the second user has access or no access to the target task list, the preview data that can be seen by the display interface is different.

Under the scene that the first user shares the target task list into the first session, a display interface of the second user corresponding to the sharing operation is an interface of the first session, and the first user and the second user are members of the first session. Or under the scene that the first user shares the target task list to the first cloud document, the display interface of the second user corresponding to the sharing operation is a cloud document interface of the first cloud document, and the first user and the second user are collaborators of the first cloud document. Specifically, when the first user shares the target task list, all or part of members in the first session may be selected for sharing, or all or part of collaborators in the first cloud document may be selected for sharing, which is not limited herein.

In this embodiment, the task list is a task container, and is used to accommodate tasks, where one or more tasks may be included in the task list, and in some embodiments, the task list may also have a state that includes 0 tasks. In some embodiments, tasks may be created in a task list, existing tasks may be added to the task list, and various tasks therein may be managed and operated based on the task list. In some embodiments, the task list may exist independently of other entities in the client. For example, task listings are not dependent on groups, teams, documents, meetings, collaboration spaces, departments, projects, and other entities. The client may be an application for collaborative office, such as an application with IM functionality as a main, task functionality as a main, or an office suite application integrating IM, task, document, etc.

In some implementations, a user can trigger an operation in the interface of the session to add the target task list as a session tab page. Specifically, the user may add the same task list as a session tab page to a plurality of sessions having no association, or add the same task list as a session tab page to a plurality of sessions having a specific association.

Wherein, no association relationship among the plurality of sessions may refer to: there is no relationship between multiple sessions and multiple sessions are not subordinate to the same other entity (e.g., group, team, workspace, department, project, etc.), e.g., the first session and the second session are not sessions under the same team or workspace. It follows that in these embodiments, task lists may be flexibly and freely added to the session tags of any session. Having a specific associative relationship between multiple sessions may refer to: multiple sessions are subordinate to the same other entity (e.g., group, team, workspace, department, project, etc.).

As can be seen, when a sharing operation triggered by the first user on the target task list is received, determining that the sharing operation corresponds to the access right of the second user on the target task list. Wherein the second user is a shared user. And after the access right of the second user to the target task list is determined, 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. That is, by the technical scheme provided by the embodiment of the disclosure, the task list can be shared, and the access right of the shared user to the task list is determined during sharing, so that preview data of the task list is displayed on the display interface corresponding to the shared user according to the access right, thereby being convenient for different users to check information of the task list and improving user experience.

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

If the second user has access rights to the target task list, the preview data at least includes one or more of the following: the title of the target task list, the owner identification of the target task list, the collaborator identification of the target task list, and the access rights information possessed by the second user. Wherein the collaborators of the target task list, i.e., the members of the target task list, can read or edit the target task list. If the second user does not have access rights to the target task list, the preview data comprises first prompt information and a first control. The first prompt message is used for prompting that the target task list does not have access rights, and the first control is used for applying for the access rights.

In some embodiments, if the second user has access to the target task list and the target task list includes overdue tasks, the preview data may include information about overdue tasks, and in some embodiments, the information about overdue tasks may include overdue task numbers; and/or the preview data includes relevant information of at least part of the tasks in the target task list, wherein the relevant information of at least part of the tasks can include task titles, creators, deadlines, the number of subtasks included in the parent tasks, and the like.

In some embodiments, if the second user has access to the target task list, the preview data includes one or more of the following controls: the second control is used for opening a target task list at the task center interface; the third control is used for adding the target task list as a session label of the session interface if the display interface corresponding to the second user is the session interface; and the fourth control is used for copying the link of the target task list.

Because the link of the target task list can be copied through the fourth control, the sharing operation triggered by the first user on the target task list can be shared by triggering the fourth control. Specifically, responding to the triggering operation of the first user on the fourth control, and acquiring the link of the target task list; and responding to the sharing operation triggered by the link of the first user to the target task list, and determining the access right of the second user corresponding to the sharing operation for the target task list. Specifically, the first user may send the link of the target task list to the same session where the first user and the second user are both in by copying the link of the target task list, or paste the link of the target task list to the same cloud document where the first user and the second user are collaborators.

When the client displays the preview data corresponding to the target task list in the interface corresponding to the sharing operation of the second user based on the access right, the client can display the preview data in a preview card mode. Specifically, a preview card of the target task list is displayed in a display interface of the second user corresponding to the sharing operation, and preview data is carried through the preview card.

For example, as shown in fig. 3a, a target task list is shared in a session interface corresponding to the second user, and preview data corresponding to the target task list is displayed in the preview card 300. The method specifically comprises the header of a target task list, creator, overdue task number, collaborator identification and related information of part of the included tasks. Since the second user has readable rights to the target task list, second control 301, third control 302, and fourth control 303 may be presented in preview card 300.

In some embodiments, if the target task list is a blank task list (task list excluding tasks), the preview card is displayed in the format shown in fig. 3b, and the title of the target task list is "punch", creator, collaborator identifier, and blank document icon. Because the second user has readable rights to the target task list, the second control, the third control and the fourth control can be displayed in the preview card.

In some embodiments, if the target task list is deleted, a second prompt may be displayed in the preview card, where the second prompt is used to prompt that the target task list is deleted. After the target task list is deleted, the display style of the preview card is shown in fig. 3c, and the reading permission and the fourth control of the second user can still be displayed.

If the second user does not have access rights to the target task list, the display style of the preview card is shown in fig. 3d, and the first prompt message "you do not have access rights", the first control 304 and the fourth control 303 are displayed. Wherein, through the first control 304, the access authority can be applied to the owner of the target task list. When the user triggers the first control 304, a permission application interface may be displayed, as shown in fig. 4a, in the permission application interface 400, the user may modify the application of reading permission or editing permission, and may remark information in an input box displayed in the interface 400.

After the user sends the permission application to the owner of the target task list, the client may send a notification message to the owner to notify the owner that the user has access permission to the target task list. For example, as shown in FIG. 4b, a notification message may be automatically sent by the task assistant in which the user identification of the applicant, the title of the target task list, the remark information, the consent control, and the rejection control may be displayed. Whichever control the owner triggers, a notification message is sent to the applicant to inform the result of the application. When the owner triggers the consent control, a notification message sent to the applicant is shown in the upper diagram in fig. 4 c; when the owner triggers the reject control, a notification message is sent to the applicant as shown in the lower diagram in fig. 4 c.

In some embodiments, if the first user views the task list preview card, the preview card of the target task list is displayed in an interface of the first user corresponding to the sharing operation, where the preview card includes a fifth control, and the fifth control is used to modify access rights of the second user to the target task list. For example, as shown in FIG. 4d, when a user sharing a target task list views a preview card of the target task list through a session interface, a fifth control 305 may be displayed to modify access rights to the target task list for members in the session through the fifth control 305.

In this embodiment, the second user may further obtain a link of the target task list by triggering a fourth control displayed in the preview card of the target task list, so as to share the target task list again, thereby facilitating more users to view relevant information of the target task request.

Based on the above method embodiments, the embodiments of the present disclosure further provide a task list sharing device and an electronic device, and the description will be made with reference to the accompanying drawings.

Referring to fig. 5, which is a block diagram of a task list sharing device according to an embodiment of the disclosure, as shown in fig. 5, the sharing device 500 may include: a determination unit 501 and a display unit 502.

A determining unit 501, configured to determine, in response to a sharing operation triggered by a first user on a target task list, an access right of a second user corresponding to the sharing operation to the target task list;

and the display unit 502 is configured to display 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.

In some embodiments, the display unit 502 is further configured to display an independent window in response to a triggering operation of the second user on the target task list in the display interface, and display information in the target task list in the independent window.

In some embodiments, if the second user has access to the target task list, the preview data includes at least one or more of: the title of the target task list, the owner identification of the target task list, the identification of the collaborator of the target task list and the access right information of the second user; or if the second user does not have access rights to the target task list, the preview data comprises first prompt information and a first control, the first prompt information is used for prompting that the second user does not have access rights to the target task list, and the first control is used for applying for the access rights.

In some embodiments, the access rights include edit rights or read rights.

In some embodiments, if the second user has access to the target task list and the target task list includes overdue tasks, the preview data includes information about overdue tasks; alternatively, the preview data includes information about at least a portion of the tasks in the target task list.

In some embodiments, if the second user has access to the target task list, the preview data includes one or more of the following controls:

the second control is used for opening the target task list at a task center interface;

the third control is used for adding the target task list as a session label of the session interface if the display interface corresponding to the second user is the session interface;

and the fourth control is used for copying the link of the target task list.

In some embodiments, the determining unit 501 is specifically configured to obtain, in response to an operation triggered by the first user to copy the link of the target task list, the link of the target task list; and responding to the sharing operation triggered by the link of the first user to the target task list, and determining the access right of the second user corresponding to the sharing operation for the target task list.

In some embodiments, the second user has no higher access rights to the target task list than the first user has to the target task list.

In some embodiments, the apparatus further comprises: a modifying unit;

the display unit 501 is further configured to display an editing interface, if the first user has editing authority for the target task list, before sharing the target task list to the second user, where the editing interface is configured to edit the access authority of the second user for the target task list;

and the modification unit is used for responding to the editing operation triggered by the first user after sharing the target task list to the second user if the first user has editing authority on the target task list, and modifying the access authority of the second user on the target task list.

In some embodiments, the display unit 502 is specifically configured to display a preview card of the target task list in a display interface of the second user corresponding to the sharing operation.

In some embodiments, the display unit 502 is further configured to display a preview card of the target task list in an interface of the first user corresponding to the sharing operation, where the preview card includes a fifth control, and the fifth control is configured to modify an access right of the second user to the target task list.

In some embodiments, the display unit 502 is further configured to display a second prompt in the preview card if the target task list is deleted, where the second prompt is used to prompt that the target task list is deleted.

In some embodiments, the display interface of the second user corresponding to the sharing operation 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 of the second user corresponding to the sharing operation is a cloud document interface of a first cloud document, and the first user and the second user are collaborators of the first cloud document.

It should be noted that, for specific implementation of each unit in this embodiment, reference may be made to the related description in the above method embodiment. The division of the units in the embodiments of the disclosure is illustrative, only one logic function division, and there may be another division manner when actually implemented. Each functional unit in the embodiments of the present disclosure may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. For example, in the above embodiment, the processing unit and the transmitting unit may be the same unit or may be different units. The integrated units may be implemented in hardware or in software functional units.

Referring to fig. 6, a schematic structural diagram of an electronic device 600 suitable for use in implementing embodiments of the present disclosure is shown. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and the like, and stationary terminals such as digital TVs, desktop computers, and the like. The electronic device shown in fig. 6 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.

As shown in fig. 6, the electronic device 600 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 601, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data required for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

In general, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, magnetic tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 shows an electronic device 600 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a non-transitory computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 609, or from storage means 608, or from ROM 602. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing device 601.

The electronic device provided by the embodiment of the present disclosure belongs to the same inventive concept as the method provided by the above embodiment, and technical details not described in detail in the present embodiment can be seen in the above embodiment, and the present embodiment has the same beneficial effects as the above embodiment.

The present disclosure provides a computer storage medium having stored thereon a computer program which, when executed by a processor, implements the method provided by the above embodiments.

It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

In some implementations, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (Hyper Text Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the method described above.

Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the first user computer, partly on the first user computer, as a stand-alone software package, partly on the first user computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the first user computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. Where the names of the units/modules do not constitute a limitation of the units themselves in some cases.

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection 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, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

It should be noted that, in the present description, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different manner from other embodiments, and identical and similar parts between the embodiments are all enough to refer to each other. For the system or device disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple, and the relevant points refer to the description of the method section.

It should be understood that in embodiments of the present disclosure, "at least one" means one or more, and "a plurality" means two or more. "and/or" for describing the association relationship of the association object, the representation may have three relationships, for example, "a and/or B" may represent: only a, only B and both a and B are present, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

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

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the embodiments of the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the embodiments of the disclosure. Thus, the embodiments of the present disclosure are not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (16)

1. A task list sharing method, the method comprising:

responding to a sharing operation triggered by a first user on a target task list, and determining the access right of a second user corresponding to the sharing operation for the target task list;

and 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.

2. The method according to claim 1, wherein the method further comprises:

and responding to the triggering operation of the second user on the target task list in the display interface, displaying an independent window, and displaying information in the target task list in the independent window.

3. The method of claim 1, wherein the step of determining the position of the substrate comprises,

if the second user has access rights to the target task list, the preview data at least includes one or more of the following: the title of the target task list, the owner identification of the target task list, the identification of the collaborator of the target task list and the access right information of the second user;

or alternatively, the process may be performed,

if the second user does not have access rights to the target task list, the preview data comprises first prompt information and a first control, the first prompt information is used for prompting that the target task list does not have access rights, and the first control is used for applying for the access rights.

4. The method of claim 1, wherein the access rights comprise edit rights or read rights.

5. The method of claim 1, wherein the step of determining the position of the substrate comprises,

if the second user has access rights to the target task list and the target task list comprises overdue tasks, the preview data comprises relevant information of overdue tasks;

and/or the number of the groups of groups,

the preview data includes information about at least a portion of the tasks in the target task list.

6. The method of claim 1, wherein if the second user has access to the target task list, the preview data includes one or more of the following controls:

the second control is used for opening the target task list at a task center interface;

the third control is used for adding the target task list as a session label of the session interface if the display interface corresponding to the second user is the session interface;

and the fourth control is used for copying the link of the target task list.

7. The method of claim 1, wherein determining, in response to a sharing operation triggered by a first user on a target task list, an access right of a second user corresponding to the sharing operation for the target task list includes:

responding to the operation of copying the link of the target task list triggered by the first user, and acquiring the link of the target task list;

and responding to the sharing operation triggered by the link of the first user to the target task list, and determining the access right of the second user corresponding to the sharing operation for the target task list.

8. The method of claim 1, wherein the second user has no higher access rights to the target task list than the first user has to the target task list.

9. The method of claim 1, further comprising one or more of:

if the first user has editing authority on the target task list, displaying an editing interface before sharing the target task list to the second user, wherein the editing interface is used for editing the access authority of the second user on the target task list;

and if the first user has editing authority on the target task list, after the target task list is shared to the second user, responding to editing operation triggered by the first user, and modifying the access authority of the second user on the target task list.

10. The method according to any one of claims 1-9, wherein the displaying preview data corresponding to the target task list in a display interface of the second user corresponding to the sharing operation based on the access rights includes:

and displaying the preview card of the target task list in a display interface of the second user corresponding to the sharing operation.

11. The method of claim 10, wherein the method further comprises:

And displaying a preview card of the target task list in an interface of the first user corresponding to the sharing operation, wherein the preview card comprises a fifth control, and the fifth control is used for modifying the access authority of the second user to the target task list.

12. The method according to claim 10, wherein the method further comprises:

and if the target task list is deleted, displaying second prompt information in the preview card, wherein the second prompt information is used for prompting that the target task list is deleted.

13. The method of claim 1, wherein the display interface of the second user corresponding to the sharing operation is a session interface of a first session, the first user and the second user being members of the first session; or alternatively, the process may be performed,

the display interface of the second user corresponding to the sharing operation is a cloud document interface of a first cloud document, and the first user and the second user are collaborators of the first cloud document.

14. A task list sharing apparatus, wherein the apparatus comprises:

the determining unit is used for responding to the sharing operation triggered by the first user on the target task list and determining the access right of the second user corresponding to the sharing operation on the target task list;

And the display unit is used 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.

15. An electronic device, the device comprising: a processor and a memory;

the memory is used for storing instructions or computer programs;

the processor for executing the instructions or computer program in the memory to cause the electronic device to perform the method of any of claims 1-13.

16. A computer readable storage medium having instructions stored therein which, when executed on a device, cause the device to perform the method of any of claims 1-13.

Images