Project management method and device and electronic equipment

Abstract

The embodiment of the invention discloses a project management method and device and electronic equipment. A specific embodiment of the method comprises the following steps: in a project management system, in response to a team creation instruction for a target entity, displaying a team creation interface; displaying a plurality of team type options in the team creation interface; according to the selected team type option, displaying a team member determination interface corresponding to the team type; and determining team members based on the team member determination interface, and creating a team of the target entity with the determined team members. Therefore, a new project management method is obtained, teams can be created through different ways for the target entity, and the dimensionality of personnel management is enriched.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a project management method, device and electronic device. Background Art

[0002] With the development of computers, users can use electronic devices to achieve various functions. For example, users can interact with other users through electronic devices, and can also use electronic devices to advance work.

[0003] In some scenarios, data management-based tools or platforms (such as project management systems) can be built to accelerate project launch and avoid project risks by creating standardized business processes. Summary of the invention

[0004] This disclosure section is provided to introduce concepts in a brief form, which will be described in detail in the detailed description section below. This disclosure section is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0005] In a first aspect, an embodiment of the present disclosure provides a method for project management, the method comprising: in a project management system, in response to a team creation instruction for a target entity, displaying a team creation interface; in the team creation interface, displaying a plurality of team type options; based on the selected team type option, displaying a team member determination interface corresponding to the team type; determining team members based on the team member determination interface, and creating a team of the target entity with the determined team members.

[0006] In a second aspect, an embodiment of the present disclosure provides a project management method, the method comprising: displaying multiple root teams of a target entity in a project management system; wherein a root team has subordinate teams, and an intersection between subordinate teams of at least two root teams is not empty.

[0007] In a third aspect, an embodiment of the present disclosure provides a project management device, comprising: a first display unit for displaying a team creation interface in a project management system in response to a team creation instruction for a target entity; a second display unit for displaying a plurality of team type options in the team creation interface; a third display unit for displaying a team member determination interface corresponding to the team type according to the selected team type option; and a creation unit for determining team members based on the team member determination interface, and creating a team of the target entity with the determined team members.

[0008] In a fourth aspect, an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the project management method as described in the first aspect or the second aspect.

[0009] In a fifth aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the project management method as described in the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0011] Figure 1 is a flowchart of an embodiment of a method for project management according to the present disclosure;

[0012] Figure 2A , Figure 2B , Figure 2C , Figure 2D is a schematic diagram of an application scenario of the project management method according to the present disclosure;

[0013] Figure 3A , Figure 3B , Figure 3C , Figure 3D , Figure 3E , Figure 3F , Figure 3G , Figure 3H , Fig. 3I , Figure 3J , Figure 3K , Figure 3L is a schematic diagram of an application scenario of the project management method according to the present disclosure;

[0014] Figure 4 is a flowchart of an embodiment of a method for project management according to the present disclosure;

[0015] Figure 5 is a schematic structural diagram of an embodiment of a project management device according to the present disclosure;

[0016] Figure 6 is an exemplary system architecture to which the project management method of an embodiment of the present disclosure may be applied;

[0017] Figure 7It is a schematic diagram of the basic structure of an electronic device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0018] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0019] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0020] The term "including" and its variations used herein are open inclusions, i.e., "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 embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0021] It should be noted that the concepts such as "first" and "second" mentioned in the present 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.

[0022] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

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

[0024] Here, for the convenience of explanation, some concepts that may be involved in the present disclosure are first introduced.

[0025] Project Management System: A software system used to help project teams plan, organize, execute and monitor project processes.

[0026] Space is a basic unit of organizational collaboration, which can be the management of a single project or a collection of multiple projects.

[0027] Work items are a collaborative work item for a team, or a collection of items broken down by a project. Work items can be divided into different types according to their content, such as requirements, defects, versions, iterations, milestones, deliverables, etc.

[0028] Requirements (Feature) can refer to the software functions required by users to solve a problem / achieve a goal. It can help team members track specific details.

[0029] Issues refer to those that do not meet the originally defined business requirements, for example, pop-up windows do not display.

[0030] View is a collection of query dimensions of work items that are of high frequency concern within the team. It can also be called view dual specialization. Views can be of various types, such as tables, lists, Kanban boards, Gantt charts, metrics, etc. Tables can be permutations and combinations of field information, arranging data in a cell mode. Gantt charts can display project progress in a time dimension through bar charts. Metrics are a continuous quantitative process of defining, collecting, and analyzing data for software development projects, processes, and their products. For example, demand throughput, quality, cycle and labor estimation.

[0031] Role: various roles involved in a project. A project requires the support of different roles.

[0032] WBS (W and / or k Breakdown Structure) plan, that is, work breakdown structure plan, can also be called WBS plan, or simply as a plan.

[0033] A process is a basic step in the life cycle of an event, which is composed of process nodes and execution methods in an orderly manner. Nodes can refer to the stage division points of a process.

[0034] Please refer to Figure 1 , which shows the process of an embodiment of the project management method according to the present disclosure. This embodiment can be applied to a project management system. Figure 1 The project management method shown includes the following steps:

[0035] Step 101: In a project management system, in response to a team creation instruction for a target entity, a team creation interface is displayed.

[0036] Here, a team is a system object preset in a project management system that expresses a collection of personnel. It carries various sets of personnel with business meanings, expresses the relationships between various sets of personnel, and supports consumption by different business parties in the project management system.

[0037] Step 102, in the team creation interface, multiple team type options are displayed.

[0038] Step 103: Based on the selected team type option, a team member determination interface corresponding to the team type is displayed.

[0039] Step 104 , determining team members based on a team member determination interface, and creating a team of the target entity with the determined team members.

[0040] The project management method provided by this embodiment is as follows: in the project management system, in response to a team creation instruction for a target entity, a team creation interface is displayed; in the team creation interface, multiple team type options are displayed; according to the selected team type option, a team member determination interface corresponding to the team type is displayed; team members are determined based on the team member determination interface, and a team of the target entity is created with the determined team members; thus, by providing multiple team type options during the team creation process, multiple personnel management systems can be built to enrich the dimensions of personnel management.

[0041] As an example, see Figure 2A ,exist Figure 2A In the team creation interface, a user type (eg, personnel), a department type (bound department), and a group type (eg, bound group) may be provided.

[0042] In contrast, some related technologies can only support a single personnel management system (such as an organizational structure or a project team), and cannot support the simultaneous establishment of multiple types of personnel collections.

[0043] In some embodiments, the multiple team type options include at least two of the following: associating all or part of the organizational structure to create a department type team; associating a group to create a group type team; selecting user to create a new team to create a user type team.

[0044] Triggering the Create a New Team control will pop up the Create a New Team interface. Through the Create a New Team interface, you can enter a team name; enter a team name; enter a team description. Through the Create a New Team interface, you can select the team type, which cannot be modified after creation. The team type includes the user type. After selection, a team member selection box will pop up; the team type includes the department type, select the associated department (when the organizational structure is turned on to generate a team synchronously, it does not support the creation of a team with a department type); group type, you need to select the associated group. Through the Create a New Team interface, you can set the space that can be used by this team: you can select the space that is visible to you (if you are a member of the space); if you are an enterprise administrator, you can select all spaces.

[0045] Therefore, department-type teams are established for organizational structures; group-type teams are created for project groups or business line scenarios; and user-type teams are established for user self-selection methods, so as to achieve personnel management covering multiple scenarios and enrich the personnel management dimensions.

[0046] In some embodiments, the team created for the target entity is the root team of the target entity; and the method further includes: displaying multiple root teams of the target entity, wherein the root team has subordinate teams, and the multiple levels of subordinate teams of the root team are associated with each other according to the superior-subordinate relationship.

[0047] In this way, it is possible to build multiple personnel management systems and flexibly link various personnel systems.

[0048] As an example, see Figure 2B , Figure 2B Multiple root teams of the target entity are shown, such as Team A-Organizational Structure, Team B-Business Line, and Team C-Permission Revision Project. Figure 2B The solid arrow in the figure points to Team A, a subordinate team in the organizational structure. Figure 2B A team is shown in each box. Figure 2B The dotted arrow in the figure points to Team B, the subordinate team of the business line. Figure 2B The dotted arrow in the figure points to the subordinate team of Team C-Permission Modification Project.

[0049] In some embodiments, the intersection between the subordinate teams of at least two root teams among the multiple root teams is not empty.

[0050] In this way, a network team structure can be formed, flexible connections between various sets of personnel can be achieved, and a variety of scenarios in project management can be supported.

[0051] As an example, see Figure 2B It can be seen that the subordinate teams of Team A-Organizational Structure and Team B-Business Line include View Design, Platform Design, View Product Manager, and Platform Product Manager. The subordinate teams of Team B-Business Line and Team C-Permission Revision Project include Platform Product Manager-Permission.

[0052] As an example, see Figure 2C , Figure 2C It is shown that multiple root teams and subordinate teams of each root team are displayed for the target entity.

[0053] In some embodiments, between teams having a direct or indirect superior-subordinate relationship, the administrator of the superior team has management authority over the subordinate team.

[0054] In this way, it is possible to build multiple personnel management systems and flexibly link various personnel systems.

[0055] As an example, see Figure 2D , Figure 2D A schematic diagram of the relationship between three teams with a superior-subordinate relationship is shown. The administrator of the current team A1 has management authority over the subordinate team A11. The administrator of A1 can create a subordinate team A11 and can dissolve the association with A11 (after the contact, there is no relationship between A and A11). The superior team A has management authority over both A1 and A11. The administrator of A can initiate a subordinate team association request to A1, and the administrator of the A1 team can agree to the team association. The administrator of A can dissolve the association with A1 (without affecting the relationship between A1 and A11). The association between superior and subordinate teams can be through the association between existing teams (for example, as shown by A and A1), or by creating a subordinate team under the superior team (for example, as shown by A1 and A11).

[0056] In some embodiments, the method also includes: displaying a team interface of the target user, wherein the team interface includes a team navigation interface and / or a team details interface; wherein the team navigation interface is used to display the team identification of the team associated with the target user; and the team details interface is used to display relevant information of the target team, wherein the team indicated by the team identification selected in the team navigation interface is the target team.

[0057] In some embodiments, the team navigation interface includes one or more of the following: a first navigation sub-interface and a second navigation sub-interface; wherein the first navigation sub-interface is used to display a first team of which the target user is a direct team member, and subordinate teams of the first team; and the second navigation sub-interface displays a second team of which the target user is a team administrator, and subordinate teams of the second team.

[0058] As an example, the first navigation sub-interface may identify the team I am in. The second navigation sub-interface may identify the team being managed.

[0059] In some embodiments, the team navigation interface includes the team I am in (the currently logged in user is a team member) and the team I manage (the currently logged in user is a team administrator). Optionally, the team I am in can be positioned by default, and the user's selection can be cached locally.

[0060] For the team I am in, you can display the team that the current person is in (as a direct member) and all subordinate teams of the team. Optionally, when displaying, you can determine whether there is a superior-subordinate relationship between all teams that the current person is a direct member of, and display those teams without superior relationships (no association or the top of all associations) flatly, and other teams are hidden by default, and you can click to expand and view the subordinate teams of the team you are in.

[0061] For the teams I manage, all teams of which the current person is the direct team administrator and all subordinate teams of these teams are displayed. Optionally, when displaying, the teams directly managed by the current person can be calculated first to determine whether these teams have a superior-subordinate relationship, and those teams without a superior relationship (the top layer without any association or all associations) can be displayed flatly, and other teams are hidden by default; then all teams can be expanded downwards to the last level.

[0062] The team navigation interface includes a new team control. Triggering the new team control can pop up the new team interface. Therefore, through the new team interface, you can enter the team name, enter the team name; enter the team description. Through the new team interface, you can select the team type, which cannot be modified after creation. Among them, the team type includes the user type, and a team member selection box pops up after selection; the team type includes the department type, select the associated department (when the organizational structure is turned on to synchronize the team generation, it does not support the creation of a team with a department type); group type, you need to select the associated group. Through the new team interface, you can set the space that can be used by this team: support selecting the space visible to yourself (if you are a member of the space); if you are an enterprise administrator, support selecting all spaces.

[0063] In the team display interface, you can display the team's unauthorized interface or the team details page.

[0064] As an example, see Figure 3J , when the current user is not a direct member of the team, administrator, or superior team administrator, clicking the team name or entering the URL will enter the team permissionless interface. In the team permissionless interface, the team name, description, avatar, tag, and team administrator (the two most recently added administrators are taken by default) can be displayed.

[0065] Optionally, you can list several situations where the team has no permission to view the interface: a direct team member is on the team's parent team page; a direct team member is in the My Team list on the left and clicks on a subordinate team of which he is not a direct member; when you directly enter a team through a URL and the current person has no permission to view the team.

[0066] When the current user is any of the following: team member, administrator, or superior team administrator, the team details page is displayed.

[0067] In some embodiments, the method also includes: in response to the target user being a direct team member of the target team, displaying the team members and superior team of the target team in the team details interface; in response to the target user being a team administrator or superior team administrator of the target team, displaying the team members, superior team and subordinate team of the target team in the team details interface; in response to the target user not being any of the following of the target team: team member, team administrator and superior team administrator, displaying a no-authorization prompt message in the team details interface.

[0068] As an example, if the target user is a direct team member of the target team and the target team is the user team, you can Figure 3A As shown, the team members of the target team are displayed on the team details page; team members include direct team members. Team members can see the exit team control in their own row and click it to exit the team.

[0069] As an example, if the target user is a direct team member of the target team and the target team is of type department, you can Figure 3B As shown, team members are displayed on the team details page; team members include direct team members. A list of direct members can be displayed below the team members. If the team type is a department team, the name of the associated department is displayed.

[0070] As an example, if the target user is a direct team member of the target team and the target team is a group type, you can Figure 3C As shown in the figure, team members are displayed on the team details page. A list of direct members can be displayed below the team members. If the team type is a group team, the name of the associated group is displayed.

[0071] As an example, see Figure 3A , Figure 3B and Figure 3C , the target user is a direct member of the target team. The team members can be displayed on the team details page. The team members include a list of subordinate members, showing the composition of the subordinate teams of the team (personnel, groups, departments), and each component element is deduplicated. As an example, for the parent team A, member A is in the subordinate team A1 and the subordinate team A2. Then, in the subordinate member list of the parent team A, only member A is displayed once, and team A1 and team A2 are displayed in the team to which member A belongs. As an example, member A belongs to department A3 at the same time, and subordinate team A4 is associated with department A3. Then, in the subordinate team list of the parent team A, team A1, A2 to which member A belongs, and team A4 to which department A3 belongs will be displayed. When the subordinate team type is department / group, the department / group is displayed here, and the users of the specific department / group are not displayed.

[0072] For example, if the target user is a direct team member of the target team, the parent team of the target team is displayed on the team details page, such as Figure 3D As shown; all first-level parent teams are visible; when clicking on a parent team, the team homepage visibility of the current user in the corresponding team is verified; the current user is a member or has management authority in the corresponding team: the complete team details page (including user list, superior and subordinate list, etc.) is visible; the current user has no member / management authority: the team's no-authority page (team basic information and team administrator) is visible.

[0073] As an example, if the target user is a team admin or parent team admin of the target team and the target team is a user team, such as Figure 3E As shown in the figure, team members are displayed on the team details page; team members include direct team members. Figure 3E In the scenario of , you can delete direct members.

[0074] As an example, if the target user is a team administrator or a parent team administrator of the target team and the target team is a department team, such as Figure 3F As shown in the figure, team members are displayed on the team details page; team members include direct team members. Figure 3F In the scenario, you can modify the associated department.

[0075] As an example, if the target user is a team admin or parent team admin of the target team and the target team is a group team, such as Figure 3G As shown in the figure, team members are displayed on the team details page; team members include direct team members. Figure 3G In the scenario, you can modify the associated group.

[0076] As an example, if the target user is a team administrator or a parent team administrator of the target team, such as Figure 3H As shown, the parent team is displayed on the team details page; all first-level parent teams are visible; when clicking on a parent team, the team homepage visibility of the current user in the corresponding team is verified. If the current user is a member or has management authority in the corresponding team, the complete team details page (including user list, superior and subordinate list, etc.) can be seen; if the current user has no member / management authority: the team's no-authority page (team basic information + team administrator) can be seen.

[0077] As an example, if the target user is a team administrator or a parent team administrator of the target team, such as Fig. 3IAs shown in the figure, the subordinate teams are displayed on the team details page; when clicked, all pages of the corresponding subordinate team can be viewed (with the same permissions as the team administrator). It supports unbinding one-level subordinate teams, and a notification is sent to the subordinate team administrator when unbinding. It does not support cross-level unbinding of associations. Display the add subordinate team control, and click it to enter the add subordinate team page; you can add a new team or add an existing team. Click the subordinate team button to jump to the subordinate team details page (default location is the member list page). The team administrator's permissions are the administrator of all subordinate teams by default.

[0078] As an example, the team details page may include basic team information, a list of team members, a list of upper-level teams, and a list of lower-level teams.

[0079] Team basic information may include team information and team-related operation controls.

[0080] Team information can include team avatar, name, tags, and description, which are visible to everyone who has permission to see the team.

[0081] Team label description: The system sets 3 labels. Organizational structure: associated with the team creation method, used to identify the team created by synchronizing the organizational structure; when the organizational structure synchronization function is disabled, this label will be automatically deleted for all teams created by organizational structure synchronization; - When the organizational structure synchronization function is enabled again, this label will be added to all teams created by organizational structure synchronization. Associated group abnormality: linked with the group, when the associated group identifier cannot be found, this label will be automatically added to the corresponding team to remind the team administrator to pay attention; when the associated group is changed, this label will be automatically cancelled; Associated department abnormality: linked with the associated department, when the associated department identifier cannot be found, this label will be automatically added to the corresponding team to remind the team administrator to pay attention; when the associated department is changed, this label will be automatically cancelled.

[0082] In some embodiments, the method also includes: in response to the target user being a team administrator or a superior team administrator of the target team, displaying a setting control on the team details interface; in response to a trigger operation on the setting control, displaying at least one of the following: a team setting control, an administrator setting control, a copy team ID control, and a team operation record viewing control.

[0083] In other words, team-related operation controls are only visible to team administrators and superior team administrators.

[0084] Click on the pop-up function selection list to display team-related operation controls.

[0085] Team-related operation controls Team settings controls, team administrator settings controls, copy team ID controls, operation record controls. (As an example, please refer to Figure 3K )

[0086] Trigger the team settings control to display the team settings list.

[0087] The team setting list may include team type, team logo, team name, team avatar, team description, controls that can be used by the team, and deletion of team controls.

[0088] Team type: if it is a user type, the number of direct team members is displayed; if it is a department type, the associated department name (name of the department) and the control for changing the associated department are displayed. Click this to change the department associated with the current team. The team is created in a synchronized organizational structure and there is no button for changing the associated department. Group type: the associated group name and the control for changing the associated group are displayed. Click this to change the group associated with the current team.

[0089] Delete team control. When the tenant turns on the synchronization of organizational structure, all teams created in the tenant with the synchronization organizational structure cannot be deleted (the delete button is hidden); teams with subordinate teams cannot be deleted; and they cannot be restored after deletion.

[0090] Team administrator settings controls are used to add and delete administrators. When deleting an administrator, if there is only one team administrator left in the enabled state, deleting this administrator is not supported. When clicking delete, the backend will make a judgment. If there is only one enabled state, the deletion will fail, and a prompt will be given that there is only one enabled administrator left and cannot be deleted. When adding a team administrator, first determine the team type; if it is a user type, determine whether the administrator is a team member. If not, remind the current operator to add the team administrator to the team; if it is a department type or group column, remind that the current team type is a department / group. If there is a personnel change in the department / group, the team administrator may not be in the team member list.

[0091] Copy the team control and click to copy the current team ID.

[0092] Team operation record control, which is visible to team administrators and superior team administrators. Each team has an independent set of operation records (as an example, please refer to Figure 3L ). Operation users: user, system (mainly the part that synchronizes the organizational structure). Operation classification, a new first-level module: team; a new second-level operation module under the team, basic information: including the modification of team name, avatar, description, label, and visible range; team personnel: team administrator, team member, modification of related departments / groups; team association: modification of upper and lower teams.

[0093] In some embodiments, the method further includes: recording a predefined event of the team and generating a team operation record; and displaying the team operation record in response to a record viewing operation. Figure 3L , Figure 3L The relevant fields of the operation record can be displayed, such as the operation user, operation module, operation details and operation time.

[0094] Events that need to be recorded in team operation records: team name modification, team avatar modification, team description modification, team tag modification (system operation), team visibility scope modification; team administrator modification, team member modification, associated department / group modification; creating a new subordinate team, applying to associate with a subordinate team, subordinate team agreeing to associate, subordinate team refusing to associate, unbinding a subordinate team; agreeing to associate with a superior team, refusing to associate with a superior team, and unbinding a superior team; exiting a team.

[0095] In this way, team operations can be recorded and a traceability basis can be provided for team management.

[0096] The team member list includes: direct member list and subordinate member list.

[0097] Direct member list: When the team type is member, the member list is displayed; the team administrator can see the edit member control, and the team member can see the exit team control in his own row, and click it to exit the team. If the team type is department group, the name of the associated department is displayed. If the team type is group: the name of the associated group is displayed.

[0098] The subordinate member list shows the composition of the subordinate teams of the team (individuals, groups, departments), and each component element is deduplicated. As an example, in the upper team A, member A is in the subordinate team A1 and the subordinate team A2. In this case, member A is only displayed once in the subordinate member list of the upper team A, and team A1 and team A2 are displayed in the team to which member A belongs. As an example, member A also belongs to department A3, and subordinate team A4 is associated with department A3. In this case, in the subordinate team list of the upper team A, team A1 and A2 to which member A belongs, and team A4 to which department A3 belongs will be displayed. When the subordinate team type is department / group, the department / group is displayed here, and the users of the specific department / group are not displayed.

[0099] In some embodiments, the method further includes: in response to a subordinate team adding instruction, displaying a subordinate team adding interface, wherein the subordinate team adding interface includes a new team creating option and an add existing team option; in response to a selection operation for the new team creating option, creating a new team as a subordinate team of the target team; in response to a selection operation for the add existing team option, selecting an existing team as a subordinate team of the target team.

[0100] In some embodiments, the method also includes at least one of the following: in response to the target user being a team administrator of the target team and the target team being a user type team, displaying a delete control for team members in the team details interface; in response to the target user being a team administrator of the target team, displaying a subordinate team add control in the team details interface; in response to the target user being a team administrator of the target team, displaying an unbinding control for the first-level subordinate team of the target team in the team details interface.

[0101] List of subordinate teams, not visible to team members but visible to team administrators.

[0102] Visible to all subordinate teams (as an example, see Fig. 3I ), click to view all pages of the corresponding subordinate team (with the same permissions as the team administrator). Support unbinding one-level subordinate teams, and send a notification to the subordinate team administrator when unbinding. Cross-level unbinding of associations is not supported. Display the add subordinate team control, click to enter the add subordinate team page; you can add a new team or add an existing team. Click the subordinate team button to jump to the subordinate team details page (default location is the member list page). The team administrator's permissions are the administrator of all subordinate teams by default.

[0103] To create a new team, you need to enter the team name, team type, and team members (the current operator will be automatically set as the team creator and administrator of the new team).

[0104] To add an existing team, you need to enter the team ID, select the team, and then send a notification to the corresponding team administrator. The team will be added to the subordinate team only after the administrator agrees (this notification has no validity period, as long as one administrator agrees, it is agreed). If the current operator is also the administrator of the team being added, it will be automatically approved without sending another notification. When you click Confirm here, you need to verify whether the added team is the parent team or indirect parent team of the current team. If so, it cannot be added and an error will be reported. In other words, a loop cannot be formed here. For special considerations, when the current team is created in the organizational structure synchronization mode, it does not support adding subordinate teams for such teams. Such teams can be associated with other teams as subordinate teams (by adding existing teams.

[0105] The parent team list is visible to both team members and team administrators.

[0106] Team members (as an example, see Figure 3D), all first-level superior teams are visible; when clicking on a superior team, the team homepage visibility of the current user in the corresponding team is verified; the current user is a member or has management authority in the corresponding team: the complete team details page (including user list, superior and subordinate lists, etc.) is visible; the current user has no member / management authority: the team's no-authority page (team basic information and team administrator) is visible.

[0107] Team Admin (as an example, see Figure 3H ), all first-level superior teams are visible; when clicking on a superior team, the team homepage visibility of the current user in the corresponding team is verified. If the current user is a member or has management authority in the corresponding team, the complete team details page (including user list, superior and subordinate lists, etc.) can be seen; if the current user has no member / management authority: the team's no-authority page (team basic information + team administrator) can be seen.

[0108] In some embodiments, the method further includes: displaying, for a work item instance in a project, a team associated with the work item instance.

[0109] As an example, a team is handled as a separate object (such as a work item), and as an example, a team field is added to an instance to associate an instance with a team rather than with a person in the team.

[0110] Thereby, the integrity of personnel management of work item-related teams is improved, and the efficiency of personnel management is improved.

[0111] Please refer to Figure 4 , which shows the process of an embodiment of the project management method according to the present disclosure. This embodiment can be applied to a project management system. Figure 4 The project management method shown includes the following steps:

[0112] Step 401: Display multiple root teams of a target entity in a project management system.

[0113] Here, the root team has subordinate teams, and the intersection between at least two root teams' subordinate teams is not empty.

[0114] In this way, a network team structure can be formed, flexible connections between various sets of personnel can be achieved, and a variety of scenarios in project management can be supported.

[0115] In some embodiments, the method further includes: in a project management system, in response to a team creation instruction for a target entity, displaying a team creation interface; in the team creation interface, displaying multiple team type options; based on the selected team type option, displaying a team member determination interface corresponding to the team type; determining team members based on the team member determination interface, and creating a team for the target entity with the determined team members.

[0116] In some embodiments, the multiple team type options include at least two of the following: associating all or part of the organizational structure to create a department type team; associating a group to create a group type team; selecting user to create a new team to create a user type team.

[0117] In some embodiments, the root team has subordinate teams, and the subordinate teams of the root team at multiple levels are associated with each other according to the superior-subordinate relationship.

[0118] In some embodiments, between teams having a direct or indirect superior-subordinate relationship, the administrator of the superior team has management authority over the subordinate team.

[0119] In some embodiments, the method also includes: displaying a team interface of the target user, wherein the team interface includes a team navigation interface and / or a team details interface; wherein the team navigation interface is used to display the team identification of the team associated with the target user; and the team details interface is used to display relevant information of the target team, wherein the team indicated by the team identification selected in the team navigation interface is the target team.

[0120] In some embodiments, the team navigation interface includes one or more of the following: a first navigation sub-interface and a second navigation sub-interface; wherein the first navigation sub-interface is used to display a first team of which the target user is a direct team member, and subordinate teams of the first team; and the second navigation sub-interface displays a second team of which the target user is a team administrator, and subordinate teams of the second team.

[0121] In some embodiments, the method also includes: in response to the target user being a direct team member of the target team, displaying the team members and superior team of the target team in the team details interface; in response to the target user being a team administrator or superior team administrator of the target team, displaying the team members, superior team and subordinate team of the target team in the team details interface; in response to the target user not being any of the following of the target team: team member, team administrator and superior team administrator, displaying a no-authorization prompt message in the team details interface.

[0122] In some embodiments, the method also includes: in response to the target user being a team administrator or a superior team administrator of the target team, displaying a setting control on the team details interface; in response to a trigger operation on the setting control, displaying at least one of the following: a team setting control, an administrator setting control, a copy team ID control, and a team operation record viewing control.

[0123] In some embodiments, the method also includes at least one of the following: in response to the target user being a team administrator of the target team and the target team being a user type team, displaying a delete control for team members in the team details interface; in response to the target user being a team administrator of the target team, displaying a subordinate team add control in the team details interface; in response to the target user being a team administrator of the target team, displaying an unbinding control for the first-level subordinate team of the target team in the team details interface.

[0124] In some embodiments, the method further includes: in response to a subordinate team adding instruction, displaying a subordinate team adding interface, wherein the subordinate team adding interface includes a new team creating option and an add existing team option; in response to a selection operation for the new team creating option, creating a new team as a subordinate team of the target team; in response to a selection operation for the add existing team option, selecting an existing team as a subordinate team of the target team.

[0125] In some embodiments, the method further includes: recording predefined events of the team and generating a team operation record; and displaying the team operation record in response to a record viewing operation.

[0126] Here, the predefined events include one or more of the following: team name modification, team avatar modification, team description modification, team label modification, team visibility modification, team administrator modification, team member modification, team-associated department modification, team-associated group modification, new subordinate team creation, application for association with subordinate team, subordinate team consent to association, subordinate team refusal to association, unbinding subordinate team, consent to superior team association, refusal to superior team association, superior team unbinding, and exit from team.

[0127] In some embodiments, the method further includes: displaying, for a work item instance in a project, a team associated with the work item instance.

[0128] It should be noted that Figure 4 For the implementation details and technical effects of the illustrated embodiments, please refer to the descriptions in other parts of this application.

[0129] Further references Figure 5 As an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of a project management device, and the device embodiment is Figure 1 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0130] like Figure 5As shown, the project management device of this embodiment includes: a first display unit, used to display a team creation interface in the project management system in response to a team creation instruction for a target entity; a second display unit, used to display a plurality of team type options in the team creation interface; a third display unit, used to display a team member determination interface corresponding to the team type according to the selected team type option; a creation unit, used to determine team members based on the team member determination interface, and to create a team of the target entity with the determined team members.

[0131] In this embodiment, the specific processing of the first display unit 501, the second display unit 502, the third display unit 503 and the creation unit 502 of the project management device and the technical effects brought by them can be referred to respectively. Figure 1 The relevant descriptions of step 101, step 102, step 103 and step 104 in the corresponding embodiment are not repeated here.

[0132] In some embodiments, the multiple team type options include at least two of the following: associating all or part of the organizational structure to create a department type team; associating a group to create a group type team; selecting user to create a new team to create a user type team.

[0133] In some embodiments, the team created for the target entity is the root team of the target entity; and the device is also used to: display multiple root teams of the target entity, wherein the root team has subordinate teams, and the multiple levels of subordinate teams of the root team are associated according to the superior-subordinate relationship.

[0134] In some embodiments, the intersection between the subordinate teams of at least two root teams among the multiple root teams is not empty.

[0135] In some embodiments, between teams having a direct or indirect superior-subordinate relationship, the administrator of the superior team has management authority over the subordinate team.

[0136] In some embodiments, the device is also used to: display a team interface of the target user, wherein the team interface includes a team navigation interface and / or a team details interface; wherein the team navigation interface is used to display the team identification of the team associated with the target user; and the team details interface is used to display relevant information of the target team, wherein the team indicated by the team identification selected in the team navigation interface is the target team.

[0137] In some embodiments, the team navigation interface includes one or more of the following: a first navigation sub-interface and a second navigation sub-interface; wherein the first navigation sub-interface is used to display a first team of which the target user is a direct team member, and subordinate teams of the first team; and the second navigation sub-interface displays a second team of which the target user is a team administrator, and subordinate teams of the second team.

[0138] In some embodiments, the device is also used to: in response to the target user being a direct team member of the target team, display the team members and superior team of the target team in the team details interface; in response to the target user being a team administrator or superior team administrator of the target team, display the team members, superior team and subordinate team of the target team in the team details interface; in response to the target user not being any of the following of the target team: team member, team administrator and superior team administrator, display an unauthorized prompt message in the team details interface.

[0139] In some embodiments, the device is also used to: in response to the target user being the team administrator or the superior team administrator of the target team, display the setting control on the team details interface; in response to the trigger operation on the setting control, display at least one of the following: team setting control, administrator setting control, copy team ID control, team operation record viewing control.

[0140] In some embodiments, the device is also used for at least one of the following: in response to the target user being a team administrator of the target team and the target team being a user type team, displaying a delete control for team members in the team details interface; in response to the target user being a team administrator of the target team, displaying a subordinate team add control in the team details interface; in response to the target user being a team administrator of the target team, displaying an unbinding control for the first-level subordinate team of the target team in the team details interface.

[0141] In some embodiments, the device is also used to: in response to a subordinate team adding instruction, display a subordinate team adding interface, wherein the subordinate team adding interface includes a new team option and an add existing team option; in response to a selection operation for the new team option, create a new team as a subordinate team of the target team; in response to a selection operation for the add existing team option, select an existing team as a subordinate team of the target team.

[0142] In some embodiments, the device is also used to: record predefined events of the team and generate team operation records; and display the team operation records in response to a record viewing operation.

[0143] Here, the predefined events include one or more of the following: team name modification, team avatar modification, team description modification, team label modification, team visibility modification, team administrator modification, team member modification, team-associated department modification, team-associated group modification, new subordinate team creation, application for association with subordinate team, subordinate team consent to association, subordinate team refusal to association, unbinding subordinate team, consent to superior team association, refusal to superior team association, superior team unbinding, and exit from team.

[0144] In some embodiments, the apparatus is further configured to: for a work item instance in a project, display a team associated with the work item instance.

[0145] Please refer to Figure 6 , Figure 6 An exemplary system architecture is shown in which the project management method according to one embodiment of the present disclosure can be applied.

[0146] like Figure 6 As shown, the system architecture may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 is used to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. The network 604 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0147] The terminal devices 601, 602, and 603 can interact with the server 605 through the network 604 to receive or send messages, etc. Various client applications, such as web browser applications, search applications, and news information applications, can be installed on the terminal devices 601, 602, and 603. The client applications in the terminal devices 601, 602, and 603 can receive user instructions and perform corresponding functions according to the user instructions, such as adding corresponding information to the information according to the user instructions.

[0148] Terminal devices 601, 602, and 603 can be hardware or software. When terminal devices 601, 602, and 603 are hardware, they can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, Moving Picture Experts Group Audio Layer 3), MP4 (Moving Picture Experts Group Audio Layer IV, Moving Picture Experts Group Audio Layer 4) players, laptop computers, and desktop computers, etc. When terminal devices 601, 602, and 603 are software, they can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules (for example, software or software modules used to provide distributed services), or it can be implemented as a single software or software module. No specific limitation is made here.

[0149] The server 605 may be a server that provides various services, such as receiving information acquisition requests sent by the terminal devices 601, 602, and 603, and acquiring display information corresponding to the information acquisition requests in various ways according to the information acquisition requests. The relevant data of the display information is sent to the terminal devices 601, 602, and 603.

[0150] It should be noted that the project management method provided in the embodiment of the present disclosure can be executed by a terminal device, and accordingly, the project management device can be set in the terminal devices 601, 602, and 603. In addition, the project management method provided in the embodiment of the present disclosure can also be executed by a server 605, and accordingly, the project management device can be set in the server 605.

[0151] It should be understood that Figure 6 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0152] Reference below Figure 7 , which shows an electronic device (eg, Figure 6 The terminal device in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0153] like Figure 7 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the electronic device 700 are also stored. The processing device 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0154] Typically, the following devices may be connected to the I / O interface 705: input devices 706 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 707 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 708 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 709. The communication devices 709 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although Figure 7 An electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0155] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 709, or installed from a storage device 708, or installed from a ROM 702. When the computer program is executed by the processing device 701, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0156] It should be noted that the computer-readable medium disclosed above 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, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0157] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0158] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0159] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: in the project management system, in response to a team creation instruction for a target entity, displays a team creation interface; in the team creation interface, displays multiple team type options; based on the selected team type option, displays a team member determination interface corresponding to the team type; determines team members based on the team member determination interface, and creates a team of the target entity with the determined team members.

[0160] 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 multiple root teams of the target entity in the project management system; wherein the root team has subordinate teams, and the intersection between the subordinate teams of at least two root teams is not empty.

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

[0162] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0163] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, a verification unit may also be described as a "unit for determining whether the target value passes verification".

[0164] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

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

[0166] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other.

[0167] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0168] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

Claims

1. A project management method, the method comprising: In a project management system, in response to a team creation instruction for a target entity, a team creation interface is displayed; In the team creation interface, multiple team type options are displayed; According to the selected team type option, the team member confirmation interface corresponding to the team type is displayed; The team members are determined based on a team member determination interface, and a team of the target entity is created with the determined team members.

2. The method according to claim 1, characterized in that: The multiple team type options include at least two of the following: Associate all or part of the organizational structure to create department-type teams; Associated groups, used to create group-type teams; Select User New to create a team of user type.

3. The method according to claim 1, characterized in that The team created for the target entity is the root team of the target entity; as well as The method further comprises: Displays multiple root teams of the target entity, where: The root team has subordinate teams, and the multiple levels of subordinate teams of the root team are associated with each other based on the superior-subordinate relationship.

4. The method according to claim 3, characterized in that The intersection between the subordinate teams of at least two root teams among the multiple root teams is not empty.

5. The method according to claim 3, characterized in that: Between teams with direct or indirect superior-subordinate relationships, the administrator of the superior team has the management authority over the subordinate team.

6. The method according to claim 1, characterized in that The method further comprises: Displaying a team interface of a target user, wherein the team interface includes a team navigation interface and / or a team details interface; Among them, the team navigation interface is used to display the team logo of the team associated with the target user; The team details interface is used to display relevant information of the target team, wherein the team indicated by the team logo selected in the team navigation interface is the target team.

7. The method according to claim 6, characterized in that The team navigation interface includes one or more of the following: a first navigation sub-interface and a second navigation sub-interface; in The first navigation sub-interface is used to display the first team of which the target user is a direct team member, and the subordinate teams of the first team; The second navigation sub-interface displays the second team whose target user is the team administrator, and subordinate teams of the second team.

8. The method according to claim 6, characterized in that The method further comprises: In response to the target user being a direct team member of the target team, displaying the team members and parent team of the target team on the team details interface; In response to the target user being a team administrator or a superior team administrator of the target team, displaying team members, superior teams, and subordinate teams of the target team on the team details interface; In response to the target user not being any of the following members of the target team: team member, team administrator, and superior team administrator, a no-authorization prompt message is displayed on the team details interface.

9. The method according to claim 6, characterized in that The method further comprises: In response to the target user being a team administrator or a superior team administrator of the target team, displaying a setting control on the team details interface; In response to a trigger operation on a setting control, at least one of the following is displayed: a team setting control, an administrator setting control, a copy team ID control, and a team operation record viewing control.

10. The method according to claim 6, characterized in that The method further comprises at least one of the following: In response to the target user being a team administrator of the target team and the target team being a user type team, displaying a delete control for the team member in the team details interface; In response to the target user being a team administrator of the target team, displaying a subordinate team adding control in the team details interface; In response to the target user being a team administrator of the target team, an unbinding control is displayed for the first-level subordinate teams of the target team in the team details interface.

11. The method according to claim 11, characterized in that: The method further comprises: In response to the subordinate team adding instruction, displaying the subordinate team adding interface, wherein the subordinate team adding interface includes a new team creation option and an existing team addition option; In response to a selection operation on a new team option, the new team is created as a subordinate team of the target team; In response to a selection operation on the option of adding an existing team, an existing team is selected as a subordinate team of the target team.

12. The method according to claim 1, characterized in that The method further comprises: Record the team's predefined events and generate team operation records; In response to a record viewing operation, displaying the team operation record; Among them, the predefined events include one or more of the following: team name modification, team avatar modification, team description modification, team label modification, team visibility modification, team administrator modification, team member modification, team-associated department modification, team-associated group modification, new subordinate team creation, application for association with subordinate team, subordinate team consent to association, subordinate team refusal to association, unbinding subordinate team, consent to superior team association, refusal to superior team association, superior team unbinding, and exit from team.

13. The method according to claim 1, characterized in that The method further comprises: For work item instances in a project, displays the teams associated with the work item instances.

14. A project management method, the method comprising: In a project management system, multiple root teams of target entities are displayed; Among them, the root team has subordinate teams, and the intersection between the subordinate teams of at least two root teams is not empty.

15. A project management device, comprising: A first display unit is used to display a team creation interface in the project management system in response to a team creation instruction for a target entity; The second display unit is used to display multiple team type options in the team creation interface; The third display unit is used to display a team member determination interface corresponding to the team type according to the selected team type option; The creation unit is used to determine team members based on a team member determination interface, and to create a team of a target entity with the determined team members.

16. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 14.

17. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 14 is implemented.

Images