CN120407006A

CN120407006A - Data interaction system and method based on Feishu card message directly triggering Jira workflow

Info

Publication number: CN120407006A
Application number: CN202510484068.XA
Authority: CN
Inventors: 王晓杰; 孙芳
Original assignee: Beijing Dianfu Technology Co ltd
Current assignee: Beijing Dianfu Technology Co ltd
Priority date: 2025-04-17
Filing date: 2025-04-17
Publication date: 2025-08-01

Abstract

The present invention provides a data interaction system and method based on Feishu card messages directly triggering Jira workflows. By using a webhook configured on the Jira platform to monitor specific events, and upon detecting a specific event, the system sends the event data to a local server for parsing and conversion to generate Feishu card information. The local server then sends the Feishu card information to a created Feishu application. The Feishu application then forwards the received Feishu card information to designated users within the configured permission range, allowing the designated users to access the Jira platform and perform corresponding operations using the Feishu card information. The present invention enables Feishu card messages to directly trigger Jira workflows, solving the information island problem found in existing integration solutions while also improving the automation level and response speed of the entire workflow.

Description

Data interaction system and method based on direct trigger Jira workflow of book flying card information

Technical Field

The invention relates to the technical field of computers, in particular to a data interaction system and method based on a fly book card message to directly trigger Jira workflow.

Background

Integration of project management and team collaboration tools is becoming increasingly important. Especially in the field of software development, agile development and DevOps practices emphasize the value of fast iteration and continuous delivery. To achieve these goals, efficient information circulation and automated workflow is essential.

In an actual working scenario, project management tools such as Jira and instant messaging platform fly books often run independently. The mutually separated state promotes the serious information island problem, so that the data among different systems are difficult to realize effective sharing, and the improvement of team cooperation efficiency is greatly hindered. For example, when a tester submits a bug at Jira, the developer cannot perceive and process the bug in time, which delays the best time for problem solving and slows down the overall progress of the project.

As business complexity continues to rise, so does the need for automation by businesses. Enterprises are urgent to expect to reduce human intervention, improve working efficiency, and simultaneously ensure that all related personnel can acquire the latest project progress in real time. However, existing solutions tend to be frustrating in dealing with this need, and the problem is even more pronounced, especially when cross-platform operation is involved. Moreover, the traditional notification mode is limited to a simple text form, lacks interactivity, and is difficult to meet the requirement of efficient collaboration of the next team.

Disclosure of Invention

In view of the above-mentioned drawbacks of the prior art, the present invention aims to provide a data interaction system and method based on the direct triggering Jira of the flyer card message, which are used for solving the technical problems in the prior art that the independent work of Jira and flyer cannot be timely fed back to project data and progress, so that workers cannot find and process in time, and further the working efficiency is reduced.

In order to achieve the above and other related objects, the invention provides a data interaction system based on a fly book card message to directly trigger Jira a workflow, which comprises a created fly book application, a Jira platform, a built local server and a corresponding user, wherein the created fly book application is configured with corresponding authorities, the Jira platform is configured with webhook for monitoring specific events, the built local server is used for receiving event data from the Jira platform and converting the event data into a message format suitable for the fly book card to display so as to generate fly book card information, wherein the specific events are monitored through webhook, the event data are sent to the local server to be analyzed and converted into the fly book card information when the specific events are monitored, the local server sends the fly book card information to the created fly book application, and the fly book application forwards the received fly book card information to the designated user within the range of the configured authorities so that the corresponding user can enter the Jira platform through the fly book card information to perform corresponding operations.

In one embodiment of the invention, an flybook application is created on a flybook open platform, user ID acquisition permission and flybook card information receiving and transmitting permission of the flybook application are configured, and an API interface is provided for a local server to call, wherein the user ID acquisition permission comprises single user ID permission and group ID permission.

In one embodiment of the present invention, webhook is configured for a specific event on the Jira platform, and a trigger condition of the specific event and a URL address of the local server are set, where when webhook monitors that a corresponding specific event is triggered, event data is sent to the URL address through an HTTP request.

In an embodiment of the present invention, webhook is configured on the Jira platform for a specific work order status change event, and status switching of the corresponding work order status between different processing stages is used as a trigger condition, so that when the webhook monitors that the work order status is switched to the processing stage, the current work order data is sent to the local server.

In one embodiment of the invention, a Python in combination with Flask framework is used to build a local server.

In an embodiment of the present invention, the local server analyzes the received worksheet data from webhook, and maps the analyzed worksheet information to each field in the corresponding flyer card template based on a preset data mapping rule, so as to generate the flyer card information.

In one embodiment of the invention, corresponding flying book card templates are constructed according to different work order states, wherein the flying book card templates comprise basic information of the work order and operation buttons for users to click to enter a Jira platform.

In an embodiment of the present invention, the local server sends an authentication request to an API interface of the flybook application based on the identity credential provided by the flybook application, and sends flybook card information to the API interface after the authentication is passed.

In an embodiment of the present invention, the local server encrypts the flyash card information including the sensitive information, and then transmits the encrypted flyash card information to the API of the flyash application, so that the flyash application can forward the corresponding flyash card information to the designated user within the configuration authority range after decrypting.

In order to achieve the above and other related objects, the present invention provides a data interaction method based on the direct triggering Jira of the flycard message, which comprises the steps of monitoring a specific event through webhook configured on a Jira platform, sending event data to a local server when the specific event is monitored, receiving the event data from the Jira platform through the local server, converting the event data into a message format suitable for the flycard to display, generating flycard information, and sending the flycard information to a created flycard application, and forwarding the received flycard information to a designated user within a configuration authority range by the flycard application, so that the corresponding user can enter the Jira platform to perform corresponding operation through the flycard information.

As described above, the invention is a data interaction system and method based on the direct triggering Jira of the fly book card information, which has the advantages that the invention monitors specific events through webhook configured on the Jira platform, and when the specific events are monitored, the event data are sent to the local server to be analyzed and converted into the fly book card information, the local server sends the fly book card information to the created fly book application, and the fly book application forwards the received fly book card information to the appointed user within the configuration authority range, so that the corresponding user can enter the Jira platform to perform corresponding operation through the fly book card information. The invention realizes the direct triggering Jira of the flying book card message, solves the problem of information island in the existing integration scheme, and improves the automation level and response speed of the whole workflow.

Drawings

Fig. 1 is a schematic structural diagram of a data interaction system based on a direct trigger Jira workflow of a fly-book card message according to an embodiment of the present invention.

FIG. 2 is a schematic diagram of a task handling process for a job ticket in accordance with one embodiment of the present invention.

Fig. 3 is a flow chart illustrating a method for directly triggering Jira a workflow based on a fly-book card message according to an embodiment of the present invention.

Detailed Description

Other advantages and effects of the present invention will become apparent to those skilled in the art from the following disclosure, which describes the embodiments of the present invention with reference to specific examples. The invention may be practiced or carried out in other embodiments that depart from the specific details, and the details of the present description may be modified or varied from the spirit and scope of the present invention. It should be noted that the following embodiments and features in the embodiments may be combined with each other without conflict.

In the following description, reference is made to the accompanying drawings, which illustrate several embodiments of the invention. It is to be understood that other embodiments may be utilized and that mechanical, structural, electrical, and operational changes may be made without departing from the spirit and scope of the present invention. The following detailed description is not to be taken in a limiting sense, and the scope of embodiments of the present invention is defined only by the claims of the issued patent. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Spatially relative terms, such as "upper," "lower," "left," "right," "lower," "below," "lower," "above," "upper," and the like, may be used herein to facilitate a description of one element or feature as illustrated in the figures relative to another element or feature.

Throughout the specification, when a portion is said to be "connected" to another portion, this includes not only the case of "direct connection" but also the case of "indirect connection" with other elements interposed therebetween. In addition, when a certain component is said to be "included" in a certain section, unless otherwise stated, other components are not excluded, but it is meant that other components may be included.

The first, second, and third terms are used herein to describe various portions, components, regions, layers and/or sections, but are not limited thereto. These terms are only used to distinguish one portion, component, region, layer or section from another portion, component, region, layer or section. Thus, a first portion, component, region, layer or section discussed below could be termed a second portion, component, region, layer or section without departing from the scope of the present invention.

Furthermore, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes," and/or "including" specify the presence of stated features, operations, elements, components, items, categories, and/or groups, but do not preclude the presence, presence or addition of one or more other features, operations, elements, components, items, categories, and/or groups. The terms "or" and/or "as used herein are to be construed as inclusive, or meaning any one or any combination. Thus, "A, B or C" or "A, B and/or C" means "any of A, B, C, A and B, A and C, B and C, A, B and C". An exception to this definition will occur only when a combination of elements, functions or operations are in some way inherently mutually exclusive.

The invention provides a data interaction system based on a fly book card message to directly trigger Jira workflow, which monitors a specific event through webhook configured on a Jira platform, transmits event data to a local server to analyze and convert the event data to generate fly book card information when the specific event is monitored, and transmits the fly book card information to a created fly book application, and the fly book application forwards the received fly book card information to a designated user within a configuration authority range so that a corresponding user can enter the Jira platform to perform corresponding operation through the fly book card information. The invention realizes the direct triggering Jira of the flying book card message, solves the problem of information island in the existing integration scheme, and improves the automation level and response speed of the whole workflow.

The embodiments of the present invention will be described in detail below with reference to the attached drawings so that those skilled in the art to which the present invention pertains can easily implement the present invention. This invention may be embodied in many different forms and is not limited to the embodiments described herein.

Fig. 1 shows a schematic flow chart of a data interaction system based on the direct triggering Jira of workflow by the fly-book card message in the embodiment of the invention.

The system comprises:

the created flyer book application 1 is configured with corresponding rights;

Jira platform 2 is configured with webhook to listen for a particular event, which may be a change to any item of data in Jira.

The built local server 3 is used for receiving event data from the Jira platform 2, converting the event data into a message format suitable for displaying the flying book card, and generating flying book card information;

The method comprises the steps of monitoring a specific event through webhook, sending event data to a local server 3 to analyze and convert the event data to generate flying book card information when the specific event is monitored, sending the flying book card information to a created flying book application 1 by the local server 3, and forwarding the received flying book card information to a designated user within a configuration authority range by the flying book application 1 so that a corresponding user can enter a Jira platform 2 through the flying book card information to perform corresponding operation.

The system realizes real-time monitoring of the change of project data in Jira by configuring webhook on Jira platform 2, synchronizes the change to the flyash through the built local server 3, precisely pushes Jira key project progress information to a specific user based on strong message pushing capability of the flyash, has an interactive function instead of simple text pushing, and can be used by a receiver to directly execute simple operation in the flyash message to enter Jira platform 2. The method ensures that data between the Jira platform and the flyer book are shared in real time, breaks through the information barriers between the Jira platform and the flyer book, changes the situation that the data of different platforms are difficult to communicate in the past, and enables development, testing and other personnel to acquire bug related information in time. Conventionally, starting Jira the workflow requires a series of operations to be performed manually at Jira. The fly book card information in the system can trigger Jira the workflow by one key, so that manual operation steps are reduced, the process is automatically operated, and the task execution efficiency is greatly improved.

In one embodiment, the creation of the flybook application 1 includes:

And logging in an flyer book open platform, creating a flyer book application 1 according to the flyer book official document guide, and filling in detailed information of the application according to actual requirements, wherein the detailed information comprises an application name, an application description and the like. For example, the application name is "work order status notification should", and the application is described as "this application is used to receive Jira work order status flycard information and send it to a designated user or group".

And configures the user ID acquisition authority and the messaging authority of the flybook application 1, wherein the user ID acquisition authority comprises the authority of acquiring a single user ID or a group ID, and for example, a plate relevant to authority management is found in an application configuration interface. In the rights list, rights to acquire a single user ID or group ID are checked. The right to acquire a single user ID can be used to precisely send messages to a particular user, and the right to acquire a group ID can be used to send messages to all members within the group. The messaging rights include receiving the flyer card information rights from the local server 3 and sending the flyer card information rights to users or groups within the rights. For example, in the right management block as well, a right to receive the fly-book card information from the local server 3 is configured. This means that the local server 3 can send pre-designed fly card information to the application 1. Configuring the authority for transmitting the fly-book card information to the users or groups within the authority range. Thus, the application can push the received card information to the designated user or group.

The flybook application 1 provides an API interface for the local server 3 to call, and specific information of the API interface including an interface address, a request method, a request parameter, a return value, and the like is required to be set. It is ensured that the local server 3 can access these API interfaces via the network in order to invoke them when needed to achieve the functions of user ID acquisition and messaging etc.

In one embodiment, the manner in which platform 2 is configured webhook at Jira includes:

The settings page of Jira platform 2 is entered, webhook is configured for a particular event, and the basic information of webhook is filled in, including a name and description, for example, a name "work order status change notification", briefly described as "send notification to local server 3 when the phase status of work order status is switched". And sets the triggering condition of the specific event, jira provides various event types for selection, and common has the functions of work order creation, work order update, work order state change and the like. For example, if you are focusing on a work order status change event, select the corresponding "work order status change" option and set the trigger condition. The URL address of the local server 3 is also set, which is the URL address of the local server 3 that receives Webhook data.

When webhook monitors that the corresponding specific event is triggered, event data is sent to a preset URL address through an HTTP request.

In one embodiment, at Jira, there are various work order states, such as the Bug state. When the status of the work order changes, a "status change event" is generated. The invention configures webhook for a particular work order state change event on Jira platform 2 and uses state switching of the corresponding work order state between different processing stages as a trigger condition. webhook continuously monitor the phase change of all work order states. Whenever a job ticket status changes in phase, jira checks if the status change meets the trigger condition set by us, if so, it means that the trigger Webhook condition is met, webhook sorts the relevant data (such as the job ticket number, title, description, current status, etc.) of the current job ticket status into a suitable format (typically JSON format), and then sends the relevant data to the URL of the local server 3 specified by us through an HTTP request. The local server 3 can obtain the work order state change information in time so as to carry out subsequent processing, such as notifying related personnel, updating other system data and the like.

For example, for the Bug state, common phase states are "committed", "processed to verify", "verified", and "resolved". Each time a Bug work order changes from one state to another, a state change event is generated. When the status of the Bug work order is changed from 'submitted' to 'processed to be verified', the developer processes the submitted Bug to wait for verification of the tester, at this time Webhook sends the current work order data to the local server 3, so that the local server 3 communicates with the flyer application 1 to push 'to be verified' information (including key content of the Bug work order) to the tester responsible for verification. When the Bug work order is changed from 'processed to verified' to 'verified', the tester is informed that the Bug is verified and confirms that the Bug is repaired, at this time Webhook sends the current work order data to the local server 3, so that the local server 3 communicates with the flyer application 1 to send 'verified' information to related personnel (such as project manager, developer and the like), and informs them that the Bug is verified, and the solution flow can be entered. When the Bug work order changes from "verified" to "resolved", it represents that this Bug has completed the entire process flow, at which point Webhook sends the current work order data to the local server 3, causing the local server 3 to communicate with the flyer application 1 to send "resolved" information to all users focusing on the Bug, informing them that this Bug has been thoroughly resolved.

In an embodiment, the local server 3 is built using a Python in combination Flask framework. The Python grammar is simple, the readability is strong, the Flask core is light and has no complex configuration, and the combination of the Python grammar and the Flask core greatly improves the development efficiency, so that a developer can quickly get on hand and accelerate development by means of rich expansion libraries. The server can freely integrate the third party library according to the actual requirements to customize the functions and the architecture. The lightweight Flask has the advantages of less occupation of resources, high performance, ensured stability by error processing and debugging mechanisms, rich document and community resources matched by clear code structures, and great improvement of maintainability. And it supports the distributed architecture, is convenient for carrying on the function expansion according to the business development, respond to the high concurrency and changeable business demand from beginning to end.

In one embodiment, corresponding fly book card templates are designed according to different work order states. The template needs to cover the basic information of the work order and the operation buttons.

The work order basic information includes:

the title of the work order, i.e., the brief name of the work order, such as "JIRA bug daily reminder", is explicitly shown at the title location.

The detailed description of the work order provides deeper information for users so that they can know the details and the background of the work order.

The responsible person displays the name of the person responsible for processing the work order.

The operation button includes:

And a detail view button is clicked, and a user can enter a work order detail page of the Jira platform. This enables the user to view the complete process record and the latest progress of the work order, obtaining more comprehensive information.

And marking a completion button, namely clicking the button to submit a completion confirmation when the processor considers that the work order is processed. The operation is monitored by the Jira platform, so that the stage state of the work order is updated, a new processing stage is entered, and the dynamic property and the interactivity of the whole flow are reflected.

In one embodiment, the local server 3 processes the parsed work order information based on a preset data mapping rule. These preset rules are predefined and define how to map the various parts of the work order information to the various fields of the fly book card template. For example, a work order summary may be mapped to a work order title of the flyer card, and a work order description may be mapped to a work order description of the flyer card. Through this mapping operation, the local server 3 can populate the work order information into the flyer card template, thereby generating the flyer card information.

In one embodiment, the local server 3 is in a listening state awaiting receipt of work order state change data sent from Webhook of Jira's platform 2. Upon receiving the data, the primary task of the local server 3 is to parse the data. Since Webhook sent data may be encapsulated in a specific format (e.g., JSON, XML, etc.), the server needs to disassemble the data according to the rules of the corresponding format, and identify the critical work order information. Such work order information may include the number, title, description, current status, responsible person, etc. of the work order, which is the basis for subsequent processing. After the job ticket information is successfully analyzed, the local server 3 calls the corresponding flyer card template according to the recognized job ticket state. Once the corresponding fly card template is determined, the local server 3 performs the next operation in combination with the preset data mapping rule. These mapping rules specify how the fields in the work order information should be mapped to the positions of the flyer card template through such accurate data mapping, and the local server 3 accurately fills the parsed work order information into the fields of the flyer card template, thereby generating complete flyer card information.

In one embodiment, the local server 3 needs to obtain the identity credential provided by the flybook application 1 before starting to interact with the flybook application 1. This identity credential is typically generated by the flyweight open platform at the time of creation of flyweight application 1 and assigned to the application, such as a Client ID (Client ID), a Client key (CLIENT SECRET), and the like. The local server 3 sends an authentication request to the API interface of the flybook application 1 based on the acquired identity credential and the selected authentication mode. The request contains the relevant identity certificate information, and the API interface of the flybook application 1 verifies the identity certificates in the request to check whether the certificates are correct and valid and conform to the corresponding security policies. After the API interface of the flybook application 1 processes the authentication request, an authentication result is returned. If the identity credential is correct and all verification conditions are met, the identity verification is passed, and the API interface returns corresponding successful identification, possible authorization token and other information. After receiving the successful verification result, the local server 3 obtains the authority of legally accessing the API interface of the flyer book application 1. If the authentication fails, for example, the identity credential is wrong or the security policy is not satisfied, the API interface returns an error message, and the local server 3 needs to perform corresponding processing according to the error prompt, for example, checking whether the identity credential is correct, reacquiring the identity credential, etc. When the authentication of the local server 3 is passed, it can send the flyer card information to the API interface of the flyer application 1.

Preferably, the local server 3 employs oauth2.0 protocol to ensure the security of API calls. Oauth2.0 is a widely used authorization framework that allows the local server 3 to obtain access to the flyash application API without directly passing sensitive information such as the user's password.

In one embodiment, after the local server 3 generates the fly book card information, it first needs to determine whether the card information contains sensitive information. Sensitive information may include, but is not limited to, personal identity information of the user (e.g., name, contact, etc.), business critical data (e.g., financial data, business secrets, etc.), work order content related to privacy, etc. Upon confirming that the flyer card information contains sensitive information, the local server 3 is ready for SSL/TLS encryption. This includes obtaining or configuring the appropriate SSL/TLS certificates. SSL/TLS certificates are issued by a trusted Certificate Authority (CA) and contain the identity information of the server as well as the public key. The local server 3 needs to ensure that the certificates used are valid, unexpired, and match the domain name or IP address of the server. The local server 3 encrypts the fly-book card information containing the sensitive information by using the acquired SSL/TLS certificate and a corresponding encryption algorithm. In the SSL/TLS encryption process, the server encrypts the data using the public key, converting the original plaintext fly card information into ciphertext. Even if the ciphertext is intercepted in the network transmission process, the interceptor cannot read the content because the interceptor does not have the corresponding private key, so that the confidentiality of the data is ensured. After the encryption is completed, the local server 3 transmits the encrypted flyer card information to the API interface of the flyer application 1 through the network. After receiving the encrypted flyer card information, the API interface of the flyer application 1 decrypts the ciphertext by using the private key corresponding to the flyer card information. After successfully decrypting the flyer card information, the flyer application 1 forwards the corresponding flyer card information to the designated user according to the preset authority range.

In one embodiment, the system performs unit testing, integration testing, performance testing, and exception handling testing.

Unit testing focuses primarily on individual modules of the system. For the present system, the modules may include Webhook modules configured by the flyweight application 1, jira platform 2, and the local server 3. After the flybook application 1 is built, whether the identity certificate provided by the flybook application 1 can be used normally or not is verified, whether the flybook application 1 can correctly receive the flybook card information from the local server 3 or not is tested, whether the flybook card information can be forwarded to a user or not is tested, and the like. Testing of Webhook modules configured on Jira platform 2 includes ensuring that Webhook can be accurately triggered in accordance with the conditions configured on Jira platform 2. When Webhook triggers, it is checked whether it can send the correct work order data to the local server 3. Testing of the local server 3 includes simulating the sending of work order data of different formats and content from Webhook of the Jira platform, checking if the local server 3 can correctly receive and parse the data. After the local server 3 analyzes the data, the work order information needs to be mapped onto the corresponding flyer card template field according to a preset data mapping rule. For the flybook card information containing the sensitive information, it is tested whether the local server 3 can correctly perform SSL/TLS encryption, and the encrypted data is securely transmitted to the API interface of the flybook application 1.

The integrated test simulates a real environment, and each module is combined for testing, so that the importance is attached to whether the whole flow of the system is smooth or not. Starting with Jira platform 2, the simulated work order state changes event triggers, webhook monitors event triggers to send data. Then, the local server 3 receives and processes the data to generate the fly-book card information. Then, the local server 3 performs identity verification based on the identity credentials of the flybook application 1, and after passing, sends the flybook card information to the API interface of the flybook application 1. Finally, the flyer book application 1 receives the information and forwards it to the designated user within the configuration authority range. In the process, whether the connection between each link is normal or not is checked, and whether data can be accurately transmitted between each component or not is ensured, so that the problems of data loss, error processing and the like do not occur in the whole message transmission process from Jira to the flyer book.

Performance testing mainly evaluates the performance of a system in high concurrency situations. In practical application, a large number of work order state change events may occur at the same time, so that Webhook is frequently triggered, and a large amount of data is gushed into the local server 3. By means of a special testing tool or method, a large number of events which occur simultaneously are simulated, the running state of the system under the high concurrency condition is observed, whether the local server 3 can process a large amount of data in time is checked, and the conditions of jamming, breakdown and the like are avoided.

Exception handling tests test for various possible exception conditions, such as network interruption, timeout, etc., to verify the robustness and fault tolerance of the system.

In a specific embodiment, in the use scene of the system, a complete work order processing task is processed by depending on a cyclic triggering mechanism. As in FIG. 2, the tester discovers the bug and submits the task at Jira platform 2. At this time, webhook monitors Jira the status change of the platform 2 in real time, and once the change of task submission is captured, rapidly transmits the work order data containing the bug information to the local server 3. After receiving the work order data, the local server 3 generates the flying book card information according to a preset rule and sends the flying book card information to the flying book application 1. The flyer application 1 in turn pushes messages to the relevant group. The developer obtains the bug situation through the fly-book card information, and the platform confirms whether the problem is a real bug or not at Jira. If the user determines that the user does not need to make a bug, the user directly closes the bug, and if the user does not need to make a bug, the developer starts to process the bug from the flying book card information to the Jira platform. When the developer changes the work order state after completing the bug processing, webhook senses the change again and sends updated work order data to the local server 3. The local server 3 generates the flyer card information again and transmits it to the flyer application 1, and the flyer application 1 transmits a message again to the group informing of the bug progress. The testers learn to develop the processed bug through the information of the flying book card, and enter a Jira platform to verify whether the bug is repaired or not. If the repairing is confirmed, the bug is closed, the process is ended, and if the repairing is not found, the tester resubmites the task. Webhook after monitoring the change submitted by the task, sending work order data to the local server 3 again, and starting a new round of circulation of generating the fly book card information by the local server 3, sending a message by the fly book application 1, developing, processing and testing and verifying until the bug is successfully repaired and closed. In addition to the message triggering mechanism in the above procedure, the newly built and closed bug triggers the timing task every day. Under the timing task, webhook sends work order data to the local server 3, the local server 3 generates the flying book card information, and the flying book application 1 sends related information to the group at regular time every day, so as to ensure that team members know the new building and closing dynamics of the bug in time.

Similar to the principles of the above embodiments, the present invention provides a data interaction method based on the direct triggering Jira of the workflow by the fly-book card message.

Specific embodiments are provided below with reference to the accompanying drawings:

Fig. 3 shows a flow chart of a data interaction method based on the direct triggering Jira of the workflow by the fly-book card message in the embodiment of the invention.

The method comprises the following steps:

Step S1, monitoring a specific event through webhook configured on the Jira platform, and sending event data to a local server when the specific event is monitored;

S2, receiving event data from a Jira platform through a local server, converting the event data into a message format suitable for displaying the fly-book card to generate fly-book card information, and sending the fly-book card information to a created fly-book application;

and step S3, forwarding the received flying book card information to a designated user within the configuration authority range by the flying book application so that the corresponding user can enter the Jira platform to perform corresponding operation through the flying book card information.

Since the implementation principle of the data interaction method based on the direct triggering Jira of the fly-book card message has been described in the foregoing embodiments, the description thereof will not be repeated here.

Compared with the prior art, the invention has the advantages that:

1. Automatic flow triggering and test efficiency improvement

The flying book card message can directly trigger Jira workflow, reduce manual operation steps and enable the test flow to run automatically. In the past, a series of operations are needed to be manually performed in Jira to start the workflow, and the workflow is triggered by one key through the flying book card information, so that the time and energy are saved, and the execution speed of the test task is greatly improved.

2. Cross-platform collaboration, information real-time sharing and enhanced communication collaboration

The flybooks and Jira are different platforms, and the workflow of Jira is directly triggered through the flybook card information, so that seamless butt joint and cooperative work between the two platforms are realized. Team members can operate in a familiar flying book environment, meanwhile, by utilizing Jira powerful project management and workflow functions, barriers among platforms are broken, and team cooperation efficiency and effect are improved. And the flying book card information can bear rich information, and key information in the testing process, such as problem description, testing data, related accessories and the like, can be timely and accurately transmitted to related personnel in Jira workflow. Developers, testers and other team members can view and communicate the information in real time in the message card of the flyer book, so that delay and error of information transmission are avoided, and cooperation among teams is promoted.

3. Standardized test flow and improved test accuracy

The Jira workflow triggered based on the fly-book card message can define standardized testing steps and rules, ensuring that each test is performed according to a unified standard. This helps to reduce interference from human factors and improve accuracy and reliability of test results.

4. Data trace back and analysis

After the flying book card message is combined with Jira workflow, various data in the test process can be conveniently recorded, including the generation of problems, the processing process, the results and the like. The data can be used for subsequent tracing and analysis, so that teams can find problems and bottlenecks in the testing process, the testing flow is optimized, and the testing quality is improved.

6. Cost reduction

Fly books are a widely used and relatively simple tool for users to operate, with whom team members are familiar. Through the trigger Jira workflow of the flying book card message, team members do not need to spend a great deal of time learning Jira complicated operation interfaces and processes, and the training cost is reduced. The efficient test flow and good communication cooperation can avoid resource waste and improve the utilization rate of resources.

In summary, according to the data interaction system and method based on the fly book card message direct triggering Jira workflow, the webhook configured on the Jira platform monitors a specific event, and when the specific event is monitored, event data is sent to the local server to be analyzed and converted into fly book card information, the local server sends the fly book card information to the created fly book application, and the fly book application forwards the received fly book card information to the appointed user within the configuration authority range, so that the corresponding user can enter the Jira platform to perform corresponding operation through the fly book card information. The invention realizes the direct triggering Jira of the flying book card message, solves the problem of information island in the existing integration scheme, and improves the automation level and response speed of the whole workflow. Therefore, the invention effectively overcomes various defects in the prior art and has high industrial utilization value.

The above embodiments are merely illustrative of the principles of the present invention and its effectiveness, and are not intended to limit the invention. Modifications and variations may be made to the above-described embodiments by those skilled in the art without departing from the spirit and scope of the invention. It is therefore intended that all equivalent modifications and changes made by those skilled in the art without departing from the spirit and technical spirit of the present invention shall be covered by the appended claims.

Claims

1. A data interaction system based on a fly-book card message direct trigger Jira workflow, the system comprising:

the created flyer application is configured with corresponding rights;

Jira platform configured with webhook for listening for specific events;

the built local server is used for receiving event data from the Jira platform, converting the event data into a message format suitable for displaying the flying book card, and generating flying book card information;

The method comprises the steps of monitoring a specific event through webhook, sending event data to a local server to analyze and convert the event data to generate flying book card information when the specific event is monitored, sending the flying book card information to a created flying book application by the local server, and forwarding the received flying book card information to a designated user within a configuration authority range by the flying book application so that a corresponding user can enter a Jira platform to perform corresponding operation through the flying book card information.

2. The data interaction system based on the direct trigger Jira of the flyer card message as set forth in claim 1, wherein the flyer application is created on the flyer open platform, the user ID acquisition permission of the flyer application and the flyer card information transceiving permission are configured, and an API interface is provided for the local server to call, wherein the user ID acquisition permission includes a single user ID permission and a group ID permission.

3. The system of claim 2, wherein the webhook is configured for a specific event on the Jira platform, and the trigger condition of the specific event and the URL address of the local server are set, wherein when webhook monitors that the corresponding specific event is triggered, the event data is sent to the URL address via an HTTP request.

4. The data interaction system based on the flyer card message direct triggering Jira workflow of claim 3, wherein the configuration webhook is configured for a specific work order status change event on the Jira platform, and the status switch of the corresponding work order status between different processing stages is used as a trigger condition for webhook to send the current work order data to the local server when the status switch of the work order status occurrence processing stage is monitored.

5. The data interaction system based on the direct triggering Jira of the fly-book card message as set forth in claim 1, wherein the local server is built using Python in conjunction with Flask framework.

6. The data interaction system based on the direct trigger Jira workflow of the flyer card message of claim 5, wherein the local server analyzes the received work order information from the work order data of webhook, and maps the analyzed work order information to each field in the corresponding flyer card template based on a preset data mapping rule to generate the flyer card information.

7. The data interaction system based on the direct trigger Jira of the flyer card message in claim 6 is characterized in that corresponding flyer card templates are constructed according to different work order states, wherein the flyer card templates contain basic information of the work order and operation buttons for users to click to enter a Jira platform.

8. The data interaction system based on the direct trigger Jira workflow of the flybook card message as claimed in claim 2, wherein the local server sends an authentication request to the API interface of the flybook application based on the identity credential provided by the flybook application, and sends the flybook card message to the API interface after the authentication is passed.

9. The data interaction system based on the direct trigger Jira workflow of the flybook card message according to claim 2, wherein the local server encrypts the flybook card information containing the sensitive information by SSL/TLS and then transmits it to the API interface of the flybook application, so that the flybook application can forward the corresponding flybook card information to the designated user within the configuration authority range after decrypting.

10. A data interaction method based on a fly book card message direct trigger Jira workflow, the method comprising:

Monitoring a specific event through webhook configured at Jira platform, and sending event data to a local server when the specific event is monitored;

receiving event data from a Jira platform through a local server, converting the event data into a message format suitable for displaying a flying book card to generate flying book card information, and sending the flying book card information to a created flying book application;

And forwarding the received flying book card information to a designated user within the configuration authority range by the flying book application so that the corresponding user can enter the Jira platform for corresponding operation through the flying book card information.