Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

2024年7月

1 Technical Programme

1.1 Plugin Overview

JIRA FEISHU plug-in (URANUS FEISHU) is to connect JIRA and FEISHU products.

At the application of Feishu (mobile phone and PC), JIRA account can be associated with Feishu account, so that users of Feishu can view, process and create JIRA ISSUE related information, and the associated issue information can be notified to relevant Feishu users in real time.

In the JIRA, Feishu users can also log in to JIRA through the Flybook scanning code to view the relevant information.

2 Operating Instructions

2.1 Operating Environment

JIRA FEISHU plug-in (URANUS FEISHU) supports version JIRA (8.0.0) or above.

2.2 Plugin Installation

2.2.1 Preparation for JIRA plugin installation

Prepare the downloaded URANUS FEISHU plugin package, click the button in the upper right corner of the main interface of the system to pop up menu as shown in Figure 2.2.1.1

2.2.1.1 System Management Menu

Click "Manage Applications" to enter the application management page as shown in 2.2.1.2, and a second password confirmation will pop up. Please enter the password of the currently logged in jira account to proceed to the next step.

2.2.1.2Management Application Page

Click "Manage Applications" on the left menu bar to enter the plugin installation procedure.

2.2.2 Feishu Self-built Applications

2.2.2.1 Log in to the Feishu Open Platform

Access Address:

https://accounts.feishu.cn/accounts/page/login?app_id=7&no_trap=1&redirect_uri=https%3A%2F%2Fopen.feishu.cn%2Fapp%2Fcli_a68b9186c698d00b%2Fwebpage

2.2.2.2 Create an enterprise self-built application for Feishu

Access Address: https://open.feishu.cn/app/

Create a self-built application as shown below:

1). Fill in the name and description of the self-built application

2.2.2.3 Getting credentials and base information for self-built apps appId and App Secret

2.2.2.4 Add application capabilities, robot and web application functions

Configure the web application

2.2.2.5 Clicking on the web application to configure the web application

Configuring the desktop home page and mobile home page

Desktop homepage configuration:

https://open.feishu.cn/open-apis/authen/v1/authorize?app_id=cli_a68b9186c698d00b&redirect_uri=http://192.168.10.44:2990/jira/plugins/servlet/callback/feishuCallback/desktop/auth&scope=contact:user.id:readonly

Mobile homepage configuration:

https://open.feishu.cn/open-apis/authen/v1/authorize?app_id=cli_a68b9186c698d00b&redirect_uri=http://192.168.10.44:2990/jira/plugins/servlet/callback/feishuCallback/auth&scope=contact:user.id:readonly

Note that the replacement of the relevant parameters url (to replace the access address to JIRA address only need to change the ip and port on the line, also supports the domain name) and app_id (to create the enterprise self-built app app id) information . Choose to open in a new tab in Feishu as shown below:

2.2.2.6 Security settings

Click on the security settings of the self-built application and set the redirection url.

Add url: To replace the ip and port (http://192.168.10.44:2990/jira) with your own domain name.

http://192.168.10.44:2990/jira/plugins/servlet/callback/feishuCallback/desktop/auth

http://192.168.10.44:2990/jira/plugins/servlet/callback/feishuLoginCallback

http://192.168.10.44:2990/jira/plugins/servlet/callback/feishuCallback/auth

As shown in the figure below:

2.2.2.7 Permission configuration for self-built applications

1)Add the following 9 permissions to the permissions management api permissions:

1. Read address book as an application.

2. Access departmental organization information

3. Access to basic department information

4. Access basic user information

5. Access user's mailbox information

6. Access user's cell phone number

7. Send messages as an application

8. ID Access user ID by phone number or Email

9. user ID Access user ID

As shown in the figure below:

2)Configure permission ranges at Data Permissions

2.2.2.8 Version release of enterprise self-build application

In the Versioning & Publishing section, click Create a Version to publish the current changes.

Fill in the version number and update instructions and click Save. Once saved, click Request Online Release.

2.2.3 JIRA Feishu Plugin Configuration

After the JIRA plugin is installed, can see the Feishu plugin URANUS FEISHU on the JIRA plugin management page.

2.2.3.1.1 Feishu Configuration Interface

Click Feishu Management to enter the Feishu configuration interface, there are two configurations in: one is the global configuration, and the other is the function configuration.

  1. Global Configuration:

1)Administrator permission group: choose to configure a group, the people in this group can change the configuration of the Feishu.

2)Feishu application id: create the application id of the Feishu enterprise self-built applications.

3)Feishu application key: create the application key of Feishu enterprise self-built application.

4) Whether to turn on Feishu scanning code login: When this function is turned on, an interface that can scan code through Feishu will appear in jira login interface.

As shown in the figure below:

  1. Function Configuration:

1) When a Feishu user scans the code to log in, if the corresponding jira account does not exist, is it allowed to create the corresponding jira account. When jira users are allowed to be created, the default password is the user's cell phone password. eg: +86134********. When the user's cell phone number is empty, the user cannot be created.

2) Default permission group when creating jira account

When Feishu user scans the code to login, if the binding information does not exist, is it allowed to bind the jira account by itself. When binding is allowed, it will go to auto-binding based on the user's email. When no matching email is found, the binding fails.

As shown in the figure below

2.2.3.1.2 Feishu User Binding

Click the plugin of Feishu User Binding to enter jira's Feishu User Binding interface. The left side of the Feishu user binding interface shows the users who are not bound to jira and Feishu, and the right side shows the users who are bound to jira and Feishu.

There are three buttons in the center:

1) Default Binding Button: Clicking the Default Binding button, the plugin will match the e-mail account of the jira user with that of the Feishu user, and if they are the same, the user will be bound by default.

2) New Binding Button: Select the jira user and the Feishu user on the left and click the New Binding button to bind the user manually.

3) Clear Binding Button: Click the Clear Binding button to clear the binding.

4) There is also a button to delete a bound user on the right side, click Delete to delete the bound user.

As shown in the figure below:

3 Functions

3.1 JIRA Scan Code Login

The QR code of Feishu authorization login will appear in the login interface of jira when the code scanning login function is enabled, use the Feishu app to scan the code to login.

1) Feishu code scanning login, if there is no user binding, it will not be able to login.

2) If turn on the code scanning login, the jira user function will be created when the jira user does not exist. Then a new jira account will be created and bound to the Feishu account for scanning.

3) If enable the default privilege group, then when create an account, you will also put the user under the specified group.

3.2 JIRA Configuration Interface

3.3 User Binding Interface

3.4 Feishu Self-built Application Robot Prompt Interface

3.5 PC Browsing Interface

3.6 Phone Browsing Interface

3.7 Phone Issue Browsing Interface

1) Click on the Issue button to enter the Issue Browser.

2) Click on the question button to edit the issue, modify the issue, upload attachments and comments, etc.

3)Click the "+" plus button to create an issue

3.8 Check Personal Information

Click the "My" button to display personal information, and can also turn on or off the push message function.

  • No labels