WO2023222043A1

WO2023222043A1 - View management method and apparatus, electronic device, and storage medium

Info

Publication number: WO2023222043A1
Application number: PCT/CN2023/094819
Authority: WO
Inventors: 林诗鸿; 刘大畅; 唐伟豪
Original assignee: 北京字跳网络技术有限公司
Priority date: 2022-05-17
Filing date: 2023-05-17
Publication date: 2023-11-23
Also published as: CN115525370A

Abstract

The present disclosure provides a view management method and apparatus, an electronic device, and a storage medium. The view management method comprises: upon detecting that a view processing control is triggered, displaying a view management list, wherein the view management list comprises view association information of at least one created view that has been currently managed; using the created view corresponding to the view association information triggered in the view management list as a view to be managed, and performing, on the basis of operation permission information corresponding to the view to be managed, management operation on said view; and updating, on the basis of the corresponding view when the management operation is completed, the view to be managed.

Description

View management method, device, electronic device and storage medium

This application claims priority to the Chinese patent application with application number 202210541735.X, which was submitted to the China Patent Office on May 17, 2022. The entire content of this application is incorporated into this application by reference.

Technical field

The present disclosure relates to image processing technology, for example, to a view management method, device, electronic device and storage medium.

Background technique

Displaying project requirement information through views has become a very common data management method at present. In related technologies, the views generated for displaying project requirement information are all managed individually. Each time you need to view a view, you need to manually input the view information you want to view in order to complete the display and management operations of the view. However, manual input is inefficient, time-consuming and labor-intensive; individual management is inconvenient.

Contents of the invention

The present disclosure provides a view management method, device, electronic device, and storage medium to manage views efficiently and conveniently.

The embodiment of the present disclosure provides a view management method, including:

When a triggered view processing control is detected, display a view management list, wherein the view management list includes view association information of at least one created view that is currently managed;

Use the created view corresponding to the view association information triggered in the view management list as a view to be managed, and perform management operations on the view to be managed based on the operation permission information corresponding to the view to be managed;

The view to be managed is updated based on the view corresponding to when the management operation is completed.

An embodiment of the present disclosure also provides a view management device, which includes:

A view management list display module configured to display a view management list when a triggered view processing control is detected, wherein the view management list includes view association information of at least one created view that is currently managed;

The view operation module to be managed is configured to use the created view corresponding to the view association information triggered in the view management list as the view to be managed, and to operate the view based on the operation permission information corresponding to the view to be managed. Describe the management view to perform management operations;

The view update module to be managed is configured to update the view to be managed based on the view corresponding to when the management operation is completed.

An embodiment of the present disclosure also provides an electronic device, including:

one or more processors;

a storage device configured to store one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the view management method as described in any one of the embodiments of the present disclosure.

Embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the view management method as described in any one of the embodiments of the present disclosure is implemented.

Description of the drawings

Figure 1 is a schematic flowchart of a view management method provided by an embodiment of the present disclosure;

Figure 2 is a schematic diagram of a display interface provided by an embodiment of the present disclosure;

Figure 3 is a schematic diagram of a sharing operation provided by an embodiment of the present disclosure;

Figure 4 is a schematic diagram of a batch operation provided by an embodiment of the present disclosure;

Figure 5 is a schematic flowchart of another view management method provided by an embodiment of the present disclosure;

Figure 6 is a schematic diagram of a sorting operation provided by an embodiment of the present disclosure;

Figure 7 is a schematic structural diagram of a view management device provided by an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure.

Detailed ways

Embodiments of the present disclosure will be described below with reference to the accompanying drawings. Although some embodiments of the disclosure are shown in the drawings, the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather these embodiments are provided for the purpose of understanding the disclosure. The drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of the present disclosure.

Multiple steps described in the method implementations of the present disclosure may be executed in different orders and/or in parallel. Furthermore, method embodiments may include additional steps and/or omit performance of illustrated steps. The scope of the present disclosure is not limited in this regard.

As used herein, the term "include" and its variations are open-ended, ie, "including but not limited to." The term "based on" means "based at least in part on." The term "one embodiment" means "at least one embodiment"; the term "another The term "embodiments" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the description below.

Concepts such as "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units. relation.

The modifications "a" and "plurality" mentioned in this disclosure are illustrative and not restrictive, and should be understood as "one or more" unless the context indicates otherwise.

The names of messages or information exchanged between multiple devices in the embodiments of the present disclosure are for illustrative purposes only and are not used to limit the scope of these messages or information.

Before introducing this technical solution, an exemplary description of the application scenario can be provided. Based on this technical solution, application software or display pages can be developed, such as HyperText Markup Language 5.0 (H5) pages, so that the application software or display page can realize the function of unified management of views. This technical solution can also be integrated into a project management platform or system and used to manage project views generated by project data in the project platform or system. For example, if a platform user wants to view and edit the demand data and planning information of related projects, he can quickly and efficiently operate the view based on the solution of this embodiment to facilitate user management.

Figure 1 is a schematic flowchart of a view management method provided by an embodiment of the present disclosure. The embodiment of the present disclosure is suitable for unified management of built views. This method can be executed by a view management device, and the device can It is implemented in the form of software and/or hardware, optionally, through electronic equipment. The electronic equipment can be a mobile terminal, a personal computer (Personal Computer, PC) or a server.

As shown in Figure 1, the view management method includes the following steps.

S110. When the triggering view processing control is detected, display the view management list.

The view management list includes view association information of at least one created view that is currently managed. The created view may include at least one of project requirement information, project attribute information and project plan information. The view association information includes the created view. Information such as view name, view ID, view description, etc.

In this embodiment, the view processing control is a control that starts the function of displaying the view management list when triggered. For example, the view processing control can be a button containing the words "view processing control", and the shape of the button can be rectangular, circular, Star shape, etc.; the view processing control can also be an icon containing animation information of the view processing action, and the icon of the view processing control can be vividly and vividly displayed on the display interface of the project management platform or system to start the function based on the trigger operation.

In embodiments, various methods may be used for triggering operations of the view processing control. For example, the triggering operation of the view processing control can be implemented through at least one of voice control, external device control, touch screen control, and gesture control. For example, the external device may include a mouse. When the view processing control is displayed in the form of a rectangular button, and a mouse click operation on the rectangular control is detected, it can be determined that the view processing control is triggered; or when a voice command is recognized , it can be determined that the view processing control is triggered; or, if it is detected that the touch screen is clicked, and the click position is at the button position displayed by the view processing control, it is determined that the view processing control is triggered.

In this embodiment, the view processing control includes at least one type of processing control, such as "all demand view processing control", "unfinished demand view processing control" or "completed demand view processing control", etc., which can be based on the detected The type of the triggered view processing control displays the view management list of the corresponding type; for example, when the "Unfinished Requirements View Processing Control" is triggered, the corresponding display only contains a list of unfinished requirements views, and the list only contains each A constructed view of an item's unfulfilled requirements.

In an embodiment, the view management list may be displayed in a default position of the current display interface or displayed in a preset designated position. For example, the default position may include the left, right, top, or left sides of the current display interface. The bottom and other positions to avoid blocking other display information in the display interface; in addition, project management users can input the location information of the specified location in advance through an external output device to display the view management list according to the specified location. For example, the location information can be the display location. coordinate data, or the user can perform a selection operation on the current display interface through a mouse or other device, and use the detected selected area information as location information. For example, the display form of the view management list may include scrolling cycle display, folded and hidden display, all expanded display, etc. The display form of the view management list may be determined according to actual application requirements.

In this embodiment, in order to display the view management list intuitively and clearly, the display method of displaying the view management list includes: popping up a window including the view management list; expanding and displaying the folded view management list in the display interface.

The display interface can display a window containing the folded view management list. When it is detected that the view processing control is triggered, the window can be popped up directly; in order to display the information in the view management list in a complete and detailed manner, the folded display can be The view management list is expanded and displayed. For example, a folding control is also deployed in the window, which is used to fold or expand the view management list when triggered. Collapse controls can be represented by shapes such as triangles, arrows, circles, or rectangular boxes. It can be triggered by a click operation, and based on the trigger operation, the view management list is updated to the opposite display state to the current one; if it is currently displayed in the expanded state, after the folding control is triggered, the information in the view management list will be collapsed and displayed.

Take Figure 2 as an example to illustrate. In Figure 2, the view management list is displayed on the left navigation bar of the display interface, and the view management list is displayed through the folding control. Control the switching between the collapsed and expanded states of each view in the view management list. For example, when the view management list is displayed for the first time, it can be displayed in an expanded state. To fully display each view included in the view management list; before displaying, it can be determined whether the number of views included in the view management list is greater than the preset number of views, if the number of views included in the view management list is greater than the preset view number Quantity means that there are too many views in the view management list and they cannot all be displayed at the same time. You can set a scroll bar on the left navigation bar and drag the scroll bar to display each view in the view management list. If the number of views included in the view management list is less than or equal to the preset number of views, each view can be directly expanded to display. The number of preset views can be determined based on the display font size, display spacing and other display parameters set on the display interface.

As shown in Figure 2, the display interface can also include a search control. If you need to search for requirements, defects, and work item instances in the current view, you can click the search button to enter relevant keywords, highlight the found keywords, and Show examples of requirements, defects, or work items that contain this keyword.

In this embodiment, the view association information includes at least one indicator item, and the at least one indicator item includes at least one of view name information, creator identification, creation time, browsing permissions, and collaborators; the created views include system views, At least one of fixed views and conditional views.

The creator ID can be the codename of the user who created the view, the collaborators include the participants involved in the created view, and the browsing permission is the permission to view the content in the corresponding created view; for example, the browsing permission includes all browsing permissions and Partial browsing permissions. For example, when the user has full browsing permissions, all content in the corresponding view can be browsed. When the user only has partial browsing permissions, only part of the browsable content in the corresponding view is displayed, that is, only the user himself is involved. part of the content, thereby improving the confidentiality and security of the view content.

In this embodiment, the created views can be divided into at least one of a system view, a fixed view, and a conditional view according to different configuration methods. Among them, the system view is a template view created by the administrator; it can open operation rights or browsing rights to the administrator. After the view processing control for displaying the system view is triggered, the view association information of each template view included in the system view can be displayed on the display interface; the view association information of each template view can be arranged in the left navigation bar of the display interface , the view association information of each displayed template view can be adjusted in order, the view association information can be changed, etc. based on the administrator's operations.

Created views can also include fixed views. Fixed views are views created after selecting at least one configuration item from the fixed requirement list; configuration items include links to other views, data links, and requirements in project associated data. At least one of the items; through the link of the view, the fixed view can be directly associated with other views to facilitate quick switching to other views; the data corresponding to the data link can be obtained in the fixed view through the data link. For example, in requirements review or version iteration requirements scenarios, a fixed view can be used to display each configuration item.

In an embodiment, the content displayed in the fixed view can be updated based on the configuration item selected in the fixed requirement list. For example, when it is detected that the configuration item selected in the requirement list is different from the configuration item displayed in the current fixed view. When the configuration items are different, the differential configuration items are added or deleted in the current fixed view accordingly, and the current fixed view is updated based on the addition or deletion results.

Created views can also include conditional views. Conditional views are views generated after determining the view's participation in data based on preset filtering conditions. In the embodiment, the filtering conditions can be input in advance, for example, the input box can be directly displayed in the display interface to facilitate the user to input the filtering conditions; the set filtering conditions can also be imported into the project management platform by importing the text of the filtering conditions. or in the system; or, when it is detected that the filter condition input control is triggered, the editing interface can pop up to facilitate the user to input filter conditions; or when the control associated with the filter condition input operation is triggered, the filter condition editing page can pop up. to edit the filter criteria. Based on the preset filtering conditions, the filtered data that meets the filtering conditions can be determined in the project management database as view participation data, and the view participation data is used as the component content to form a conditional view.

For example, the filtering relationships of the filtering conditions include belonging to, containing, equal to, empty, and in an interval. Among them, the type of belonging is in the single-selection scenario, such as A belongs to A and B, but C does not belong to A and B; in the multiple-selection scenario, such as A and D belong to A, B, C, D, but D and E do not belong to A, B, C. Inclusion types are used in multiple scenarios. For example, A, B, and C include A and B, but A and C do not include A and B.

As shown in Figure 2, the display box of the view type can be set in the top navigation bar of the display interface. The display box can be an input display box, that is, using direct input, the system view, fixed view and conditional view can be entered in the display box. Any view type in; or, a hidden selection control is set in the adjacent area of the display box. When the hidden selection control is triggered, the options corresponding to the system view, fixed view and conditional view are displayed accordingly, and the selection is determined based on the selection operation. The currently selected view type is displayed in the display box, and the view management list and corresponding view association information corresponding to the type are displayed.

For example, a default view can also be preset to display when the system view, fixed view, and conditional view are not set. For example, when the view management method proposed in this embodiment is applied to a project management system, the default view may include at least one item from the pool of all requirements, ongoing requirements, completed requirements, and terminated requirements pools. Among them, click on all requirements to display all requirements of the current control, excluding terminated requirements; click on ongoing requirements to display ongoing requirements; completed requirements to display requirements whose status is ended; terminate the demand pool , when the demand is terminated, it will enter the terminated demand pool by default. In addition, the default view can also display defect views, such as all defects, pending defects, user-reported defects and user-handled defects.

S120. Use the created view corresponding to the view association information triggered in the view management list as a view to be managed, and perform management operations on the view to be managed based on the operation permission information corresponding to the view to be managed.

Operation permission information includes sorting, sharing, favorites, deletion, modification, and At least one operation permission in the export. Different users have different operation permissions for different views to be managed.

In the embodiment, when it is detected that each corresponding view association control in the view management list is triggered, it means that the view association information corresponding to the view association control currently needs to be managed, and the view association information corresponding to the triggered view association information can be The created view is determined to be a view to be managed. For example, the view associated control can be a text box button that displays the associated information of each view. When it is detected that the text box button is clicked, it is determined that the view associated control corresponding to the text box button is triggered; it can also be through voice instructions. Trigger the view association control. When the voice command of "start A view association information" is detected, it can be determined that the corresponding A view association information is triggered.

In this embodiment, before performing the management operation on the view to be managed, the operation permission information corresponding to the view to be managed can be determined. The implementation method can be: determining the user login information currently logged in to the system, and obtaining the user corresponding to the user login information. Operation permission information, and based on the correspondence between the pre-stored user operation permission information and each view, determine the operation permission information corresponding to the view to be managed, so as to perform management operations on the view to be managed according to the operation permission information. The user login information includes at least one of the authorized login address, login user code, or user ID of the logged in user.

For example, when obtaining the user operation permission information corresponding to the user's login information, the user's corresponding operation permission information can be determined through the pre-stored user permission range; it can also be determined by determining the user type and/or corresponding to the user's login information. The user operation level determines the user's corresponding operation permission information; for example, when the user login information reflects that the currently logged-in user is an administrator, the administrator can be given the maximum operation permission and can perform any operation on any view. ; When the user login information reflects that the currently logged-in user is a project participant, the project participant can be given the operating permission to only browse the participating projects to improve the security of the information; it can also be used for various logged-in users The operation level is preset. Different operation levels have different operation permissions. The higher the operation level, the greater the user operation permission. According to the user operation level corresponding to the user login information, the user operation permission information corresponding to the user login information is determined.

In the embodiment, when performing a management operation on the view to be managed, it is necessary to detect whether the current management operation being triggered is within the determined range of the operation authority information; if the current management operation being triggered is within the range of the determined operation authority information, Then you can operate the pending management view according to the current management operation that is triggered; if the current management operation that is triggered is not within the determined operation permission information range, the prompt message "No operation permission, you can activate the permission before operating" will be prompted. , to prompt the user to activate the corresponding permission; if it is detected that the same operation without operation permission is triggered by the same user a preset number of times, an alarm message is generated and sent to the management terminal to prompt that the current operation is risky.

In this embodiment, the management operation for the view to be managed includes at least one of a sharing view operation, a favorite view operation, and a batch operation. Optional, when the management operation is a share view operation, based on The operation permission information corresponding to the view to be managed. The management operation of the view to be managed is implemented in the following way: when a sharing operation of the view to be managed is detected, and the operation permission information includes the sharing permission, the view link of the view to be managed is shared. To at least one user to be shared, to obtain the view to be managed based on the view link.

The user to be shared is a user with permission to view the view to be managed, and the view link can be the storage path of the view to be managed in the current project management system.

In the embodiment, the display interface includes a sharing control. When it is detected that the sharing control is triggered, the manageable operation is a sharing operation. To ensure the safety of the operation, it is necessary to verify whether the operation permission information corresponding to the view to be managed contains the sharing permission. If yes, it means that the view to be managed can be shared. After the sharing control is triggered, the view link of the view to be managed is provided, and the user is prompted to enter the information of the user to be shared, such as the code name, login name and other information of the user to be shared. To obtain the information of the user to be shared, and share the view link to the user to be shared based on the information of the user to be shared.

For example, the user to be shared can be one or more users specified by the currently logged in user, or all users belonging to a project group. When it is necessary to share to all users in the project group, enter the project group number and project group name. Just wait for the information; when you need to share it with one or more designated users, just directly enter the code name, login name and other information of the user to be shared.

The sharing operation is usually suitable for project review, and the review preview is shared by sharing the project view link. In order to more clearly demonstrate the implementation of the sharing view, see Figure 3. In the figure, a sharing control is set in the top navigation bar of the display interface. When a click operation is detected at the location of the sharing control on the display interface, the sharing control can be confirmed. When triggered, the sharing information input window can pop up, as shown in Figure 3. The sharing information input window displays the address of the sharing link, the copy control, and the information input control of the user to be shared. By triggering the copy control, the information to be managed can be obtained. For the storage address link of the view, enter the identification of the user to be shared at the input position corresponding to the user to be shared, so as to send "Link A" to the user to be shared corresponding to the entered identification.

Optionally, when the management operation is a collection view operation, based on the operation permission information corresponding to the view to be managed, the management operation of the view to be managed is implemented in the following manner: if the operation permission information includes the collection permission, then the view to be managed is collected. Or cancel favorite views to be managed.

Collection permissions include collection view permissions and unfavorite view permissions. For example, if the operation permission information includes the collection permission of the view to be managed, then when the management operation is the collection of the view to be managed, the view to be managed can be added to the favorites list, and the view to be managed can be added to the favorites list in the view management list. The view is marked as a favorite. The favorite mark can be at least one of highlighting, bolding, underlining, and special symbol marking on the information of the collected view to be managed; when the management operation is to cancel the collection of the view to be managed. to remove the view to be managed from the favorites list and cancel the favorite mark of the view to be managed in the view management list. For example, when the management operation is to collect or cancel the collection to be managed When the view is displayed and the operation permission information does not include the collection permission, a prompt message can be generated to remind the user through voice broadcast, text display, etc. that the user currently does not have the collection permission and cannot perform the operation.

For example, to illustrate the collection operation method, as shown in Figure 3, a collection control is set in the top navigation bar of the display interface. The view currently displayed in the view display area can be collected by clicking on the collection control. Operate or cancel collection operations.

When the view to be managed is an uncollected view and needs to be collected, you can click the collection control in the display interface; for example, the view displayed in the view display area is the content of view B, and view B is required. To perform a collection operation on the view to be managed, just click the collection control. The collection control after being clicked will be displayed differently from the collection control before clicking. For example, the collection control before clicking will be displayed without a shadow. After clicking, a shadow will be added to the collection control. ;The favorite control before clicking is surrounded by a dotted frame, and the favorite control after clicking is surrounded by a solid frame, etc. When the view to be managed "View B" is collected, the associated information of View B can be marked in the view management list containing "View B". For example, the mark "○" can be filled with color and changed to "●" to show that the view has been favorited.

When the view to be managed is a favorited view and the management operation is to cancel the favorite operation, the view can be canceled in the following ways: 1. You can click the favorite control again to make the favorite control in the unfavorite state. , then cancel the collection of the view in the view display area; 2. In the view management list where the view to be managed is located, click the logo control in front of the view to be managed to cancel the collection operation and leave the logo control in an uncollected state. ;As shown in Figure 3, the logo control in front of "View A" is "○", that is, it is in the uncollected state, while the logo control "●" in front of "View B" is in the collected state; 3. It can be In the list of favorite views, click the icon control in front of the favorite view to be managed to cancel the favorite.

Optionally, when the management operation is a batch operation, based on the operation permission information corresponding to the view to be managed, the management operation of the view to be managed is implemented in the following manner: if the operation permission information includes a batch operation of views, then at least one to-be-managed view is operated in batches. Management view for batch management operations.

View batch operations include at least one of batch upgrade, batch deletion, batch modification, batch export, and drag and drop. The view to be managed includes at least one data item, and the batch operation can be an operation on at least one view to be managed, or an operation on at least one data item in the view to be managed; batch upgrade can be used to upgrade the selected at least one view to be managed Upgrade to a preset view template; batch deletion can be used to delete at least one selected view to be managed from the view management list or data items contained in the view to be managed; batch modification can be used to delete at least one selected view to be managed Modify at least one of the view's associated information, view parameters, view content and included data items; batch export can be used to export at least one selected view to be managed or data items in the view to be managed to a preset address; drag and drop It is used to change the sorting of at least one selected view to be managed in the view management list, and can also be used to change the sorting order of any requirement in the view to be managed.

In this embodiment, the display interface is provided with an upgrade control, a deletion control, a modification control and an export control respectively. When the corresponding control is triggered, the selected at least one view to be managed is upgraded, deleted, modified or exported. For batch upgrade operations, in order to prevent upgrade misoperations, when it is detected that the upgrade control is triggered, a pop-up window prompt can be displayed to remind the user again of the operation content. Until the confirmation operation sent by the user through the input device is obtained, the selected The view to be managed performs corresponding operations.

For batch deletion operations, the deletion operation can be performed when the view is invalid, the view is created incorrectly, or the requirements in the view to be managed are created incorrectly. The operation path can be to select at least one view to be managed or at least one data item in the view to be managed, and click Delete control to delete the selected view or data item to be managed.

For batch modification operations, it is mainly used in scenarios where the same type of fields are modified or replaced in batches. For example, if the priority of at least one data item in the view to be managed is increased in batches, the data items that need to be increased in priority can be modified in batches. Select to batch modify the priority values corresponding to the selected data items that need to be increased in priority.

For batch export operations, it is mainly used in scenarios where the views to be managed or at least one data item in the views to be managed are exported to local storage. In the embodiment, at least one selected view to be managed can be exported according to the preset storage address. Or the data items are exported to the corresponding storage location. Exported views or data items can be stored in table form, image form, or text form.

For drag and drop operations, it is mainly used in scenarios where the order of the view to be managed or at least one data item in the view to be managed is changed. The implementation method may be to select the view or data item to be managed, move it from the initial position to the target position, and based on The moved sort updates the view management category or the sorting of each data item in the view to be managed. For drag and drop operations, you can drag only one view or data item at a time; when multiple views or data items need to be dragged, in order to improve convenience, you can determine the target position of each view or data item that needs to be dragged. Is it consistent? If the target position of each view or data item that needs to be dragged is the same, you can select each view or data item that needs to be dragged, and drag the selected content to the target position at the same time; if the target position of each view or data item that needs to be dragged is the same, If the target positions of views or data items are different, select the views or data items with the same target position together in batches and drag them to the target position.

For example, as shown in Figure 4, the top navigation bar of the display interface is provided with upgrade controls, delete controls, export controls and modify controls; each view in the view management list corresponds to a check box, which can be clicked on Operation to realize the selection operation of the view. Each selection box can be selected entirely, or a few of them can be selected; the selection box corresponding to the selected view is marked with an "×" mark to distinguish it from the unselected views. When the number of selected views exceeds the preset number, the display status of each view can be marked, for example, by highlighting each selected view. For example, the selected view can be used as a view to be managed, and corresponding operations on the view to be managed can be implemented by clicking any one of upgrade controls, deleting controls, exporting controls, or modifying controls. By way of example, when the view When each view in the management list needs to be selected, you can click the Select All control below the view management list to set all views as views to be managed.

S130. Update the view to be managed based on the view corresponding to when the management operation is completed.

In this embodiment, the management operation may include at least one operation of browsing, sharing, sorting, modifying, deleting, and exporting. For the browsing operation, the display content and display mode of the view to be managed will not change after the operation, while sharing, Operations such as sorting, modifying, deleting, and exporting will change the display content and/or presentation method of the views to be managed. Therefore, when the management operation is completed, it can be detected whether the display content and/or presentation method of the view to be managed before the operation and the view to be managed after the operation are consistent. If they are consistent, the state of the view to be managed before the operation can be maintained; If they are inconsistent, the view to be managed after the management operation is saved as a new view to replace the view to be managed before the operation to complete the update operation of the view to be managed.

Before updating the view to be managed, it can also be determined whether it is detected whether the "Save Current View" control is triggered. If so, the view to be managed is updated based on the current corresponding view to avoid view errors caused by the user's misoperation of the view to be managed. ; If not, query information can be displayed on the interface according to the preset time interval. The query information can pop up to the display interface in the form of a dialog box to display the text "Do you need to update this view?" When "Confirm update" is detected When the control is triggered, the view to be processed can be updated. If it is detected that the "do not update yet" control is triggered, there is no need to update the view to be managed.

For example, a preset number of views to be managed before the update can be stored. When the user makes an operation error or wants to view historical views, the views to be managed before the update are re-displayed to improve user convenience. Alternatively, each view to be managed before update within a preset time period can be stored, so that the user can manage and view each historical view to be managed within the preset time period.

The technical solution of the embodiment of the present disclosure is to display a view management list when a triggered view processing control is detected, and the view management list includes view association information of at least one created view that is currently managed, thereby realizing the unification of created views. Management; and use the created view corresponding to the view association information triggered in the view management list as the view to be managed, and perform management operations on the view to be managed through the operation permission information corresponding to the view to be managed, which improves the view to be managed The security of the operation is performed, and the view to be managed is updated based on the corresponding view when the management operation is completed. The embodiments of the present disclosure solve the labor-intensive and time-consuming problem in related technologies, and can manage views efficiently and conveniently.

Figure 5 is a schematic flow chart of a view management method provided by an embodiment of the present disclosure; based on the foregoing embodiment, when the triggering of the view creation control is detected, the target view is drawn; when the triggering of the sorting in the view to be managed is detected Control, handles sorting of data in the management view. For its implementation, please refer to the technical solution of this embodiment. Wherein, the same or corresponding technical terms as those in the above embodiments are used here No longer.

As shown in Figure 5, the method includes the following steps.

S210. When the triggering view processing control is detected, display the view management list. The view management list includes view association information of at least one created view that is currently managed.

S220. Use the created view corresponding to the view association information triggered in the view management list as a view to be managed, and perform management operations on the view to be managed based on the operation permission information corresponding to the view to be managed.

S230. Update the view to be managed based on the view corresponding to when the management operation is completed.

S240. When the triggering view creation control is detected, obtain the view name information in the view name editing control.

The view creation control is used to create a new view, and the view name editing control is used to input the name information of the view to be created. The view name information includes the identification and/or naming of the view to be created, such as "demand view for this week", "completed this week" Views" and "Unfinished views this week", etc.

Users can customize the demand list or display conditions based on actual usage preferences to create views based on actual needs. In an embodiment, after the view creation control is triggered, a view name editing page including a view name editing control may pop up. The view name editing control may include at least one of input boxes, selection buttons, scroll bars, and drop-down menus. The view name editing control may be triggered to obtain information by selecting preset name information and actively inputting information. View name information can be obtained by obtaining the content entered in the view name edit control.

S250. Obtain at least one filtering condition and/or at least one configuration item selected from the requirement list, and determine the view drawing participation data.

The requirement list includes at least one configuration item, and the configuration item includes at least one of links to other views, data links, and project-related data; the filter condition is used to filter out configuration items in the requirement list to use the filtered configuration items as views Plot participation data.

In this implementation, when determining the view drawing participation data through filtering conditions, the filtering conditions can include at least one of time filtering information, progress filtering information, and participating user filtering information. For example, the filtering conditions can be set to "the first time period "Project data completed within", the data that meets the filter conditions can be used as view drawing participation data. When determining the view drawing participation data through the selected configuration item, it can be detected whether each configuration item in the demand list is selected, and the data corresponding to the selected configuration item is determined as the view drawing participation data.

S260: Draw the target view according to the selected view display form, view name information and view drawing participation data.

The view display form includes at least one of list view, column chart, pie chart, line chart, curve chart, three-dimensional view and Gantt chart. The list view can clearly display all detailed information, such as business lines, priorities, responsible persons or progress nodes, etc. A Gantt chart is a type of bar chart that displays the progress and relationships of projects, schedules, and other time-related systems over time. The Gantt chart can visually display the progress of requirements, nodes, node subtasks, or individual version iterations. For example, the Gantt chart supports step size settings and supports display in different time granules, such as months, bi-months, half-years and years.

In this embodiment, the alternative view display form can be displayed in advance. The display method can be a hidden folded display or an expanded display. When it is detected that the control corresponding to the alternative view display form is triggered, the triggered alternative view display form can be Determine the target view display format, display the view drawing participation data in the interface according to the target view display format, and display the view name information correspondingly to generate the target view.

S270. When the triggering view determination control is detected, the target view is regarded as the created view, and the view association information of the target view is updated to the view management list.

The view determination control is used to confirm whether the generated target view is determined as a created view and to update the view management list. In an embodiment, in order to prevent misoperation, a view determination control may be set, and when the view determination control is triggered, the target view will be regarded as the created view.

For example, in order to facilitate finding the target view, the view management information of the target view can be updated into the view management list. For example, the view association information corresponding to the target view can be added to the view management list according to the view creation time sequence.

For example, the view type of the created view can also be set. For example, when the currently displayed created view is set to the system view switch control is turned on, the displayed created view can be set to the system view by the user; for the system view Provides a "Favorite for Control Members" control, through which system views can be favorited, and the system views will be pinned to the top of the favorited views list by default. For example, the row size and column size of the created view can also be set. For example, the row height of the table in the view can be divided into compact, moderate, high, super high and custom types; similarly, the row width can be Set to compact, moderate, high, super high and custom types; you can save the set row and row sizes, and then open the created view again to display according to the saved row and row sizes.

In an embodiment, when displaying the created view, an "open in new tab" option can be provided on the display interface. After this option is selected, a new page is restarted and the created view is displayed at the same time.

In this embodiment, it also includes: setting browsing permissions and operation permission information for the created view to determine the external visibility of the created view based on the browsing permission, and performing management operations on the created view based on the operation permission information; generating and creating The view link corresponding to the view to obtain the created view based on the view link.

In order to better manage views and improve security, you can set browsing rights for created views. Restrictions and operation permission information. The operation permission information includes at least one operation permission of sorting, sharing, collecting, deleting, modifying, exporting and upgrading the view to be managed, and different users have different operation permissions for different views to be managed.

In embodiments, different browsing permissions and operation permission information can be set for the created views according to different role types of the operating users. For example, when the view management method provided in this embodiment is applied to a project management system, the operation permissions of various role types can be set in the settings panel by clicking the "Edit" control. Operation permissions can be divided into the following situations: 1. Public permissions, that is, all visitors can modify the view settings; 2. Non-public permissions, only the creator or collaborator can modify the view settings; 3. Collaborators can modify the view display conditions , the view display conditions can be synchronously applied to all view visitors after saving the changes; 4. In the fixed view, collaborators can add or remove the demand list in the fixed view.

For example, for an operation user whose role type is a view creator, the browsing permission can be set to allow browsing, and the operation permission can be set to perform at least one operation of sorting, sharing, collecting, deleting, modifying, exporting, and upgrading the view; for For operating users whose role type is collaborator, they can set the browsing permission to allow browsing, and the operating permission to be unable to perform any of the operations of sorting, sharing, collecting, deleting, modifying, exporting, and upgrading; for users whose role type is illegal, that is, no operations can be performed. If you register as a user, set the browsing permission to not allow browsing, and the operation permission to not allow any operations.

For example, in order to facilitate the user to obtain the view quickly and conveniently, a view link can be generated based on the view association information of the created view, the view link can be displayed to the corresponding position of the created view in the view management list, and the corresponding view link can be directly accessed through the view link. View created.

S280. When it is detected that the sorting control in the view to be managed is triggered, the indicator item corresponding to the sorting control is determined, the data in the view to be managed is sorted according to the indicator item, and the view to be managed is updated.

The indicator items are column headers and/or row headers in the view to be managed. The column header includes at least one of creation time, view data volume, creation user, task leader, and priority; the row header includes the view identifier. Sorting processing includes ascending order processing and descending order processing, and sorting controls include ascending order sorting controls and descending order sorting controls.

In an embodiment, the implementation method of determining the indicator items corresponding to the sorting control may include: when the sorting control triggering the view to be managed is detected, a sorting selection window pops up, and the selected indicator items in the sorting selection window are determined to follow the The selected indicator item sorts the data in the management view; alternatively, a corresponding sorting sub-control is established for each header item included in the row header and/or column header. When the sorting sub-control is detected and is triggered, Determine the header item corresponding to the triggered sorting sub-control, sort the data in the view to be managed according to the header item, and update the view to be managed according to the sorting result.

For example, as shown in Figure 6, the column header includes the name, creation user, creation time, etc., and the row header includes view association information; in the table of each item in the column header, a "↑" control is set, Used to indicate ascending order, and a "↓" control is also provided to indicate descending order; by clicking on the ascending order and descending order controls, the sorting order is determined; and the indicator items corresponding to the click operation are determined, and the sorting is determined according to Sort the determined indicator items in order to obtain the view to be managed that conforms to the sorting order.

In this embodiment, when it is detected that the group control in the view to be managed is triggered, the grouping information corresponding to the grouping control is determined, the data in the view to be managed is grouped according to the grouping information, and the view to be managed is updated. For example, you can configure grouping items by editing the page, generate grouping information based on the configured grouping items, and group the data in the management view to display the data clearly and at multiple levels. As an example, three levels of grouping may be supported.

For example, controls such as node flow and status flow can also be set in the view. When it is detected that the node flow control is triggered, the information of the flow nodes can be obtained based on the node flow control, and node flow can be quickly performed in the view to be managed. State flow includes status flow between defect, iteration, and version views. Through the state flow control, quick switching between defect, iteration, and version views is realized.

In this disclosed embodiment, the target view can be created through the view creation control, and the browsing permissions and operating permissions of the created view can be set to improve the security of view operations; and through the established view link, you can quickly and conveniently search, Get the created view you want to operate. In addition, the embodiments of the present disclosure can also sort the data in the to-be-managed view according to the indicator items, which can better meet the diverse needs of users.

FIG. 7 is a schematic structural diagram of a view management device provided by an embodiment of the present disclosure. The device can execute the view management method provided by any embodiment of the present disclosure, and has functional modules and effects corresponding to the execution method. As shown in Figure 7, the device includes: a view management list display module 310, a view to be managed operation module 320, and a view to be managed update module 330.

The view management list display module 310 is configured to display a view management list when a triggered view processing control is detected, wherein the view management list includes view association information of at least one created view that is currently managed;

The view operation module 320 to be managed is configured to use the created view corresponding to the view association information triggered in the view management list as the view to be managed, and to operate the view based on the operation permission information corresponding to the view to be managed. The view to be managed performs management operations;

The view update module 330 to be managed is configured to update the view to be managed based on the view corresponding to when the management operation is completed.

Based on the above multiple technical solutions, the device also includes:

View name information acquisition module, set to obtain the view when the triggering view creation control is detected View name information in the name editing control;

The view drawing participation data determination module is configured to obtain at least one filter condition and/or at least one configuration item selected from the requirement list and determine the view drawing participation data;

The target view drawing module is set to draw the target view based on the selected view display form, view name information, and view drawing participation data;

A view management list update module configured to use the target view as the created view when a triggered view determination control is detected, and update the view association information of the target view to the view management list;

Wherein, the view display format includes at least one of list view, bar chart, pie chart, line chart, curve chart, three-dimensional view and Gantt chart.

Based on the above multiple technical solutions, the device also includes:

A management operation module configured to set browsing permissions and operation permission information for the created view, to determine the external visibility of the created view based on the browsing permission, and to set the created view based on the operation permission information. Carry out management operations;

A view link generation module is configured to generate a view link corresponding to the created view, so as to obtain the created view based on the view link.

Based on the above multiple technical solutions, the view management list display module 310 includes:

Window pop-up unit, set to pop up a window including a view management list;

The list expansion unit is set to expand and display the collapsed view management list in the display interface.

Based on the above multiple technical solutions, the view association information includes at least one indicator item, and the at least one indicator item includes at least one of view name information, creator identification, creation time, browsing permissions, and collaborators; The created views include at least one of a system view, a fixed view, and a conditional view.

Based on the above multiple technical solutions, the system view is a template view created by the administrator;

The fixed view is a view created after selecting at least one configuration item from a fixed requirement list, where the configuration item includes links to other views, data links, and at least one of each requirement item in project associated data. ;

The conditional view is a view generated after determining the view participating data based on preset filtering conditions.

Based on the above multiple technical solutions, the view operation module 320 to be managed includes:

A view sharing unit, configured to detect a sharing operation on the view to be managed, and the When the operation permission information includes sharing permission, share the view link of the view to be managed to at least one user to be shared, so as to obtain the view to be managed based on the view link.

The view collection unit is configured to collect the view to be managed or uncollect the view to be managed if the operation permission information includes the collection permission.

A view batch management unit configured to perform batch management operations on at least one view to be managed if the operation permission information includes a batch operation of views;

The view batch operations include at least one of batch upgrade, batch deletion, batch modification, batch export, and drag and drop.

Based on the above multiple technical solutions, the device also includes:

The indicator item determination module is configured to determine the indicator item corresponding to the sorting control when triggering the sorting control in the view to be managed is detected;

A view data sorting module configured to sort the data in the view to be managed according to the indicator item and update the view to be managed;

Wherein, the indicator item is a column header and/or a row header in the view to be managed.

The view management device provided by the embodiments of the present disclosure can execute the view management method provided by any embodiment of the present disclosure, and has corresponding functional modules and effects for executing the method.

The multiple units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above-mentioned divisions, as long as they can achieve the corresponding functions; in addition, the names of the multiple functional units are only for the convenience of distinguishing each other. , are not used to limit the protection scope of the embodiments of the present disclosure.

FIG. 8 is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. Referring now to FIG. 8 , a schematic structural diagram of an electronic device (such as the terminal device or server in FIG. 8 ) 400 suitable for implementing embodiments of the present disclosure is shown. Terminal devices in embodiments of the present disclosure may include mobile phones, Notebook computers, digital broadcast receivers, personal digital assistants (Personal Digital Assistant, PDA), tablet computers (Portable Android Device, PAD), portable multimedia players (Portable Media Player, PMP), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc. Mobile terminals such as digital television (TV), desktop computers, etc. The electronic device shown in FIG. 8 is only an example and should not impose any limitations on the functions and scope of use of the embodiments of the present disclosure.

As shown in Figure 8, the electronic device 400 may include a processing device (such as a central processing unit, a graphics processor, etc.) 401. The processing device 401 may process data according to a program stored in a read-only memory (Read-Only Memory, ROM) 402 or from a program. The storage device 408 loads the program in the random access memory (Random Access Memory, RAM) 403 to perform various appropriate actions and processes. In the RAM 403, various programs and data required for the operation of the electronic device 400 are also stored. The processing device 401, ROM 402 and RAM 403 are connected to each other via a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.

The following devices can be connected to the I/O interface 405: input devices 406 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a liquid crystal display (LCD), speaker , an output device 407 such as a vibrator; a storage device 408 including a magnetic tape, a hard disk, etc.; and a communication device 409. The communication device 409 may allow the electronic device 400 to communicate wirelessly or wiredly with other devices to exchange data. Although FIG. 8 illustrates electronic device 400 with various means, implementation or availability of all illustrated means is not required. More or fewer means may alternatively be implemented or provided.

According to embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product including a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such embodiments, the computer program may be downloaded and installed from the network via communication device 409, or from storage device 408, or from ROM 402. When the computer program is executed by the processing device 401, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

The electronic device provided by the embodiment of the present disclosure belongs to the same concept as the view management method provided by the above embodiment. Technical details that are not described in detail in this embodiment can be referred to the above embodiment, and this embodiment has the same effect as the above embodiment. .

Embodiments of the present disclosure provide a computer storage medium on which a computer program is stored. When the computer program is executed by the processor, the view management method provided by the above embodiment is implemented.

The computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. Computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard drives, RAM, ROM, Erasable Programmable Read-Only Memory (EPROM), flash memory, fiber optics, Portable Compact Disc Read-Only Memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In this disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take many forms, including electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device . Program code embodied on a computer-readable medium can be transmitted using any appropriate medium, including: wire, optical cable, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.

In some embodiments, the client and server can communicate using any currently known or future developed network protocol, such as HyperText Transfer Protocol (HTTP), and can communicate with digital data in any form or medium. Communications (e.g., communications network) interconnections. Examples of communication networks include Local Area Networks (LANs), Wide Area Networks (WANs), the Internet (e.g., the Internet), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any current network for knowledge or future research and development.

The above-mentioned computer-readable medium may be included in the above-mentioned electronic device; it may also exist independently without being assembled into the electronic device.

The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: displays a view management list when the view processing control is detected to be triggered, wherein the view management list The list includes view association information of at least one created view that is currently managed; the created view corresponding to the view association information triggered in the view management list is used as a view to be managed, and is based on the operation corresponding to the view to be managed. Permission information is used to perform management operations on the view to be managed; based on the corresponding view when the management operation is completed, the view to be managed is updated.

Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, including object-oriented programming languages—such as Java, Smalltalk, C++, and also conventional procedural programming languages—such as "C" or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In situations involving remote computers, the remote computer may be connected to the user computer through any kind of network, including a LAN or WAN, or may be connected to an external computer (eg, through the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operations 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 diagram may represent a module, segment, or portion of code that contains one or more logic functions that implement the specified executable instructions. 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 one after another may actually execute substantially in parallel, or they may sometimes execute in the reverse order, depending on the functionality involved. Each block in the block diagram and/or flowchart illustration, and combinations of blocks in the block diagram and/or flowchart illustration, may be implemented by special purpose hardware-based systems that perform the specified functions or operations, or may be implemented using special purpose hardware implemented in combination with computer instructions.

The units involved in the embodiments of the present disclosure can be implemented in software or hardware. In one case, the name of the unit does not constitute a limitation on the unit itself. For example, the first acquisition unit can also be described as "the unit that acquires at least two Internet Protocol addresses."

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used include: Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), Application Specific Standard Parts (ASSP) , System on Chip (SOC), Complex Programmable Logic Device (CPLD), etc.

In the context of this disclosure, a machine-readable medium may be a tangible medium that may 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. Machine-readable media may include electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination of the foregoing. Machine-readable storage media includes one or more wire-based electrical connections, portable computer disks, hard drives, RAM, ROM, EPROM, flash memory, fiber optics, portable CD-ROMs, optical storage devices, magnetic storage devices, or the above Inside any suitable combination of contents. The storage medium may be a non-transitory storage medium.

According to one or more embodiments of the present disclosure, [Example 1] provides a view management method, including:

According to one or more embodiments of the present disclosure, [Example 2] provides a view management method, including:

When the triggering view creation control is detected, obtain the view name information in the view name editing control;

Obtain at least one filter condition and/or at least one configuration item selected from the requirement list to determine the view drawing participation data;

Draw the target view based on the selected view display form, view name information, and view drawing participation data;

When a triggered view determination control is detected, use the target view as the created view, and update the view association information of the target view to the view management list;

According to one or more embodiments of the present disclosure, [Example 3] provides a view management method, including:

Set browsing permissions and operation permission information for the created view to determine the external visibility of the created view based on the browsing permissions, and perform management operations on the created view based on the operation permission information;

Generate a view link corresponding to the created view to obtain the created view based on the view link.

According to one or more embodiments of the present disclosure, [Example 4] provides a view management method, including:

A window including a view management list pops up;

Expand and display the collapsed view management list in the display interface.

According to one or more embodiments of the present disclosure, [Example 5] provides a view management method, including:

The view association information includes at least one indicator item, and the at least one indicator item includes at least one of view name information, creator identification, creation time, browsing permissions, and collaborators; the created views include system views, At least one of fixed views and conditional views.

According to one or more embodiments of the present disclosure, [Example 6] provides a view management method, including:

The system view is a template view created by the administrator;

According to one or more embodiments of the present disclosure, [Example 7] provides a view management method, including:

When a sharing operation on the view to be managed is detected, and the operation permission information includes sharing permissions, share the view link of the view to be managed to at least one user to be shared, so as to obtain the view based on the view link. The view to be managed.

According to one or more embodiments of the present disclosure, [Example 8] provides a view management method, including:

If the operation permission information includes the collection permission, the view to be managed is collected or the view to be managed is uncollected.

According to one or more embodiments of the present disclosure, [Example 9] provides a view management method, including:

If the operation permission information includes view batch operations, perform batch management operations on at least one view to be managed;

According to one or more embodiments of the present disclosure, [Example 10] provides a view management method, including:

When it is detected that the sorting control in the view to be managed is triggered, determine the indicator item corresponding to the sorting control;

Sort the data in the view to be managed according to the indicator items, and update the view to be managed;

According to one or more embodiments of the present disclosure, [Example 11] provides a view management device, including:

Furthermore, although various operations are depicted in a specific order, this should not be understood as requiring that these operations be performed in the specific order shown or performed in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although numerous implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Some features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

A view management method including:

When triggering the view processing control is detected, display a view management list, wherein the view management list includes view association information of at least one created view that is currently managed;

Use the created view corresponding to the view association information triggered in the view management list as a view to be managed, and perform management operations on the view to be managed based on the operation permission information corresponding to the view to be managed;

The view to be managed is updated based on the corresponding view when the management operation is completed.
The method of claim 1, further comprising:

When a triggering view creation control is detected, obtain the view name information in the view name editing control;

Perform at least one of the following to determine the view drawing participation data: obtain at least one filter condition; select at least one configuration item from the requirements list;

Draw the target view according to the selected view display form, the view name information and the view drawing participation data;

When the triggering view determination control is detected, use the target view as the created view, and update the view association information of the target view to the view management list;

Wherein, the view display format includes at least one of list view, bar chart, pie chart, line chart, curve chart, three-dimensional view and Gantt chart.
The method of claim 2, further comprising:

Browse permissions and operation permission information are set for the created view to determine the external visibility of the created view based on the browsing permissions, and management operations are performed on the created view based on the operation permission information.
The method of claim 2, further comprising:

Generate a view link corresponding to the created view to obtain the created view based on the view link.
The method according to claim 1, wherein the displaying the view management list includes:

Pop up a window including the view management list;

Expand and display the collapsed view management list in the display interface.
The method according to claim 1, wherein the view association information includes at least one indicator item, and the at least one indicator item includes at least one of the following: view name information, creator identification, Creation time, browsing permissions, and collaborators; the created views include at least one of the following: system view, fixed view, and conditional view.
The method according to claim 6, wherein the system view is a template view created by an administrator;

The fixed view is a view created after selecting at least one configuration item from a fixed requirement list, where the configuration item includes links to other views, data links, and at least one of multiple requirement items in project associated data. one;

The conditional view is a view generated after determining the view participating data based on preset filtering conditions.
The method according to claim 1, wherein said performing a management operation on the view to be managed based on the operation permission information corresponding to the view to be managed includes:

When a sharing operation on the view to be managed is detected, and the operation permission information includes sharing permissions, share the view link of the view to be managed to at least one user to be shared, based on the view link Get the view to be managed.
The method according to claim 1, wherein said performing a management operation on the view to be managed based on the operation permission information corresponding to the view to be managed includes:

If the operation authority information includes the collection authority, the view to be managed is collected or the view to be managed is uncollected.
The method according to claim 1, wherein said performing a management operation on the view to be managed based on the operation permission information corresponding to the view to be managed includes:

When the operation permission information includes batch operations of views, perform batch management operations on at least one view to be managed;

The view batch operations include at least one of batch upgrade, batch deletion, batch modification, batch export, and drag and drop.
The method of claim 1, further comprising:

When it is detected that the sorting control in the view to be managed is triggered, determine the indicator item corresponding to the sorting control;

Sort the data in the view to be managed according to the indicator items, and update the view to be managed;

Wherein, the indicator item is at least one of the following in the view to be managed: a column header or a row header.
A view management device including:

A view management list display module configured to display a view management list when triggering a view processing control is detected, wherein the view management list includes view association information of at least one created view that is currently managed;

The view operation module to be managed is configured to use the created view corresponding to the view association information triggered in the view management list as the view to be managed, and to operate the view based on the operation permission information corresponding to the view to be managed. Describe the management view to perform management operations;

The view update module to be managed is configured to update the view to be managed based on the corresponding view when the management operation is completed.
An electronic device including:

one or more processors;

a storage device configured to store one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the view management method according to any one of claims 1-11.
A storage medium containing computer-executable instructions that, when executed by a computer processor, are used to perform the view management method according to any one of claims 1-11.