Kanban management method and device and storage medium

Abstract

The invention provides a billboard management method and device and a storage medium, relates to the technical field of computers, and is used for enabling a worker without development experience to complete the design of a billboard and meeting the personalized requirements of the worker. The method comprises the following steps: acquiring a management instruction of a first account, wherein the management instruction is used for indicating that target index information is displayed on a target billboard through a target component; and associating the target index information with the target component to obtain the associated target component. And filling the associated target component into the target billboard.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a management method, device and storage medium for a kanban board. Background Art

[0002] In the context of industrial digitalization, enterprises are in urgent need of a digital management system to achieve integrated and unified management of business indicators. Since enterprises have different levels of staff, the tasks and business indicators of staff at each level are different.

[0003] Currently, the dashboard of the management system can be designed by writing code, and then the dashboard can be displayed on a monitor, so that the staff can monitor the business indicators on the dashboard through the monitor. However, the design of the dashboard by writing code requires the operation or auxiliary operation of the developer. The staff without development experience cannot complete the design of the dashboard, and it is difficult to meet the personalized needs of the staff. Summary of the invention

[0004] The present application provides a management method, device and storage medium of a kanban board, which are used to enable staff without development experience to complete the design of a kanban board and meet the personalized needs of the staff.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions:

[0006] In a first aspect, the present application provides a method for managing a dashboard. The method includes: a management device for a dashboard (hereinafter referred to as a "management device") obtains a management instruction of a first account, and the management instruction is used to instruct to display target indicator information on a target dashboard through a target component. The management device can associate the target indicator information with the target component to obtain an associated target component. The management device can fill the associated target component into the target dashboard.

[0007] The technical solution provided by the present application brings at least the following beneficial effects: the management device can obtain the management instruction of the first account, and the management instruction is used to instruct to display the target indicator information through the target component on the target dashboard. The management device can associate the target indicator information with the target component to obtain the associated target component. The management device can fill the associated target component into the target dashboard. In this way, the staff can perform operations on the target component and fill the target component of the associated data into the target dashboard, and the design and management of the target dashboard can be completed without writing code. In this way, the staff can create and manage the target dashboard according to personal needs to meet personalized needs.

[0008] Optionally, the management method of the dashboard also includes: in response to a hierarchy creation instruction, the management device can create multiple preset hierarchy nodes, the hierarchy creation instruction is used to instruct the creation of multiple preset hierarchy nodes, and one preset hierarchy node corresponds to one target dashboard.

[0009] Optionally, a parent-child relationship exists between multiple preset hierarchical nodes; the hierarchical creation instruction includes: a first creation instruction or a second creation instruction, the first creation instruction is used to instruct the addition of multiple newly added hierarchical nodes based on the historical hierarchical nodes, and the second creation instruction is used to instruct the creation of multiple new preset hierarchical nodes. The above-mentioned "creating multiple preset hierarchical nodes in response to the hierarchical creation instruction" includes: if the hierarchical creation instruction is the first creation instruction, the management device can obtain the historical hierarchical nodes, use the parent nodes of the multiple newly added hierarchical nodes as the child nodes of the terminal nodes in the historical hierarchical nodes, and create multiple preset hierarchical nodes according to the parent-child relationship. If the hierarchical creation instruction is the second creation instruction, the management device can use the parent nodes of the multiple hierarchical nodes as the root nodes, and create multiple preset hierarchical nodes according to the parent-child relationship.

[0010] Optionally, the target component is a map. The management method of the dashboard further includes: for each preset level node, in response to a fence drawing instruction, the management device may draw a fence corresponding to the preset level node in the map, wherein the fence drawing instruction is used to instruct drawing the fence corresponding to the preset level node. The management device may verify the fence corresponding to each preset level node.

[0011] Optionally, the management device may obtain a dashboard request message of the second account and hierarchical authority information of the second account, wherein the dashboard request message is used to request viewing of a target dashboard, and the hierarchical authority information is used to indicate all hierarchical nodes that the second account can view, and the first account is different from the second account. If the hierarchical authority information contains a hierarchical node corresponding to the target dashboard, the management device may display the target dashboard.

[0012] Optionally, the management method of the dashboard further includes: if there is no hierarchical node corresponding to the target dashboard in the hierarchical permission information, the management device may receive an authorization request message from the second account, the authorization request message being used to request viewing the target dashboard. The management device may receive an authorization response message, the authorization response message being used to indicate that the second account is allowed to view the target dashboard. The management device may display the target dashboard.

[0013] In a second aspect, the present application provides a management device for a kanban board, the device comprising: an acquisition module and a processing module.

[0014] The acquisition module is used to acquire the management instruction of the first account, and the management instruction is used to instruct to display the target indicator information through the target component on the target dashboard. The processing module is used to associate the target indicator information with the target component to obtain the associated target component. The processing module is also used to fill the associated target component into the target dashboard.

[0015] Optionally, the processing module is further used to create multiple preset level nodes in response to a level creation instruction, where the level creation instruction is used to instruct the creation of multiple preset level nodes, and one preset level node corresponds to one target dashboard.

[0016] Optionally, a parent-child relationship exists between multiple preset hierarchical nodes; the hierarchical creation instruction includes: a first creation instruction or a second creation instruction, the first creation instruction is used to instruct the addition of multiple newly added hierarchical nodes based on the historical hierarchical nodes, and the second creation instruction is used to instruct the creation of multiple preset hierarchical nodes. The processing module is specifically used to obtain the historical hierarchical nodes if the hierarchical creation instruction is the first creation instruction, use the parent nodes of the multiple newly added hierarchical nodes as the child nodes of the terminal nodes in the historical hierarchical nodes, and create multiple preset hierarchical nodes according to the parent-child relationship. The processing module is specifically used to use the parent nodes of the multiple hierarchical nodes as the root nodes if the hierarchical creation instruction is the second creation instruction, and create multiple preset hierarchical nodes according to the parent-child relationship.

[0017] Optionally, the target component is a map. The processing module is further used to, for each preset level node, in response to a fence drawing instruction, draw a fence corresponding to the preset level node in the map, wherein the fence drawing instruction is used to instruct drawing the fence corresponding to the preset level node. The processing module is further used to verify the fence corresponding to each preset level node.

[0018] Optionally, the acquisition module is further used to acquire a dashboard request message of the second account and hierarchical authority information of the second account, wherein the dashboard request message is used to request to view the target dashboard, and the hierarchical authority information is used to indicate all hierarchical nodes that the second account can view, and the first account is different from the second account. The processing module is further used to display the target dashboard if a hierarchical node corresponding to the target dashboard exists in the hierarchical authority information.

[0019] Optionally, the acquisition module is further used to receive an authorization request message from the second account if there is no hierarchical node corresponding to the target dashboard in the hierarchical permission information, the authorization request message being used to request to view the target dashboard. The acquisition module is further used to receive an authorization response message, the authorization response message being used to indicate that the second account is allowed to view the target dashboard. The processing module is further used to display the target dashboard.

[0020] In a third aspect, the present application provides a kanban management device, the device comprising: a processor and a memory. The processor and the memory are coupled. The memory is used to store one or more programs, the one or more programs including computer-executable instructions, and when the kanban management device is running, the processor executes the computer-executable instructions stored in the memory to implement the kanban management method described in any possible implementation of the first aspect.

[0021] In a fourth aspect, the present application provides a computer-readable storage medium, in which instructions are stored. When the instructions are executed on a computer, the computer executes the kanban management method described in any possible implementation of the first aspect.

[0022] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, enables the computer to implement the kanban management method described in any possible implementation manner in the first aspect.

[0023] In the above scheme, the technical problems that can be solved and the technical effects achieved by the management device, computer equipment, computer storage medium or computer program product of the dashboard can be referred to the technical problems and technical effects solved by the above first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application, and do not constitute improper limitations on the present application.

[0025] Figure 1 is a schematic diagram of the architecture of a kanban management system according to an exemplary embodiment;

[0026] Figure 2 is a flow chart of a method for managing a kanban board according to an exemplary embodiment;

[0027] Figure 3 is a flow chart of another method for managing a kanban board according to an exemplary embodiment;

[0028] Figure 4 is a flow chart of another method for managing a kanban board according to an exemplary embodiment;

[0029] Figure 5 is a flow chart of another method for managing a kanban board according to an exemplary embodiment;

[0030] Figure 6 is a schematic diagram of a hierarchical creation interface according to an exemplary embodiment;

[0031] Figure 7 is a schematic diagram of an interface for creating a kanban board according to an exemplary embodiment;

[0032] Figure 8 is a schematic diagram of a kanban list according to an exemplary embodiment;

[0033] Fig. 9 is a structural block diagram of a kanban management device according to an exemplary embodiment;

[0034] Fig.10 is a structural schematic diagram of a kanban management device according to an exemplary embodiment;

[0035] Fig.11 The present invention is a conceptual partial view of a computer program product according to an exemplary embodiment. DETAILED DESCRIPTION

[0036] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0037] In this article, the character " / " generally indicates that the objects before and after are in an "or" relationship. For example, A / B can be understood as A or B.

[0038] The terms “first” and “second” in the description and claims of the present application are used to distinguish different objects rather than to describe a specific order of the objects.

[0039] In addition, the terms "including" and "having" and any variations thereof mentioned in the description of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or modules is not limited to the listed steps or modules, but may optionally include other steps or modules that are not listed, or may optionally include other steps or modules that are inherent to these processes, methods, products or devices.

[0040] In addition, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present concepts in a specific way.

[0041] Before introducing the management method of the dashboard of the embodiment of the present application in detail, the implementation environment and application scenarios of the embodiment of the present application are first introduced.

[0042] In the context of industrial digitalization, enterprises are in urgent need of a digital management system to achieve integrated and unified management of business indicators. Since enterprises have different levels of staff, the tasks and business indicators of staff at each level are different.

[0043] Currently, the dashboard of the management system can be designed by writing code, and then the dashboard can be displayed on a monitor, so that the staff can monitor the business indicators on the dashboard through the monitor. However, the design of the dashboard by writing code requires the operation or auxiliary operation of the developer. The staff without development experience cannot complete the design of the dashboard, and it is difficult to meet the personalized needs of the staff.

[0044] In order to solve the above problems, an embodiment of the present application provides a management method for a dashboard, the method comprising: a server can obtain a management instruction of a first account, and the management instruction is used to instruct to display the target indicator information through the target component on the target dashboard. The server can associate the target indicator information with the target component to obtain the associated target component. The server can fill the associated target component into the target dashboard. In this way, the staff can perform operations on the target component and fill the target component of the associated data into the target dashboard, and the design and management of the target dashboard can be completed without writing code. In this way, the staff can create and manage the target dashboard according to personal needs to meet personalized needs.

[0045] The implementation environment of the embodiments of the present application is introduced below.

[0046] Figure 1 The schematic diagram of the architecture of a kanban management system according to an exemplary embodiment is shown. The architecture includes: a management device (such as a server 101) and a client 102. The server 101 and the client 102 can perform wired / wireless communication.

[0047] The server 101 may be a single physical server, or a server cluster consisting of multiple servers. Alternatively, the server cluster may be a distributed cluster. Alternatively, the server may be a cloud server. The embodiments of the present application do not limit the specific implementation of the server.

[0048] In the embodiment of the present application, the server 101 may receive an operation instruction from the client 102. The server 101 may respond to the operation instruction and lay out the billboard. The server 101 may display the billboard through the client 102.

[0049] The client 102 can be used to send the staff's operation instructions to the server 101.

[0050] It should be noted that in the embodiment of the present application, the client can perform data transmission with the server. The client can be a program that provides local services to the staff. For example, the client can be an application program that runs locally. For another example, the client can be a web browser used for the World Wide Web. For another example, the client can be instant messaging software. The client can be deployed on the server or on other hardware devices.

[0051] The embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0052] Take the application of Kanban management method to the server as an example. Figure 2 As shown, a method for managing a kanban board provided in an embodiment of the present application includes:

[0053] S201. The server obtains a management instruction for a first account.

[0054] The management instruction is used to instruct the target indicator information to be displayed on the target dashboard through the target component.

[0055] In a possible implementation, the server is connected to the client. The staff can log in to the first account. The staff can use the first account to send a management instruction to the server through the client. The server can receive the management instruction from the client to obtain the management instruction of the first account.

[0056] In an embodiment of the present application, before a staff member uses the first account to send a management instruction to the server through the client, the super administrator may authorize the first account so that the first account has the authority to manage the dashboard.

[0057] Specifically, the super administrator may issue an authorization certificate to the first account; or, the super administrator may add the identifier of the first account to the authorized account identifier.

[0058] It should be noted that in the embodiment of the present application, the permissions granted to the first account include: hierarchy management permissions, data source management permissions, and dashboard management permissions. Among them, the hierarchy management permissions are used to indicate that the first account is allowed to create custom hierarchy nodes, and the first account is allowed to authorize the created custom hierarchy nodes to other accounts to jointly view or call custom hierarchy nodes. The data source management permissions are used to indicate that the first account is allowed to perform application programming interface (API) data source docking, and the first account is allowed to authorize the created data source as a whole to other accounts to jointly view or call the data source. For the authorization of the data source, this application supports the authorization of the entire data source, but does not support the separate authorization of a certain indicator information. The dashboard management permissions are used to indicate that the first account is allowed to perform operations such as dashboard creation, editing, and preview, and the first account is allowed to authorize the created dashboard to other accounts, and decide whether to allow other accounts to manage the dashboard (i.e., the dashboard created by the first account). The permissions granted by the first account to other accounts may include: view only, editable, and manageable.

[0059] S202. The server associates the target indicator information with the target component to obtain the associated target component.

[0060] In a possible implementation, the server stores a plurality of preset components. The server may determine a target component from the plurality of preset components. The server may associate the target indicator information with the target component to obtain the associated target component.

[0061] In an embodiment of the present application, the server may obtain a data source, which includes a plurality of preset indicator information. The server may determine target indicator information from the plurality of preset indicator information. Afterwards, the server may map the target indicator information with the target component to obtain the associated target component.

[0062] It should be noted that, in the embodiment of the present application, the indicator information may include: indicator fields and indicator data. The data source may be obtained by obtaining the data source through an API or by obtaining the data source through a static file.

[0063] In a possible design, the preset components may include at least one of the following: a basic component, a chart component, an interactive component, and an independent component.

[0064] Specifically, basic components may include: text (suitable for titles), pictures (suitable for backgrounds, legends), digital text (suitable for connecting to data sources to display numbers), etc.; chart components may include: tables, bar charts, line charts, pie charts, etc.; interactive components may include: drop-down selectors, account period selectors, search boxes, Tab lists, switches, hierarchical selectors, etc.; independent components may include: iframes, resource information panels, maps, custom picture frames, etc.

[0065] S203: The server fills the associated target components into the target dashboard.

[0066] In a possible implementation, the staff can perform a target operation on the target component through the first account to move the associated target component to the target dashboard. In response to the target operation, the server can fill the associated target component into the target dashboard.

[0067] It should be noted that, in the embodiment of the present application, the target operation may be a click operation, or the target operation may be a drag operation.

[0068] In an embodiment of the present application, the target component has component attributes, and the component attributes include at least one of the following: size, color, style, trigger condition, and associated hierarchical node. The staff can perform a selection operation on the target component through the first account, and the selection operation is used to adjust the component attributes of the target component. In response to the selection operation, the server can adjust the component attributes of the target component.

[0069] It is understandable that the server can obtain the management instruction of the first account, and the management instruction is used to instruct to display the target indicator information through the target component on the target dashboard. The server can associate the target indicator information with the target component to obtain the associated target component. The server can fill the associated target component into the target dashboard. In this way, the staff can perform operations on the target component and fill the target component of the associated data into the target dashboard, and the design and management of the target dashboard can be completed without writing code. In this way, the staff can create and manage the target dashboard according to personal needs to meet personalized needs.

[0070] In some embodiments, Figure 3 As shown, before the server obtains the management instruction of the first account (S201), the board management method may further include S301.

[0071] S301. In response to a hierarchy creation instruction, the server creates a plurality of preset hierarchy nodes.

[0072] In a possible implementation, the server may receive a hierarchy creation instruction. In response to the hierarchy creation instruction, the server may create a plurality of preset hierarchy nodes.

[0073] In the embodiment of the present application, the level creation instruction includes: a first creation instruction or a second creation instruction. The first creation instruction is used to instruct to add multiple new level nodes based on the historical level nodes, and the second creation instruction is used to instruct to create multiple preset level nodes.

[0074] In a possible design, the server may store historical hierarchical nodes. If the hierarchical creation instruction is the first creation instruction, the server may obtain the historical hierarchical nodes and use the parent nodes of the multiple newly added hierarchical nodes as the child nodes of the terminal nodes in the historical hierarchical nodes. Afterwards, the server may create multiple preset hierarchical nodes according to the parent-child relationship.

[0075] It should be noted that, in the embodiment of the present application, the parent node among the multiple newly added hierarchical nodes is a node without a parent node among the multiple newly added hierarchical nodes, that is, a root node among the multiple newly added hierarchical nodes.

[0076] For example, if the historical level nodes include: provincial level, municipal level, district level, and the newly added level nodes include: grid level, sub-district level. Among them, the grid level is the parent node of the sub-district level, and the sub-district level is the child node of the grid level. Then the terminal node in the historical level nodes is the district level, and the parent node in the newly added level nodes is the grid level, and the grid level is used as the child node of the district level, that is, the multiple preset level nodes include: provincial level, municipal level, district level, grid level, sub-district level.

[0077] In another possible design, if the level creation instruction is the second creation instruction, the server can use the parent node of multiple preset level nodes as the root node. After that, the server can create multiple preset level nodes according to the parent-child relationship.

[0078] It should be noted that, in the embodiment of the present application, the parent node of the multiple preset level nodes is the node without a parent node among the multiple preset level nodes.

[0079] For example, if multiple preset hierarchical nodes include: city level, district level, grid level, and sub-district level. Among them, the city level is the parent node of the district level, the district level is the parent node of the grid level, the grid level is the parent node of the sub-district level, the district level is the child node of the city level, the grid level is the child node of the district level, and the sub-district level is the child node of the grid level. Since the city level has no parent node, the parent node of multiple hierarchical nodes is the city level, and the city level is used as the root node, that is, multiple preset hierarchical nodes include: city level, district level, grid level, and sub-district level.

[0080] In some embodiments, one preset level node corresponds to one target dashboard, and each preset level node corresponds to a different target dashboard.

[0081] For example, if the multiple preset level nodes include: provincial level, city level, district level, and grid level, then the provincial level corresponds to a target dashboard, the city level corresponds to a target dashboard, the district level corresponds to a target dashboard, and the grid level corresponds to a target dashboard.

[0082] It should be noted that, in the embodiment of the present application, one preset level node corresponds to one target dashboard, so that the staff can select the preset level node to view the target dashboard corresponding to the preset level node.

[0083] It is understandable that in response to the hierarchical creation instruction, the server can create multiple preset hierarchical nodes, and the hierarchical creation instruction is used to instruct the creation of multiple preset hierarchical nodes, and one preset hierarchical node corresponds to a target kanban. In this way, different kanbans can be viewed by staff at different levels, which is convenient for managing the kanban. There is a parent-child relationship between multiple preset hierarchical nodes, and the hierarchical creation instruction includes: a first creation instruction or a second creation instruction, the first creation instruction is used to indicate the addition of multiple newly added hierarchical nodes based on historical hierarchical nodes, and the second creation instruction is used to indicate the creation of multiple preset hierarchical nodes. If the hierarchical creation instruction is the first creation instruction, the server can obtain the historical hierarchical nodes, use the parent nodes in the multiple newly added hierarchical nodes as the child nodes of the terminal nodes in the historical hierarchical nodes, and create multiple preset hierarchical nodes according to the parent-child relationship. If the hierarchical creation instruction is the second creation instruction, the server can use the parent nodes in the multiple hierarchical nodes as the root nodes, and create multiple preset hierarchical nodes according to the parent-child relationship. In this way, staff can create custom hierarchical nodes, or add hierarchical nodes based on historical hierarchical nodes to meet the personalized needs of staff.

[0084] In some embodiments, when the target component is a map, after creating multiple preset level nodes in response to a level creation instruction, the management method of the dashboard may further include: for each preset level node, in response to a fence drawing instruction, the server may draw a map fence corresponding to the preset level node in the map to obtain multiple map fences.

[0085] Among them, the fence drawing instruction is used to instruct the drawing of the map fence corresponding to the preset level node.

[0086] It should be noted that, in the embodiment of the present application, the staff can perform a continuous click operation on the map through the first account. In response to the continuous click operation, the server can draw a map fence corresponding to the preset level node in the map.

[0087] In an embodiment of the present application, the server may verify multiple map fences.

[0088] In a possible implementation, the server may classify multiple preset level nodes to determine multiple level types, each level type including at least one preset level node. For each level type, the server may determine whether there is an overlapping area between map fences corresponding to any two preset level nodes in at least one preset level node.

[0089] In one possible design, if there is an overlapping area between the map fences corresponding to any two preset level nodes, the server can determine that multiple map fences have failed verification.

[0090] For example, if the multiple level types include provincial and municipal levels, at least one preset level node of the provincial level includes Province A, and at least one preset level node of the municipal level includes City B and City C. Since there is only Province A at the provincial level, there is no need to determine whether there is an overlapping area. The server can determine whether there is an overlapping area between the map fence corresponding to City B and the map fence corresponding to City C. If there is an overlapping area between the map fence corresponding to City B and the map fence corresponding to City C, the server can determine that multiple map fences have failed verification.

[0091] In an embodiment of the present application, the server may redraw the map fence.

[0092] In another possible design, there is a parent-child relationship between multiple level types, the child level type includes at least one child level node, and the parent level type includes at least one parent level node. If there is an overlapping area between the map fences corresponding to at least one preset level node, the server can determine at least one child level node corresponding to each parent level node in each parent level type. For each parent level node, the server can determine the total fence corresponding to the parent level node based on the map fence corresponding to each child level node in at least one child level node corresponding to the parent level node. The server can determine whether the total fence corresponding to the parent level node exceeds the map fence corresponding to the parent level node. If the total fence corresponding to the parent level node exceeds the map fence corresponding to the parent level node, the server can treat the parent level node as an abnormal level node. If the total fence corresponding to the parent level node does not exceed the map fence corresponding to the parent level node, the server can do nothing.

[0093] Exemplarily, if multiple level types include provincial and municipal levels, at least one preset level node at the provincial level includes Province A and Province D, and at least one preset level node at the municipal level includes: City B, City C, City E, and City F, wherein City B and City C are both sub-level level nodes of Province A, and City E and City F are both sub-level level nodes of Province D. The server can determine the total fence corresponding to Province A based on the map fence corresponding to City B and the map fence corresponding to City C. The server can determine whether the total fence corresponding to Province A exceeds the map fence corresponding to Province A. If the total fence corresponding to Province A exceeds the map fence corresponding to Province A, the server will treat Province A as an abnormal level node. Similarly, the server can determine the total fence corresponding to Province D based on the map fence corresponding to City E and the map fence corresponding to City F. The server can determine whether the total fence corresponding to Province D exceeds the map fence corresponding to Province D. If the total fence corresponding to Province D does not exceed the map fence corresponding to Province D, the server will not perform any operation.

[0094] In an embodiment of the present application, the server may determine whether there is an abnormal level node in at least one parent level node to determine whether multiple map fences pass verification.

[0095] In one possible design, if there is an abnormal level node in at least one parent level node, the server can determine that multiple map fences have failed verification.

[0096] In another possible design, if there are no abnormal level nodes in at least one parent level node, the server can determine that multiple map fences pass verification.

[0097] That is, if there is an overlapping area between the map fences corresponding to any two preset level nodes, and there is no abnormal level node in at least one parent level node, the server can determine that multiple map fences pass the verification.

[0098] It is understandable that, when the target component is a map, for each preset level node, in response to the fence drawing instruction, the server can draw a map fence corresponding to the preset level node in the map, and obtain multiple map fences, and the fence drawing instruction is used to instruct the drawing of the map fence corresponding to the preset level node. The server can verify the multiple map fences. In this way, when the staff manages the target kanban whose target component is a map, each preset level node can be managed according to the map fence to avoid exceeding the management scope of the staff.

[0099] It should be noted that after the first account creates the target dashboard corresponding to each preset level node, the staff can view or use the target dashboard using the first account, and can also view or use the target dashboard using other accounts (such as the second account).

[0100] In some embodiments, Figure 4 As shown, the management method of the kanban board may further include: S401-S405.

[0101] S401. The server obtains a dashboard request message of a second account and hierarchical authority information of the second account.

[0102] The first account is different from the second account. The dashboard request message is used to request to view the target dashboard, and the level permission information is used to indicate all level nodes that the second account can view.

[0103] In a possible implementation, the staff can log in to the second account. The staff can use the second account to send a kanban request message to the server through the client. The server can receive the kanban request message from the client to obtain the kanban request message from the client.

[0104] In an embodiment of the present application, the dashboard request message may include the level information of the second account. The server may determine the level authority information of the second account according to the level information of the second account to obtain the level authority information of the second account.

[0105] In one possible design, the hierarchical authority information may include: the hierarchical node where the second account is located and the hierarchical nodes lower than the hierarchical node where the second account is located.

[0106] Exemplarily, if the preset hierarchical nodes include: provincial level, municipal level, district level, and grid level, and the hierarchical information of the second account is district level, then the hierarchical authority information of the second account may include: district level and grid level.

[0107] S402: The server determines whether there is a hierarchical node corresponding to the target dashboard in the hierarchical authority information.

[0108] In a possible implementation, the server may determine the level node corresponding to the target dashboard according to the dashboard request message. The server stores all the level nodes that the second account can view. The server may determine whether there is a level node that is the same as the level node corresponding to the target dashboard among all the level nodes viewed by the second account.

[0109] In a possible design, if there is no level node identical to the level node corresponding to the target dashboard among all level nodes viewed by the second account, the server may determine that there is no level node corresponding to the target dashboard in the level permission information.

[0110] In the embodiment of the present application, if there is no hierarchical node corresponding to the target dashboard in the hierarchical authority information, the server may execute S403-S405.

[0111] In another possible design, if there is a level node identical to the level node corresponding to the target dashboard among all the level nodes viewed by the second account, the server may determine that there is a level node corresponding to the target dashboard in the level permission information.

[0112] In the embodiment of the present application, if there is a hierarchical node corresponding to the target dashboard in the hierarchical authority information, the server may execute S405.

[0113] S403: The server receives an authorization request message from the second account.

[0114] The authorization request message is used to request to view the target dashboard.

[0115] In a possible implementation, the second account may send an authorization request message to the server. The server may receive the authorization request message from the second account.

[0116] In an embodiment of the present application, after the server receives the authorization request message from the second account, the server may send an authorization request message to the first account.

[0117] It should be noted that in the embodiment of the present application, the manner in which the server sends the authorization request message to the first account is not limited. For example, the server may send the authorization request message to the first account in the form of a pop-up window. For another example, the server may send the authorization request message to the first account in the form of a message reminder. For another example, the server may send the authorization request message to the first account in the form of a text message.

[0118] S404: The server receives an authorization response message from the first account.

[0119] The authorization response message is used to indicate that the second account is allowed to view the target dashboard.

[0120] In a possible implementation, after the server sends an authorization request message to the first account, the first account may send an authorization response message to the server. The server may receive the authorization response message from the first account.

[0121] S405. The server displays the target signboard.

[0122] In a possible implementation, after the server receives the authorization response message from the first account, the server may display the target dashboard.

[0123] In some embodiments, the authorization response message may also be used to indicate that the second account is allowed to edit the target dashboard.

[0124] It should be noted that in the embodiment of the present application, after logging into the second account, the staff can not only view the target dashboard, but also edit the target dashboard to meet personalized needs.

[0125] It is understandable that the server can obtain the kanban request message of the second account and the hierarchical authority information of the second account. The kanban request message is used to request to view the target kanban, and the hierarchical authority information is used to indicate all hierarchical nodes that the second account can view, and the first account is different from the second account. If there is a hierarchical node corresponding to the target kanban in the hierarchical authority information, the server can display the target kanban. If there is no hierarchical node corresponding to the target kanban in the hierarchical authority information, the server can receive an authorization request message from the second account, and the authorization request message is used to request to view the target kanban. The server can receive an authorization response message from the first account, and the authorization response message is used to indicate that the second account is allowed to view the target kanban. The server can display the target kanban. In this way, the staff can use the second account to view the target kanban with the authorization of the first account, to ensure the security of the kanban and avoid malicious modification by others.

[0126] It should be noted that there is at least one indicator information in the target dashboard created by the first account. If the staff wants to modify the indicator information in the target dashboard created by the first account through the second account, data authorization of the first account is required.

[0127] In some embodiments, the server may receive an indicator request message from the second account, the indicator request message being used to request an operation on the indicator information in the target dashboard. The server may send an indicator authorization request to the first account. The server may receive an indicator response message from the first account, the indicator response message including at least one of the following: allowing viewing of the indicator information in the target dashboard, allowing editing of the indicator information in the target dashboard, and allowing management of the indicator information in the target dashboard.

[0128] It should be noted that, in the embodiment of the present application, editing the indicator information in the target dashboard may be operations such as adding, deleting, and modifying the data of the indicator information, and editing the indicator information in the target dashboard includes viewing the indicator information in the target dashboard. Managing the indicator information in the target dashboard may be operations such as changing the indicator information to other indicator information, and managing the indicator information in the target dashboard may include: viewing the indicator information in the target dashboard and editing the indicator information in the target dashboard.

[0129] In an embodiment of the present application, after the server receives the indicator response message from the first account, the server can respond accordingly to the indicator control operation of the second account based on the indicator response message of the first account, and the indicator control operation includes: performing a viewing operation on the indicator information, performing an editing operation on the indicator information, or performing a management operation on the indicator information.

[0130] For example, if the indicator response message includes permission to view the indicator information in the target dashboard, if the indicator control operation includes performing a viewing operation on the indicator information, the server may display the indicator information in the target dashboard, and if the indicator control operation includes performing an editing operation on the indicator information, the server ignores the indicator control operation.

[0131] It is understandable that the first account can authorize the second account to perform data operations on the indicator information in the target dashboard. In this way, the security of the data in the dashboard can be guaranteed to avoid malicious modification by others.

[0132] The following is an introduction to the kanban management method of the present application in conjunction with a specific embodiment. Figure 5 As shown, it shows a flowchart of another kanban management method. The super administrator can authorize the first account so that the staff has the hierarchy management authority, data management authority, and kanban management authority. The first account can log in to the kanban management system, create a custom hierarchy node, create a data source, and create a kanban.

[0133] In an embodiment of the present application, for creating a custom hierarchical node, the first account can determine whether to use the hierarchical node stored in the user center (i.e., the historical hierarchical node). If the hierarchical node stored in the user center is used, the first account can choose to reference the hierarchical node of the user center and create a custom hierarchical node at the node end of the hierarchical node. If the hierarchical node stored in the user center is not used, the first account can directly create a custom hierarchical node. The first account can authorize the created custom hierarchical node to other staff members. Afterwards, the first account can determine whether it is necessary to draw a map fence. If it is necessary to draw a map fence, the first account can perform a drawing operation to draw the fence to complete the creation of the custom hierarchical node. If it is not necessary to draw a map fence, the creation of the custom hierarchical node has been completed.

[0134] For example, Figure 6 As shown, it shows a schematic diagram of the interface for hierarchical creation. Suppose the custom hierarchical nodes include: Province A, City X, City Y, City W, City V, and City Z. Province A is the parent node of City X, City Y, City W, City V, and City Z. City X can be the parent node of other hierarchical nodes (i.e., unnamed hierarchical nodes), and the first account can customize the name of the hierarchical node. The first account can also add a new hierarchical node. The first account can also draw a map fence and verify the map fence. After the map fence verification is successful, the first account can also import, export, or reset the map fence. After completing the creation of the hierarchical node, the first account can save the hierarchical node.

[0135] In an embodiment of the present application, for creating a data source, the first account can select a method for obtaining the data source (i.e., an API data source or a static file data source). The first account can map the fields in the data source with the indicator information to be called to obtain the indicator data of the indicator information to be called. The first account can authorize the created data source to other staff members.

[0136] In an embodiment of the present application, for creating a dashboard, the first account can drag and drop the target component to design the dashboard interface. The first account can use the created data source and the created custom hierarchical node to associate the target component with the data source and the hierarchical node to obtain the target dashboard. The first account can preview the target dashboard. The first account can publish the target dashboard and authorize the target dashboard to other staff members.

[0137] For example, Figure 7 As shown, it shows a schematic diagram of the interface for creating a kanban board. The staff can perform operations on the custom kanban board 1. The staff can set the canvas to 100% and select the edit mode to edit the kanban board. The preset components include: basic components (text, pictures, digital text), chart components (tables, bar charts, line charts), interactive components, etc. The first account can use the iframe component to add a custom picture frame to the current layer, introduce third-party pages (such as combat units, combat maps, combat operations, combat results), and can also preview third-party pages on the current layer. The first account can also select the resource information panel to view the content in the resource information panel (such as network resource overview, market precision marketing), and interact with the resource information panel to associate the indicator information in the resource information panel with the data source. The first account can also adjust the text (such as font size, font color, etc.) and adjust the appearance of the component (such as stroke, shadow, etc.).

[0138] In some embodiments, after the first account completes the creation of the goal board, other staff members can view or use the goal board.

[0139] The following is an introduction to the method for the staff to access the target dashboard in the present application in conjunction with a specific embodiment. The server can display a list of dashboards. The second account can select a target dashboard from the list of dashboards. The server can determine whether the second account has permission to access the target dashboard. If the second account has permission to access the target dashboard, the server can display the target dashboard to the second account. If the second account does not have permission to access the target dashboard, the second account can send an authorization request message to the server. The server receives an authorization response message from the first account. The server can display the target dashboard to the second account.

[0140] It should be noted that, in the embodiment of the present application, the authorization response message includes: custom level authorization and data source authorization.

[0141] like Figure 8 As shown, it shows a schematic diagram of a board list. The board list includes the most recently used boards (such as board 1 and board 2) and all boards (such as board 1, board 2, board 3 and board 4). The staff can also search for boards. The board list can also include: boards created by me (i.e. boards created by the account itself) and boards authorized (i.e. boards created by other accounts and allowed to be used by the account).

[0142] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of computer equipment. It is understandable that in order to realize the above functions, the computer equipment includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the management method steps of the kanban board of each example described in the embodiment disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0143] The embodiment of the present application also provides a management device for a kanban board. The management device for the kanban board can be a server, a computer device, a CPU in the computer device, a module in the computer device for managing the kanban board, or a client in the computer device for managing the kanban board.

[0144] The embodiment of the present application can divide the management of the kanban board into functional modules or functional units according to the above method example. For example, each functional module or functional unit can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules or functional units. Among them, the division of modules or units in the embodiment of the present application is schematic, which is only a logical function division. There may be other division methods in actual implementation.

[0145] like Fig. 9 FIG. 1 is a block diagram of a management device for a kanban board provided in an embodiment of the present application. The management device for a kanban board is used to execute Figure 2 , Figure 3 and Figure 4 The management method of the kanban board shown in the figure. The management device of the kanban board may include an acquisition module 901 and a processing module 902.

[0146] The acquisition module 901 is used to acquire the management instruction of the first account, and the management instruction is used to instruct to display the target indicator information through the target component on the target dashboard. The processing module 902 is used to associate the target indicator information with the target component to obtain the associated target component. The processing module 902 is also used to fill the associated target component into the target dashboard.

[0147] Optionally, the processing module 902 is further used to create multiple preset level nodes in response to a level creation instruction, where the level creation instruction is used to instruct the creation of multiple preset level nodes, and one preset level node corresponds to one target dashboard.

[0148] Optionally, a parent-child relationship exists between multiple preset hierarchical nodes; the hierarchical creation instruction includes: a first creation instruction or a second creation instruction, the first creation instruction is used to instruct the addition of multiple newly added hierarchical nodes based on the historical hierarchical nodes, and the second creation instruction is used to instruct the creation of multiple preset hierarchical nodes. Processing module 902 is specifically used to obtain historical hierarchical nodes if the hierarchical creation instruction is the first creation instruction, use the parent nodes of the multiple newly added hierarchical nodes as the child nodes of the terminal nodes in the historical hierarchical nodes, and create multiple preset hierarchical nodes according to the parent-child relationship. Processing module 902 is specifically used to use the parent nodes of the multiple hierarchical nodes as the root nodes if the hierarchical creation instruction is the second creation instruction, and create multiple preset hierarchical nodes according to the parent-child relationship.

[0149] Optionally, the target component is a map. The processing module 902 is further used to draw a fence corresponding to the preset level node in the map in response to a fence drawing instruction for each preset level node, wherein the fence drawing instruction is used to instruct to draw the fence corresponding to the preset level node. The processing module 902 is also used to verify the fence corresponding to each preset level node.

[0150] Optionally, the acquisition module 901 is further used to obtain a kanban request message of the second account and hierarchical authority information of the second account, the kanban request message is used to request to view the target kanban, and the hierarchical authority information is used to indicate all hierarchical nodes that the second account can view, and the first account is different from the second account. The processing module 902 is further used to display the target kanban if there is a hierarchical node corresponding to the target kanban in the hierarchical authority information.

[0151] Optionally, the acquisition module 901 is further used to receive an authorization request message from the second account if there is no hierarchical node corresponding to the target dashboard in the hierarchical permission information, and the authorization request message is used to request to view the target dashboard. The acquisition module 901 is also used to receive an authorization response message, and the authorization response message is used to indicate that the second account is allowed to view the target dashboard. The processing module 902 is also used to display the target dashboard.

[0152] Fig.10 The diagram is a schematic diagram of a management device for a kanban board according to an exemplary embodiment. The management device for a kanban board may include a processor 1001, and the processor 1001 is used to execute application code to implement the management method for a kanban board in the present application.

[0153] The processor 1001 may be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0154] like Fig.10 As shown, the management device of the dashboard may further include a memory 1002. The memory 1002 is used to store application program codes for executing the solution of the present application, and the execution is controlled by the processor 1001.

[0155] The memory 1002 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1002 may exist independently and be connected to the processor 1001 via the bus 1004. The memory 1002 may also be integrated with the processor 1001.

[0156] like Fig.10 As shown, the management device of the kanban board may further include a communication interface 1003, wherein the processor 1001, the memory 1002, and the communication interface 1003 may be coupled to each other, for example, via a bus 1004. The communication interface 1003 is used to exchange information with other devices, for example, to support information exchange between the management device of the kanban board and other devices.

[0157] It should be pointed out that Fig.10 The device structure shown in the figure does not constitute a limitation on the management device of the billboard, except Fig.10 In addition to the components shown, the management device of the kanban board may include more or fewer components than shown, or combine certain components, or have a different arrangement of components.

[0158] In actual implementation, the functions implemented by the processing module 902 can be Fig.10 The processor 1001 shown calls the program code in the memory 1002 to implement.

[0159] The present application also provides a computer-readable storage medium, on which instructions are stored. When the instructions in the computer-readable storage medium are executed by a processor of a computer device, the computer can execute the management method of the kanban board provided in the above-mentioned embodiment. For example, the computer-readable storage medium may be a memory 1002 including instructions, and the above instructions may be executed by a processor 1001 of a computer device to complete the above method. Optionally, the computer-readable storage medium may be a non-temporary computer-readable storage medium, for example, a non-temporary computer-readable storage medium may be a ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

[0160] Fig.11 A conceptual partial view of a computer program product provided by an embodiment of the present application is schematically shown, where the computer program product includes a computer program for executing a computer process on a computing device.

[0161] In one embodiment, the computer program product is provided using a signal bearing medium 1100. The signal bearing medium 1100 may include one or more program instructions that, when executed by one or more processors, may provide the above-described Figure 2 , Figure 3 and Figure 4 Thus, for example, reference to Figure 2 In the embodiment shown in , one or more features of S201 to S203 may be undertaken by one or more instructions associated with the signal bearing medium 1100. In addition, Fig.11 The program instructions in also describe example instructions.

[0162] In some examples, the signal bearing medium 1100 may include a computer readable medium 1101, such as, but not limited to, a hard drive, a compact disk (CD), a digital video disk (DVD), a digital tape, a memory, a read-only memory (ROM), or a random access memory (RAM), and the like.

[0163] In some implementations, the signal bearing medium 1100 may include a computer recordable medium 1102 such as, but not limited to, a memory, a read / write (R / W) CD, a R / W DVD, or the like.

[0164] In some implementations, signal bearing medium 1100 may include communication medium 1103 such as, but not limited to, digital and / or analog communication media (eg, fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0165] The signal bearing medium 1100 may be communicated by a wireless form of communication medium 1103. The one or more program instructions may be, for example, computer executable instructions or logic implemented instructions.

[0166] In some examples, such as for Fig. 9 The described kanban management apparatus may be configured to provide various operations, functions, or actions in response to one or more program instructions in computer-readable medium 1101 , computer-recordable medium 1102 , and / or communication medium 1103 .

[0167] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0168] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0169] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0170] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0171] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the full classification part or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including a number of instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute the full classification part or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes various media that can store program codes, such as-U disk, mobile hard disk, ROM, RAM, disk or CD.

[0172] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A management method of Kanban, It is characterized in that The method comprises: Obtaining a management instruction of the first account, wherein the management instruction is used to instruct to display target indicator information on the target dashboard through a target component; Associating the target indicator information with the target component to obtain the associated target component; The associated target component is filled into the target dashboard.

2. The method according to claim 1, It is characterized in that Before obtaining the management instruction of the first account, the method further includes: In response to the hierarchy creation instruction, a plurality of preset hierarchy nodes are created, wherein the hierarchy creation instruction is used to instruct the creation of the plurality of preset hierarchy nodes, and one preset hierarchy node corresponds to one target dashboard.

3. The method according to claim 2, It is characterized in that There is a parent-child relationship between the plurality of preset level nodes; the level creation instruction includes: a first creation instruction or a second creation instruction, the first creation instruction is used to instruct to add a plurality of new level nodes based on the historical level nodes, and the second creation instruction is used to instruct to create the plurality of preset level nodes; in response to the level creation instruction, creating a plurality of preset level nodes includes: If the level creation instruction is the first creation instruction, the historical level nodes are acquired, the parent nodes of the multiple newly added level nodes are used as child nodes of the terminal nodes in the historical level nodes, and the multiple preset level nodes are created according to the parent-child relationship; If the hierarchical creation instruction is the second creation instruction, the parent node among the multiple hierarchical nodes is used as the root node, and the multiple preset hierarchical nodes are created according to the parent-child relationship.

4. The method according to claim 2 or 3, It is characterized in that The target component is a map; After creating a plurality of preset level nodes in response to the level creation instruction, the method further includes: For each of the preset level nodes, in response to a fence drawing instruction, a map fence corresponding to the preset level node is drawn in the map to obtain a plurality of map fences, wherein the fence drawing instruction is used to instruct drawing the map fence corresponding to the preset level node; The plurality of map fences are verified.

5. The method according to any one of claims 1 to 3, It is characterized in that The method further comprises: Obtaining a dashboard request message of a second account and hierarchical authority information of the second account, wherein the dashboard request message is used to request viewing of a target dashboard, and the hierarchical authority information is used to indicate all hierarchical nodes that the second account can view, and the first account is different from the second account; If a hierarchical node corresponding to the target dashboard exists in the hierarchical authority information, the target dashboard is displayed.

6. The method according to claim 5, It is characterized in that The method further comprises: If the hierarchical node corresponding to the target dashboard does not exist in the hierarchical authority information, receiving an authorization request message from the second account, wherein the authorization request message is used to request viewing of the target dashboard; receiving an authorization response message from the first account, wherein the authorization response message is used to indicate that the second account is allowed to view the target dashboard; The target dashboard is displayed.

7. A management device for a kanban board, It is characterized in that The device comprises: An acquisition module, used to acquire a management instruction of the first account, wherein the management instruction is used to instruct to display target indicator information on the target dashboard through a target component; A processing module, used for associating the target indicator information with the target component to obtain the associated target component; The processing module is further used to fill the associated target component into the target dashboard.

8. The device according to claim 7, It is characterized in that The processing module is further used to create a plurality of preset level nodes in response to a level creation instruction, wherein the level creation instruction is used to instruct the creation of the plurality of preset level nodes, and one preset level node corresponds to one target dashboard.

9. The device according to claim 8, It is characterized in that There is a parent-child relationship between the plurality of preset level nodes; the level creation instruction includes: a first creation instruction or a second creation instruction, the first creation instruction is used to instruct to add a plurality of new level nodes based on the historical level nodes, and the second creation instruction is used to instruct to create the plurality of preset level nodes; The processing module is specifically configured to, if the hierarchical creation instruction is the first creation instruction, obtain the historical hierarchical node, use the parent node of the multiple newly added hierarchical nodes as the child node of the terminal node in the historical hierarchical node, and create the multiple preset hierarchical nodes according to the parent-child relationship; The processing module is specifically used to, if the hierarchical creation instruction is the second creation instruction, use the parent node among the multiple hierarchical nodes as the root node, and create the multiple preset hierarchical nodes according to the parent-child relationship.

10. The device according to claim 8 or 9, It is characterized in that The target component is a map; The processing module is further configured to draw, for each of the preset level nodes, a fence corresponding to the preset level node in the map in response to a fence drawing instruction, wherein the fence drawing instruction is used to instruct drawing the fence corresponding to the preset level node; The processing module is further used to verify the fence corresponding to each of the preset level nodes.

11. The device according to any one of claims 7 to 9, It is characterized in that The acquisition module is further used to acquire a dashboard request message of a second account and hierarchical authority information of the second account, wherein the dashboard request message is used to request viewing of a target dashboard, and the hierarchical authority information is used to indicate all hierarchical nodes that the second account can view, and the first account is different from the second account; The processing module is further configured to display the target dashboard if a hierarchical node corresponding to the target dashboard exists in the hierarchical authority information.

12. The device according to claim 11, It is characterized in that The acquisition module is further configured to receive an authorization request message from the second account if the hierarchical node corresponding to the target dashboard does not exist in the hierarchical authority information, wherein the authorization request message is used to request viewing of the target dashboard; The acquisition module is further used to receive an authorization response message, where the authorization response message is used to indicate that the second account is allowed to view the target dashboard; The processing module is also used to display the target signboard.

13. A management device for a kanban board, It is characterized in that include: Processor and memory; The processor is coupled to the memory; The memory is used to store one or more programs, which include computer-executable instructions. When the kanban management device is running, the processor executes the computer-executable instructions stored in the memory to enable the kanban management device to perform the kanban management method as described in any one of claims 1-6.

14. A computer-readable storage medium having stored therein instructions, It is characterized in that When a computer executes the instruction, the computer executes the kanban management method according to any one of claims 1 to 6.

Images