Task processing method, device, equipment and product

Abstract

The invention relates to a task processing method and device, equipment and a product. The method includes generating a suggestion to create a first task based on information of at least one data source associated with the first task. And generating the first task based on the information associated with the first task and the first task template in response to feedback of the user for the suggestion for creating the first task. Through the method, the user experience and the working efficiency are improved.

Description

Technical Field

[0001] This disclosure generally relates to the field of computers, and more specifically to methods, apparatus, devices, and computer program products for processing tasks. Background Technology

[0002] Regarding information retrieval and collaboration across data sources / products / platforms, the industry generally adopts a method of aggregating events and content from different systems into actionable items. For example, some products access multiple information sources, extract information according to unified permissions, and periodically update the information. Users then extract usable information through structured indexes and semantic searches. Users further configure rules to create tasks based on the extracted usable information. Summary of the Invention

[0003] In embodiments of this disclosure, a method, apparatus, electronic device, and computer program product for processing tasks are provided.

[0004] In a first aspect of this disclosure, a method for processing a task is provided. The method includes generating a suggestion to create a first task based on information associated with the first task from at least one data source. The method also includes generating the first task based on information associated with the first task and a first task template in response to user feedback regarding the suggestion to create the first task.

[0005] In a second aspect of this disclosure, an electronic device is provided. The electronic device includes a first generation module configured to generate a suggestion for creating a first task based on information associated with a first task from at least one data source. The electronic device also includes a second generation module configured to generate the first task based on information associated with the first task and a first task template in response to user feedback on the suggestion for creating the first task.

[0006] In a third aspect of this disclosure, an electronic device is provided. The electronic device includes a processor. The electronic device also includes a memory coupled to the processor, the memory having instructions stored therein, which, when executed by the processor, cause the electronic device to perform the method according to a first aspect of this disclosure.

[0007] In a fourth aspect of this disclosure, a computer program product is provided, comprising computer-executable instructions, wherein the computer-executable instructions are executed by a processor to implement the method according to a first aspect of this disclosure.

[0008] In a fifth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores computer-executable instructions, which are executed by a processor to implement the method according to the first aspect.

[0009] The summary section is intended to present the chosen concepts in a simplified form, which will be further described in the detailed description below. The summary section is not intended to identify key or principal features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Attached Figure Description

[0010] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0011] Figure 1 A schematic diagram is shown illustrating an example environment in which one or more embodiments of the present disclosure may be implemented;

[0012] Figure 2 Flowcharts of methods for processing tasks according to some embodiments of this disclosure are shown;

[0013] Figure 3 Detailed block diagrams of a task processing module according to some embodiments of the present disclosure are shown;

[0014] Figure 4 A schematic diagram of a task generated according to some embodiments of the present disclosure is shown;

[0015] Figure 5 A schematic block diagram of a product demand platform for invoking a task processing module according to some embodiments of the present disclosure is shown;

[0016] Figure 6 A schematic diagram illustrating a defect or requirement details page of a product requirement platform according to one or more embodiments of this disclosure is shown;

[0017] Figure 7 A schematic block diagram of a code library platform for calling task processing modules according to some embodiments of the present disclosure is shown;

[0018] Figure 8 A low-level logic block diagram of the workbench of a task processing module or platform according to some embodiments of the present disclosure is shown;

[0019] Figure 9 A schematic block diagram of an electronic device for processing tasks according to some embodiments of the present disclosure is shown; and

[0020] Figure 10 A schematic block diagram of an electronic device according to some embodiments of the present disclosure is shown.

[0021] In all the accompanying figures, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0022] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0023] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0024] For example, upon receiving a user's proactive request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0025] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0026] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0027] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0028] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc., may refer to different or the same objects unless explicitly stated. Other explicit and implicit definitions may also be included below.

[0029] As mentioned above, regarding cross-product / platform information retrieval and linkage, the industry generally adopts the approach of aggregating events and content from different systems into actionable items. However, these solutions all suffer from the problem of requiring users to fill in a large number of task parameters. Furthermore, these solutions can only process related tasks on their own application platforms and cannot extend their capabilities to other platforms or other applications.

[0030] Therefore, one or more embodiments of this disclosure adopt an alternative approach to achieve proactive connection between information and actions on the workbench. This involves automatically generating consumable insights and feasible actions based on the information sources already accessed by the user, supporting one-click task initiation and parameter pre-filling. Furthermore, one or more embodiments of this disclosure can achieve bidirectional communication with the task processing module or platform, significantly reducing initiation costs and context switching costs. On another front, one or more embodiments of this disclosure lower the cold start and usage threshold by providing a task suggestion entry point on the workbench, reducing the steps and time required for users to configure and execute tasks for the first time, and minimizing user experience degradation caused by needing to remember and manually input relevant task parameters.

[0031] Therefore, one or more embodiments of this disclosure provide a scheme for processing a task. The scheme includes generating a suggestion to create a first task based on information associated with a first task from at least one data source. The scheme also includes generating a first task based on information associated with the first task and a first task template in response to user feedback on the suggestion to create the first task.

[0032] In this way, one or more embodiments of this disclosure achieve proactive connection between information and action on the workbench, that is, automatically generate consumable insights and feasible operations around the information sources already accessed by the user, supporting one-click task initiation and parameter pre-filling. Furthermore, one or more embodiments of this disclosure can achieve bidirectional communication with the task processing module or platform, significantly reducing initiation costs and context switching costs. Additionally, one or more embodiments of this disclosure lower the cold start and usage threshold by providing a task suggestion entry point on the workbench, reducing the steps and time required for users to configure and execute tasks for the first time, and reducing user experience degradation caused by having to remember relevant task parameters and manually input them, thereby greatly improving user experience and work efficiency, and enabling timely completion of relevant tasks.

[0033] Figure 1 A schematic diagram of an example environment 100 in which one or more embodiments of the present disclosure may be implemented is shown. Figure 1As shown, environment 100 includes processing device 102. Processing device 102 can be any device with processing capabilities. For example, processing device 102 can include smartphones, tablets, laptops, desktop computers, workstations, quantum computers, or smart wearable devices. In environment 100, processing device 102 can run application 104, which can be a machine learning model application or an artificial intelligence (AI) application. User 108 can interact with application 104 through processing device 102. In application 104, the user can use relevant information from platforms 110, 112, or 114 to create tasks or complete related tasks, such as completing requirements assessments, product design, code writing, or project management. For example, application 104 can also be a machine learning model application platform or an artificial intelligence application platform. Platforms 110, 112, or 114 can be at least one of a product requirements platform, a code repository platform, an instant messaging platform, a product development task platform, etc. Application 104 may include a task processing module 106 according to one or more embodiments of this disclosure. The task processing module 106 can generate task creation suggestions based on interaction with the user 108, and automatically generate tasks based on task templates according to the user's feedback on the task creation suggestions. Since the task processing module 106 can simultaneously complete task suggestion and automatic task generation, the user 108 reduces the steps and time required for initial task configuration and execution, minimizing user experience degradation caused by needing to remember and manually input relevant task parameters. This significantly improves user experience and work efficiency, enabling timely task completion. Furthermore, the task processing module 106 can also function as an independent application or application platform, rather than simply being a task processing module within application 104.

[0034] It should be understood that, for the sake of brevity, Figure 1 This document only shows a specific number of processing devices 102, applications 104, task processing modules 106, and platforms 110, 112, or 114, etc., but it is not intended to limit the number of processing devices 102, applications 104, task processing modules 106, and platforms 110, 112, or 114, etc., as applicable to this disclosure. In other implementations, any number of processing devices 102, applications 104, task processing modules 106, and platforms 110, 112, or 114, etc., applicable to this disclosure may be used. For example, processing device 102 may also be a cloud computing platform, etc.

[0035] In this way, the environment 100 containing the task processing module 106 implemented in one or more embodiments of this disclosure achieves proactive connection from information to action on the workbench, that is, automatically generates consumable insights and feasible operations around the information sources already accessed by the user, supporting one-click task initiation and parameter pre-filling. Furthermore, the environment 100 containing the task processing module 106 implemented in one or more embodiments of this disclosure can achieve bidirectional communication with the task processing module or platform, significantly reducing initiation costs and context switching costs. Additionally, the environment 100 containing the task processing module 106 implemented in one or more embodiments of this disclosure lowers the cold start and usage threshold by providing a task suggestion entry on the workbench, reducing the steps and time required for users to configure and execute tasks for the first time, and reducing user experience degradation caused by needing to remember relevant task parameters and manually input them, thereby greatly improving user experience and work efficiency, and enabling timely completion of relevant tasks.

[0036] The following will combine Figures 2 to 10 The process according to embodiments of this disclosure is described in detail. For ease of understanding, the specific data mentioned in the following description are exemplary and not intended to limit the scope of this disclosure. It should be understood that the embodiments described below may also include additional actions not shown and / or actions shown may be omitted, and the scope of this disclosure is not limited in this respect.

[0037] Figure 2 A flowchart illustrating a method 200 for processing a task according to some embodiments of the present disclosure is shown. Method 200 can be executed by a processing device. For example, method 200 can be performed by… Figure 1 The processing device 102 performs the operation. The processing device may include, for example, a smartphone, tablet computer, laptop computer, desktop computer, workstation, quantum computer, cloud computing platform, or smart wearable device.

[0038] In block 202, a suggestion to create a first task is generated based on information associated with a first task from at least one data source. In some embodiments, the at least one data source may be at least one platform (e.g., platform 110, 112, or 114, etc.). In some embodiments, method 200 may further include obtaining a first task template, and based on the first task template, parsing the page associated with the first task from at least one data source, and obtaining information associated with the first task based on the parsed page associated with the first task from at least one data source. In some embodiments, the page associated with the first task from at least one data source is the current page of at least one data source. In some embodiments, generating a suggestion to create a first task based on information associated with the first task from at least one data source may further include determining the permissions of a user (e.g., user 108), and determining the information associated with the first task from the first data source based on the user's permissions. In some embodiments, generating a suggestion to create a first task based on information associated with the first task from at least one data source may further include determining team-shared information in the information associated with the first task from the first data source. In some embodiments, generating a suggestion to create a first task based on information associated with the first task from at least one data source includes at least one of the following: generating a suggestion to initiate the first task based on information associated with the first task from the first data source; or generating an execution suggestion to initiate the first task and how to execute the first task based on information associated with the first task from the first data source.

[0039] In some embodiments, the information associated with the first task includes at least one of the following: task requirement identifier, task title, task content description, task start time or end time, task owner, task participants, task type, current task node, task status, task associated resources, code repository information, code repository merge request information, code author information, code reviewer information, code repository status, code repository change file list, current stage information of development task, or upstream and downstream related information of development task.

[0040] In box 204, in response to user feedback regarding suggestions for creating a first task, a first task is generated based on information associated with the first task and a first task template. In some embodiments, method 200 may further include sending the first task to a processing entity, receiving a first result from the processing entity executing the first task, and generating a second task based on the confirmed first result and a second task template associated with the confirmed first result in response to user confirmation of the first result. In some embodiments, the processing entity may be a proxy. In some embodiments, the processing entity may be a machine learning model proxy. In some embodiments, method 200 may further include obtaining a second task template, parsing a page associated with the second task from at least one data source based on the second task template, and obtaining information associated with the second task based on the parsed page associated with the second task from at least one data source. In some embodiments, generating a second task based on the confirmed first result and the second task template associated with the confirmed first result may include sending the confirmed first result and the second task template associated with the confirmed first result to the processing entity in response to receiving a user request to generate a second task, and receiving the second task generated by the processing entity based on the confirmed first result and the second task template associated with the confirmed first result. In some embodiments, method 200 may further include sending a second task to a first data source in at least one data source to perform the second task based on the first data source, and receiving a second result from the first data source performing the second task. In some embodiments, method 200 may further include generating a third task in response to user confirmation of the second result, based on the confirmed second result and a second task template associated with the confirmed second result.

[0041] In some embodiments, method 200 may further include classifying tasks from at least one data source, and determining corresponding triggering rules and display styles for the classified tasks based on the classified tasks from at least one data source. In some embodiments, determining the corresponding triggering rules and display styles for the classified tasks from at least one data source may include determining information about the classified tasks to be displayed, determining a task template associated with the classified tasks, or, in response to the absence of a task template associated with the classified tasks, determining reference information to provide to the user when initiating a task. In some embodiments, determining the reference information to provide to the user when initiating a task may include generating task requirement instructions based on the content description of the classified tasks, the current node of the classified tasks, the user's role, or the task objective, for the user to refer to when initiating a task. In some embodiments, each of the at least one data source may have a corresponding task configuration page. In some embodiments, the at least one data source includes at least one of a product requirement platform, a code repository platform, an instant messaging platform, or a product development task platform.

[0042] In this way, one or more embodiments of method 200 achieve proactive connection between information and action on the workbench, that is, automatically generate consumable insights and feasible operations around the information sources already accessed by the user, supporting one-click task initiation and parameter pre-filling. Furthermore, one or more embodiments of method 200 can achieve bidirectional communication with the task processing module or platform, significantly reducing initiation costs and context switching costs. Additionally, one or more embodiments of method 200 lower the cold start and usage threshold by providing a task suggestion entry point on the workbench, reducing the steps and time required for users to configure and execute tasks for the first time, and reducing user experience degradation caused by having to remember relevant task parameters and manually input them, thereby significantly improving user experience and work efficiency, and enabling timely completion of relevant tasks.

[0043] Furthermore, one or more embodiments of Method 200 establish a bidirectional link between the workbench component and the platform. This means that tasks can be initiated through workbench components (e.g., insight reports / attention events), and the task results / status can be consumed within the project space, forming a closed-loop task process. Additionally, one or more embodiments of Method 200 improve task parameter passing and context mapping. When entering the task processing module from various platforms or initiating a task within the task processing module, they support context parsing and parameter pre-filling of task templates, reducing the need for secondary parameter filling and manual information mining. Furthermore, one or more embodiments of Method 200 enhance team collaboration and the result chain by consuming task results as outputs of the project space and supporting the ability to link results to subsequent steps, thus improving collaboration efficiency. Moreover, one or more embodiments of Method 200 ensure permission consistency and context following. By following the currently logged-in user's permissions during task triggering and linkage, they ensure technical consistency between information visibility and operational permissions, and effectively notify and avoid users of unauthorized information, thereby significantly improving the user experience.

[0044] Figure 3 A detailed block diagram of a task processing module 300 according to some embodiments of the present disclosure is shown. The task processing module 300 includes a task processing main interface 301. The task processing main interface 301 includes a text input box 303 for receiving task prompts from the user. The task processing main interface 301 also includes a recommended task control 305 and a task template control 307. In some embodiments, the recommended task control 305 can generate suggestions for creating a first task based on information associated with a first task from at least one data source. In some embodiments, the task processing module 300 defines a unified information source access and processing layer, designed to standardize the processing of heterogeneous information from different products and platforms as data input for associated tasks. All information entry strictly follows the principle that permissions follow the currently logged-in user, and supports users setting permissions to globally public information during configuration, allowing space members to share information sources. In some embodiments, the task processing module 300 only retrieves and processes resources that the currently logged-in user has access to, such as documents, calendar events, chat logs, etc., under their personal name. This is the basic permission constraint for all data reading. In some embodiments, users with administrator privileges can centrally bind team-shared resources, such as code repositories and project management platform data, in the resource configuration module (not shown) of the project space. This configuration serves only as an index entry point for resources; actual access still requires verification of the current user's personal permissions. In some embodiments, when accessing a resource, the task processing module 300 can first check whether the resource belongs to the shared resources configured in the space. If so, it further verifies whether the current user has personal access permissions to the resource. Access to the resource is only allowed if both conditions are met.

[0045] In some embodiments, the task suggestion control 305 can generate task creation suggestions 309 or 313, etc. Task creation suggestions 309 or 313 may include a description of the task, or related information about the task to be created. In some embodiments, task creation suggestions 309 or 313 may include a task creation control 311, etc. If a user wishes to create the task, they can click the task creation control 311, etc., and the task processing module 300, in response to the user's feedback on the task creation suggestion, generates the relevant task based on the information associated with the task and the task template.

[0046] In some embodiments, the task template control 307 can be used to generate or manage related task templates. In some embodiments, the task templates may be designed or created by a service provider. In some embodiments, the task templates may also be designed or created by a user. In some embodiments, related task templates may be associated with related tasks. In some embodiments, related task templates may be associated with related platforms or related events on related platforms. Users can configure related settings through a settings module (not shown).

[0047] Figure 4 A schematic diagram of a task 400 generated according to some embodiments of the present disclosure is shown. Task 400 illustrates a generated Product Requirements Document (PRD) review task. Task 400 includes a task main interface 401. In some embodiments, the task main interface 401 may include a requirement instruction 403. The requirement instruction 403 indicates the specific content 405 of the requirement instruction. In some embodiments, the task main interface 401 may also include custom task information 407. The custom task information 407 indicates, for example, a PRD document link 409, which in turn indicates a specific link 411. In some embodiments, the specific content 405 of the requirement instruction 403 may be generated by a processing entity based on relevant information. In some embodiments, the specific link 411 of the PRD document link 409 may be automatically populated, thereby greatly reducing the burden on the user. In some embodiments, the user can check whether the generated task 400 meets their needs. If it does, the user can click the send control 413 to send the task 400 to the appropriate node. In some embodiments, the task 400 may be sent to different platforms for other users to complete the PRD review task. In some embodiments, even the initial review can be performed by a processing entity. In some embodiments, task 400 can be generated based on a preset PRD review task template.

[0048] In this way, one or more embodiments of the task processing module 300 proactively connect information to actions on the workbench, automatically generating consumable insights and feasible actions based on the information sources already accessed by the user, supporting one-click task initiation and parameter pre-filling. Furthermore, one or more embodiments of the task processing module 300 can achieve bidirectional communication with other task processing modules or platforms, significantly reducing initiation costs and context switching costs. Additionally, one or more embodiments of the task processing module 300 lower the cold start and usage threshold by providing task suggestion entry points on the workbench, reducing the steps and time required for users to configure and execute tasks for the first time, and minimizing user experience degradation caused by needing to remember and manually input relevant task parameters, thereby greatly improving user experience and work efficiency, and enabling timely completion of related tasks.

[0049] Figure 5 A schematic block diagram of a product requirement platform 500 for invoking a task processing module according to some embodiments of the present disclosure is shown. One or more embodiments of the present disclosure define a strategy for bidirectional communication with multiple work platforms, enabling not only the consumption of information from these platforms within the task processing module or platform, but also cross-platform updates of target task status based on core information. Furthermore, it allows direct triggering of task processing module functions across multiple platforms, achieving seamless workflow linkage. In some embodiments, an entry point for invoking the task processing module can be embedded in the user interface of the target platform (e.g., product requirement platform, code repository platform, instant messaging platform, product development task platform, etc.), allowing users to directly invoke the task template capabilities of the task processing module in the current context, thereby enabling one-click task initiation.

[0050] exist Figure 5 In this context, the product requirement platform 500 may include a main interface 501 that invokes the task processing module for test case design or review tasks. In some embodiments, the main interface 501 may include controls 503 for submitting generated tasks to the task processing module. In some embodiments, the main interface 501 may include a task sending object 505, for example, indicating whether the task can be sent to a requirement group 507 or the task triggerer 509, etc. In some embodiments, the task sending object 505 may include temporarily not sending the task 511. Users can also select a task template by using a task template 515 indicated by a trigger template 513.

[0051] In some embodiments, the main interface 501 may include task parameters 519 indicated by default parameter 517. In some embodiments, this disclosure may provide an automatic parameter pre-filling function, that is, when a task is initiated from the platform side, the system automatically parses the context of the current page (e.g., task requirement identifier (ID), codebase merge request (Codebase MR) information) and pre-fills it as parameters into the task template selected by the user, thereby greatly reducing the user's manual input cost. In some embodiments, this disclosure adopts the permission-following principle, that is, all cross-platform read and write operations strictly follow the permissions of the currently logged-in user, thereby preventing unauthorized behavior.

[0052] In some embodiments, a task processing module entry is embedded in the defect or requirement details page of the product requirement platform 500. This allows for reverse navigation from the platform where the task processing module is located to the product requirement platform 500. Figure 6 A schematic diagram of a defect or requirement details page 600 of a product requirement platform 500 according to one or more embodiments of the present disclosure is shown. In some embodiments, the defect or requirement details page 600 may include a main interface 601. In some embodiments, the main interface 601 may include a search box 603 for searching requirement or defect tasks. In some embodiments, the main interface 601 may also include various creation task suggestions 605, 607, 609, or 611 generated by the task processing module for determining defects or requirements. In some embodiments, creation task suggestions 605, 607, 609, or 611 may include a creation task control 613 for initiating a creation task. In some embodiments, the embedded task processing module can automatically extract key field information such as project space, type, ID, current node, responsible person, status, and associated resources by parsing the URL of the product requirement platform 500, thereby achieving intelligent pre-filling of template parameters. In some embodiments, the task processing module or platform filters out entries where "current node responsible person = current user" by default, pre-refining or summarizing target concerns.

[0053] In this way, one or more embodiments of the product requirement platform 500 of the task processing module can be invoked to proactively connect information to actions on the workbench. This means automatically generating consumable insights and feasible actions based on the information sources already accessed by the user, supporting one-click task initiation and parameter pre-filling. Furthermore, one or more embodiments of the product requirement platform 500 of the task processing module can achieve bidirectional communication with the task processing module or platform, significantly reducing initiation costs and context switching costs. Additionally, by lowering the cold start and usage threshold, and providing a task suggestion entry point on the workbench, one or more embodiments of the product requirement platform 500 of the task processing module reduce the steps and time required for users to configure and execute tasks for the first time, minimizing user experience degradation caused by needing to remember and manually input relevant task parameters. This greatly improves user experience and work efficiency, enabling timely task completion.

[0054] In some embodiments, this disclosure may also embed a task processing module implemented according to one or more embodiments of this disclosure into an instant messaging platform. For example, a task processing module entry point may be embedded in the "To-do" details page of the instant messaging platform. In some embodiments, this disclosure may automatically extract the title, description, deadline, and participants of a task through the task processing module for pre-populating associated task templates. In some embodiments, task execution suggestions may be generated based on this information in the "Insight Report" page of the instant messaging platform.

[0055] In some embodiments, this disclosure may also embed task processing modules implemented according to one or more embodiments of this disclosure into the code repository platform. For example, this disclosure may embed entry points such as "automated review," "generate modification suggestions," or "respond to comments" based on task processing modules into the merge request page of the code repository. Figure 7 A schematic block diagram of a codebase platform 700 for calling a task processing module according to some embodiments of the present disclosure is shown. Figure 7 In this system, the code repository platform 700 may include a main interface 701 for invoking a task processing module. In some embodiments, the main interface 701 may include a task processing module 705 indicating the invocation and may display the invocation time 707. In some embodiments, the main interface 701 may also include a control 709 for indicating a code problem description, a control 711 for displaying the processing priority of the code problem, and a control 713 for displaying improved code examples. In some embodiments, the main interface 701 may also include a response control 715 for addressing code problems and their processing results. In some embodiments, the main interface 701 may also include a marking control 717 for marking code problems as unresolved, etc.

[0056] In some embodiments, the code repository platform 700 can pre-populate information such as repository, MR ID, branch, author, reviewer, status, and change file list by calling the task processing module. In some embodiments, the code repository platform 700 can also support different perspectives such as "awaiting my review" and "my submitted merge request" by calling the task processing module, and perform code review comments write-back according to user permissions.

[0057] In some embodiments, the product development task platform can also provide entry points for triggering the task processing module (e.g., "generate test points," "assess release risks") by calling the task processing module around different stages of the development task (e.g., development, merging, testing, release). In some embodiments, the product development task platform can also pre-populate task IDs, types, current stages, statuses, and upstream / downstream related information by calling the task processing module. In some embodiments, users can see tasks related to themselves by default, while administrators can see an aggregated data view of the entire space.

[0058] In this way, one or more embodiments of the task processing module's instant messaging platform, code repository platform 700, or product development task platform can be invoked to proactively connect information to actions on the workbench. This means automatically generating consumable insights and feasible actions based on the user's accessed information sources, supporting one-click task initiation and parameter pre-filling. Furthermore, one or more embodiments of the task processing module's instant messaging platform, code repository platform 700, or product development task platform can achieve bidirectional communication with the task processing module or platform, significantly reducing initiation costs and context switching costs. Additionally, by lowering the cold start and usage threshold—providing task suggestion entry points on the workbench—the steps and time required for initial task configuration and execution are reduced, minimizing user experience degradation caused by remembering and manually entering task parameters. This greatly improves user experience and work efficiency, enabling timely task completion.

[0059] Figure 8 A low-level logical block diagram of a task processing module or platform workbench 800 according to some embodiments of this disclosure is shown. The system categorizes events by platform (e.g., product requirement platform, code repository platform, instant messaging platform, product development task platform, etc.) and defines corresponding triggering rules and display styles for each event type. Figure 8As shown, in some embodiments, third-party information sources 801 include information from sources such as the web 803, and also information from third-party platforms 805, such as product development platforms or code repository platforms. This information can be provided to components 809 of the workbench 800. In some embodiments, component 809 may include components of type insight report or event list 811, for example, those pre-configured by a vendor or configured by an administrator. In some embodiments, component 809 may also originate from space component library 813 or component instance 815, etc. In some embodiments, the corresponding space component library 813 may be provided or supplemented by (work) space 817, for example, for a project or individual 819. In some embodiments, space 817 provides support to users, for example, users who are administrators or general members 823. In some embodiments, space 817 may also provide, for example, a pre-configured dashboard 825, pre-configured by the system or administrator (827). In some embodiments, component 809 may also include pre-configured dashboard 825, etc. In some embodiments, user 821 may also set up personal dashboard 829 by pre-configuration or customization (831). The underlying logic diagram of Workbench 800 ensures effective management of the information flow and information usage control of the task processing module or platform. Each element in Workbench 800 can have a one-to-one (1:1), one-to-many (1:n), or many-to-one (n:1) correspondence or mapping relationship, which will not be elaborated upon here to save space.

[0060] In some embodiments, each platform or platform event can have an independent configuration page, where administrators can configure the information to be displayed by default in the configuration cards, as well as the task template associated when clicking "Initiate Task". If no associated template is configured, the platform will pre-draft requirement instructions based on the event description, current node, user role, and core work objectives of the event of interest, and actively fill them into the main input box for users to refer to when initiating tasks. In some embodiments, this disclosure can provide cross-platform automated task flow. For example, task results generated through "one-click initiation" on other platforms can be automatically collected and indexed based on a cross-platform "associated event" index. After users adopt the AI ​​agent's execution results, they can quickly locate, confirm, and transfer the status on the platform, and start the next step of work, thereby connecting various work stages.

[0061] In summary, one or more embodiments of this disclosure provide a one-click task initiation and intelligent parameter pre-filling interface for bidirectional platform connectivity. For example, an entry point for a "one-click task initiation module" can be embedded in platforms such as product requirement platforms, code repository platforms, instant messaging platforms, and product development task platforms. This automatically parses the current page context and intelligently pre-fills parameters such as project / resource identifiers and node status into the template. The results on the workbench side support reverse redirection to the source platform to form a closed loop.

[0062] Furthermore, one or more embodiments of this disclosure provide constraint / implementation methods. For example, they define context resolution mappings by platform (e.g., project space / type / ID / current node / responsible person / status in a product requirements platform; repository / MR ID / branch / author / reviewer / change file list in a code repository platform), and in the event of pre-population failure, they can provide an initial query for the user to manually complete the data, and all calls and write-backs follow individual permissions.

[0063] Furthermore, one or more embodiments of this disclosure implement a unified trigger bus (time-driven / event-driven / manual-driven) scheduling incremental data collection. For example, triggers such as "periodic tasks (daily / weekly)," "platform events (Webhook / polling)," and "user clicks to initiate one-click events" are uniformly accessed through the scheduling layer, and incremental data is retrieved according to the trigger type and entered into a standardized processing link. One or more embodiments of this disclosure also provide constraints / implementation conditions and methods. For example, event-driven events need to access the polling interface provided by the platform and perform incremental judgment; time-driven events are executed according to the configured cycle; and manual-driven events originate from the workbench interaction entry point, and still follow the unified information collection and verification process after triggering.

[0064] On the other hand, one or more embodiments of this disclosure also provide a card-based configuration and template linkage mechanism for the "Events of Interest" component. For example, event types are categorized by platform, and cards are configured with independent display fields and triggering rules. Each event can be bound to a related task template for one-click initiation; if no template is bound, the system automatically generates an initial query for pre-filling based on the current content / status. One or more embodiments of this disclosure also provide constraints / implementation conditions or methods. For example, the component display only includes entries related to the currently logged-in user, template binding is maintained on the configuration page and can be hot-updated, both event triggering and result collection retain source identifiers, and subsequent linkage to the next step is supported.

[0065] Therefore, through one or more embodiments of this disclosure, a proactive connection between information and task actions is achieved on the workbench. For example, by gaining insight into the information source, a task can be initiated with a single click, and a valid task completion result can be obtained. This significantly reduces the cost of task initiation and context switching, and improves task conversion rate and execution consistency. For instance, initiating a task on the requirement details page of the product requirement platform can automatically parse information such as requirement ID, node, responsible person, status, and associated resources, generate an analysis report with one click, and make it consumable in the project space, avoiding multiple jumps and manual parameter filling.

[0066] On the other hand, one or more embodiments of this disclosure lower the barriers to entry for cold starts and usage. For example, by providing a "passive / active" task suggestion entry point (automatically generated from insights + scenario-based operation guidance) on the workbench, the initial value experience time is shortened, and the usage loss caused by "remembering and re-entering" is reduced. New users can receive personalized tasks immediately after logging in, improving the technical foundation for activation and retention. For example, after user registration, the workbench automatically generates "task suggestions" (such as "generate a project progress summary based on this week's meeting minutes") based on the accessed information sources, which users can initiate with one click without having to devise prompts beforehand.

[0067] Furthermore, through one or more embodiments of this disclosure, a bidirectional link is established between the workbench components and the platform, enhancing team collaboration. For example, a bidirectional connection is formed between the platform (product requirement platform, code repository platform, instant messaging platform, product development task platform, etc.) and the workbench, from event to task, and from result to next action. This technically enables result write-back or alternative offline suggestions, allowing outputs in the project space to be collaboratively consumed. For instance, the MR on the code repository platform triggers "automated review" and generates modification suggestions. The results are aggregated and displayed on the workbench, where users can continue to reply with comments / create follow-up tasks, adopt suggestions with one click, or jump back to the source platform via MR.

[0068] Furthermore, one or more embodiments of this disclosure improve parameter passing and context mapping. For example, when entering the task processing workbench from the platform or initiating a task on the task processing workbench, context parsing and field-level parameter mapping are performed to pre-populate parameters in the template, reducing secondary parameter filling and manual information mining, lowering the risk of incorrect filling, and improving execution efficiency and the stability of result quality. As another example, when initiating a task with one click from the product requirement platform, information such as the requirement ID, current node, associated document / code link, and responsible person is automatically parsed and filled into the required parameter fields of the template.

[0069] Furthermore, one or more embodiments of this disclosure ensure consistent permissions and contextual compliance. For example, all read / write operations follow the permissions of the currently logged-in user, preventing unauthorized access and privacy breaches. Explicit notifications and alternative paths (such as generating offline suggestions or guiding permission requests) are provided for unauthorized information, improving system compliance and usability. For another example, when a user lacks access to a dashboard, the workbench displays an inaccessible message and provides an alternative summary or request guidance.

[0070] Figure 9 A schematic block diagram of an electronic device 900 for processing tasks according to some embodiments of the present disclosure is shown. Figure 9As shown, the electronic device 900 includes a first generation module 910 configured to generate a suggestion for creating a first task based on information associated with the first task from at least one data source. The electronic device 900 also includes a second generation module 920 configured to generate the first task based on information associated with the first task and a first task template in response to user feedback on the suggestion for creating the first task.

[0071] In some embodiments, the electronic device 900 is further configured to obtain a first task template, parse a page associated with the first task from at least one data source based on the first task template, and obtain information associated with the first task based on the parsed page associated with the first task from the at least one data source. In some embodiments, the page associated with the first task from the at least one data source is the current page of the at least one data source. In some embodiments, the electronic device 900 is further configured to send the first task to a processing entity, receive a first result from the processing entity performing the first task, and, in response to user confirmation of the first result, generate a second task based on the confirmed first result and a second task template associated with the confirmed first result.

[0072] In some embodiments, the electronic device 900 is further configured to obtain a second task template, parse a page associated with the second task from at least one data source based on the second task template, and obtain information associated with the second task based on the parsed page associated with the second task from the at least one data source. In some embodiments, generating a second task based on a confirmed first result and a second task template associated with the confirmed first result may include, in response to receiving a user's request to generate a second task, sending the confirmed first result and the second task template associated with the confirmed first result to a processing entity, and receiving the second task generated by the processing entity based on the confirmed first result and the second task template associated with the confirmed first result.

[0073] In some embodiments, the electronic device 900 is further configured to send a second task to a first data source among at least one data source to perform the second task based on the first data source, and to receive a second result from the first data source performing the second task. In some embodiments, the electronic device 900 is further configured to generate a third task based on the confirmed second result and a second task template associated with the confirmed second result in response to user confirmation of the second result.

[0074] In some embodiments, the first generation module 910 is further configured to generate a suggestion on whether to initiate the first task based on information associated with the first task from the first data source, or to generate an execution suggestion on whether to initiate the first task and how to execute the first task based on information associated with the first task from the first data source. In some embodiments, the first generation module 910 is further configured to determine user permissions, and based on user permissions, determine information associated with the first task from the first data source. In some embodiments, the first generation module 910 is further configured to determine team-shared information in the information associated with the first task from the first data source.

[0075] In some embodiments, the electronic device 900 is further configured to classify tasks from at least one data source, and to determine corresponding triggering rules and display styles for the classified tasks based on the classified tasks from at least one data source. In some embodiments, determining the corresponding triggering rules and display styles for the classified tasks from at least one data source includes at least one of the following: determining information about the classified tasks to be displayed; determining a task template associated with the classified tasks; or, in response to the absence of a task template associated with the classified tasks, determining reference information to provide to the user when initiating a task. In some embodiments, determining the reference information to provide to the user when initiating a task may include generating task requirement instructions based on the content description of the classified tasks, the current node of the classified tasks, the user's role, or the task objective, for the user to refer to when initiating a task.

[0076] In some embodiments, each of the at least one data source has a corresponding task configuration page. In some embodiments, at least one platform includes at least one of the following: a product requirement platform; a code repository platform; an instant messaging platform; and a product development task platform. In some embodiments, the information associated with the first task includes at least one of the following: a task requirement identifier; a task title; a task content description; a task start time or end time; a task leader; task participants; a task type; the current task node; a task status; task-related resources; code repository information; code repository merge request information; code author information; code reviewer information; code repository status; a list of code repository change files; current development task stage information; or upstream and downstream relationship information of the development task.

[0077] Understandably, in this way, one or more embodiments of the electronic device 900 achieve proactive connection from information to action on the workbench, that is, automatically generating consumable insights and feasible operations around the information sources already accessed by the user, supporting one-click task initiation and parameter pre-filling. Furthermore, one or more embodiments of the electronic device 900 can achieve bidirectional communication with the task processing module or platform, significantly reducing initiation costs and context switching costs. Additionally, one or more embodiments of the electronic device 900 lower the cold start and usage threshold by providing a task suggestion entry on the workbench, reducing the steps and time required for users to configure and execute tasks for the first time, and reducing user experience degradation caused by having to remember relevant task parameters and manually input them, thereby greatly improving user experience and work efficiency, and enabling timely completion of relevant tasks.

[0078] Figure 10 A block diagram of a device 1000 capable of implementing various embodiments of the present disclosure is shown. For example... Figure 10 As shown, device 1000 includes a central processing unit (CPU) and / or a graphics processing unit (GPU) 1001, which can perform various appropriate actions and processes according to computer program instructions stored in read-only memory (ROM) 1002 or loaded from storage unit 1008 into random access memory (RAM) 1003. Various programs and data required for the operation of device 1000 can also be stored in RAM 1003. The CPU / GPU 1001, ROM 1002, and RAM 1003 are interconnected via bus 1004. Input / output (I / O) interface 1005 is also connected to bus 1004. Although not shown in... Figure 10 As shown, device 1000 may also include a coprocessor.

[0079] Multiple components in device 1000 are connected to I / O interface 1005, including: input unit 1006, such as keyboard, mouse, etc.; output unit 1007, such as various types of monitors, speakers, etc.; storage unit 1008, such as disk, optical disk, etc.; and communication unit 1009, such as network card, modem, wireless transceiver, etc. Communication unit 1009 allows device 1000 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0080] The various methods or processes described above can be executed by CPU / GPU 1001. For example, in some embodiments, the methods may be implemented as computer software programs tangibly contained in a machine-readable medium, such as storage unit 1008. In some embodiments, part or all of the computer program may be loaded and / or installed on device 1000 via ROM 1002 and / or communication unit 1009. When the computer program is loaded into RAM 1003 and executed by CPU / GPU 1001, one or more steps or actions in the methods or processes described above can be performed.

[0081] In some embodiments, the methods and processes described above can be implemented as a computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for performing various aspects of this disclosure.

[0082] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example, but not limited to, electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination thereof. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0083] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, a local area network (LAN), a wide area network (WAN), and / or a wireless network, to an external computer or external storage device. The network may include copper cables, fiber optic cables, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0084] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​and conventional procedural programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone 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 via 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., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to execute the computer-readable program instructions, thereby implementing various aspects of this disclosure.

[0085] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0086] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0087] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0088] This disclosure also provides the following examples:

[0089] Example 1. A method for processing tasks, comprising:

[0090] Based on information associated with the first task from at least one data source, generate a suggestion for creating the first task;

[0091] In response to user feedback on suggestions for creating a first task, the first task is generated based on information associated with the first task and the first task template.

[0092] Example 2. The method described in Example 1 further includes:

[0093] Get the first task template;

[0094] Based on the first task template, parse at least one page from a data source associated with the first task; and

[0095] Based on the parsed page associated with the first task from at least one data source, obtain the information associated with the first task.

[0096] Example 3. According to the method described in Examples 1-2, the page associated with the first task of at least one data source is the current page of at least one data source.

[0097] Example 4. The method described in Examples 1-3 further includes:

[0098] Send the first task to the processing entity;

[0099] Receive the first result of the processing entity performing the first task;

[0100] In response to the user's confirmation of the first result, a second task is generated based on the confirmed first result and the second task template associated with the confirmed first result.

[0101] Example 5. The method described in Examples 1-4 further includes:

[0102] Get the second task template;

[0103] Based on the second task template, parse at least one page from a data source associated with the second task; and

[0104] Based on the parsed page associated with the second task from at least one data source, obtain information related to the second task.

[0105] Example 6. According to the method described in Examples 1-5, generating the second task based on the confirmed first result and the second task template associated with the confirmed first result includes:

[0106] In response to receiving a user's request to generate a second task, the confirmed first result and the second task template associated with the confirmed first result are sent to the processing entity; and

[0107] The receiving and processing entity generates a second task based on the confirmed first result and the second task template associated with the confirmed first result.

[0108] Example 7. The method described in Examples 1-6 further includes:

[0109] Send the second task to the first data source in at least one data source to execute the second task based on the first data source; and

[0110] Receive the second result of the second task from the first data source.

[0111] Example 8. The method described in Examples 1-7 further includes:

[0112] In response to the user's confirmation of the second result, a third task is generated based on the confirmed second result and the second task template associated with the confirmed second result.

[0113] Example 9. According to the method described in Examples 1-8, wherein generating a suggestion to create the first task based on information associated with the first task from at least one data source includes at least one of the following:

[0114] Based on information related to the first task from the first data source, generate a suggestion on whether to initiate the first task; or

[0115] Based on the information associated with the first task from the first data source, generate suggestions on whether to initiate the first task and how to execute the first task.

[0116] Example 10. According to the method described in Examples 1-9, generating a suggestion to create the first task based on information associated with the first task from at least one data source further includes:

[0117] Determine user permissions; and

[0118] Based on the user's permissions, determine the information associated with the first task from the first data source.

[0119] Example 11. According to the method described in Examples 1-10, generating a suggestion to create the first task based on information associated with the first task from at least one data source further includes:

[0120] Identify team-shared information from the primary data source that is associated with the primary task.

[0121] Example 12. The method according to Examples 1-11 further includes:

[0122] Classify tasks based on at least one data source; and

[0123] Based on the categorized tasks from at least one data source, determine the corresponding triggering rules and display styles for the categorized tasks.

[0124] Example 13. According to the method described in Examples 1-12, determining the corresponding triggering rules and display style for the categorized tasks based on at least one data source includes at least one of the following:

[0125] Determine the information for the categorized tasks that need to be displayed;

[0126] Determine the task template associated with the categorized tasks; or

[0127] In response to the absence of a task template associated with the categorized task, determine the reference information to provide to the user when initiating a task.

[0128] Example 14. According to the method described in Examples 1-13, determining the reference information provided to the user when initiating a task includes:

[0129] Based on the content description of the categorized tasks, the current node of the categorized tasks, the user's role or task objective, a task requirement instruction is generated for the user to refer to when initiating a task.

[0130] Example 15. The method described in Examples 1-14, wherein each platform in at least one data source has a corresponding task configuration page.

[0131] Example 16. According to the method described in Examples 1-15, at least one data source includes at least one of the following:

[0132] Product demand platform;

[0133] Code repository platform;

[0134] Instant messaging platform;

[0135] Product development task platform.

[0136] Example 17. The method according to Examples 1-16, wherein the information associated with the first task includes at least one of the following:

[0137] Task requirement identifier;

[0138] Task title;

[0139] Task description;

[0140] Task start time or end time;

[0141] Task leader;

[0142] Task participants;

[0143] Task type;

[0144] Current node of the task;

[0145] Task status;

[0146] Task-related resources;

[0147] Code repository information;

[0148] Code repository merge request information;

[0149] Code author information;

[0150] Code reviewer information;

[0151] Codebase status;

[0152] List of changed files in the codebase;

[0153] Information on the current stage of the development task; or

[0154] Information on upstream and downstream relationships in development tasks.

[0155] Example 18. An electronic device comprising:

[0156] A first generation module is configured to generate a suggestion for creating a first task based on information associated with the first task from at least one data source.

[0157] The second generation module is configured to generate the first task in response to user feedback on suggestions for creating the first task, based on information associated with the first task and the first task template.

[0158] Example 19. An electronic device comprising:

[0159] Processor; and

[0160] A memory coupled to a processor, the memory having instructions stored therein, which, when executed by the processor, cause the electronic device to perform a method according to any one of Examples 1 to 17.

[0161] Example 20. A computer program product comprising computer-executable instructions, wherein the computer-executable instructions are executed by a processor to implement a method according to any one of Examples 1 to 17.

[0162] The various embodiments of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical applications, or technical improvements to the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A method for processing a task, comprising: generating a suggestion to create a first task based on information associated with the first task of at least one data source; generating the first task based on the information associated with the first task and a first task template in response to a feedback of a user to the suggestion to create the first task.

2. The method of claim 1, further comprising: obtaining the first task template; parsing a page of the at least one data source associated with the first task based on the first task template; and obtaining the information associated with the first task based on the parsed page of the at least one data source associated with the first task.

3. The method of claim 2, wherein the page of the at least one data source associated with the first task is a current page of the at least one data source.

4. The method of claim 1, further comprising: sending the first task to a processing entity; receiving a first result of the processing entity executing the first task; generating a second task based on the confirmed first result and a second task template associated with the confirmed first result in response to the user confirming the first result.

5. The method of claim 4, further comprising: obtaining the second task template; parsing a page of the at least one data source associated with the second task based on the second task template; and obtaining the information associated with the second task based on the parsed page of the at least one data source associated with the second task.

6. The method of claim 4, wherein generating a second task based on the confirmed first result and a second task template associated with the confirmed first result comprises: sending the confirmed first result and the second task template associated with the confirmed first result to the processing entity in response to receiving a request of the user to generate the second task; and receiving the second task generated by the processing entity based on the confirmed first result and the second task template associated with the confirmed first result.

7. The method of claim 4, further comprising: sending the second task to a first data source of the at least one data source to execute the second task based on the first data source; and receiving a second result of the first data source executing the second task.

8. The method of claim 7, further comprising: generating a third task based on the confirmed second result and a second task template associated with the confirmed second result in response to the user confirming the second result.

9. The method of claim 1, wherein generating a suggestion to create a first task based on information associated with the first task of at least one data source comprises at least one of: generating a suggestion whether to initiate the first task based on the information associated with the first task of a first data source; or ​ ​ ​ ​ generating, based on information associated with a first task of at least one data source, a suggestion of whether to initiate the first task and an execution suggestion of how to execute the first task.

10. The method of claim 1, wherein generating, based on information associated with a first task of at least one data source, a suggestion of creating the first task further comprises: determining a permission of the user; and determining the information associated with the first task of the first data source based on the permission of the user.

11. The method of claim 1, wherein generating, based on information associated with a first task of at least one data source, a suggestion of creating the first task further comprises: determining team sharing information in the information associated with the first task of the first data source.

12. The method of claim 1, further comprising: classifying tasks of the at least one data source based on the at least one data source; and determining a corresponding trigger rule and a presentation style of the classified tasks based on the classified tasks of the at least one data source.

13. The method of claim 12, wherein determining a corresponding trigger rule and a presentation style of the classified tasks based on the classified tasks of the at least one data source comprises at least one of: determining information of the classified tasks that needs to be presented; determining a task template associated with the classified tasks; or determining reference information provided to the user when initiating a task in response to a task template associated with the classified tasks not being configured.

14. The method of claim 13, wherein determining reference information provided to the user when initiating a task comprises: generating task requirement instructions for reference by the user when initiating a task based on a content description of the classified tasks, a current node of the classified tasks, a user function, or a task objective.

15. The method of claim 12, wherein each of the at least one data source has a corresponding task configuration page.

16. The method of claim 1, wherein the at least one data source comprises at least one of: a product requirement platform; a code base platform; an instant messaging platform; a product development task platform.

17. The method of claim 1, wherein the information associated with a first task comprises at least one of: a task requirement identifier (ID); a task title; a task content description; a task start time or a deadline; a task owner; a task participant; a task type; a task current node; a task status; a task associated resource; code base information; code base merge request information; code author information; code reviewer information; code base status; a code base change file list; development task current stage information; or development task upstream and downstream association information.

18. An electronic device, comprising: a first generating module configured to generate, based on information associated with a first task of at least one data source, a suggestion of creating the first task; a second generation module configured to generate, in response to feedback from a user with respect to the suggestion to create the first task, the first task based on information associated with the first task and a first task template.

19. An electronic device, comprising: a processor; and a memory coupled with the processor, the memory having stored therein instructions which, when executed by the processor, cause the electronic device to perform the method according to any one of claims 1-17.

20. A computer program product comprising computer-executable instructions, wherein the computer-executable instructions are executed by a processor to implement the method according to any one of claims 1-17.

Images