Uranus Ding Talk for Jira
- Carmen Wu
- Aliven
2024年7月
- 1 1 Technical Programme
- 2 2 Operate Instructions
- 2.1 2.1 Operate Environment
- 2.2 2.2 Plugin Installation
- 2.2.1 2.2.1 Prepare for JIRA Plugin Installation
- 2.2.2 2.2.2 Ding Talk Self-built Application
- 2.2.2.1 2.2.2.1 Login Ding Talk open platform
- 2.2.2.2 2.2.2.2 Create an enterprise self-built application for Ding Talk
- 2.2.2.3 2.2.2.3 Get the credentials and basic information of the self-built application: corpId, agentId, appSecret and appKey
- 2.2.2.4 2.2.2.4 Add application capabilities
- 2.2.2.5 2.2.2.5 Login and share
- 2.2.2.6 2.2.2.6 Permission configuration of self-built application
- 2.2.2.7 2.2.2.7 Security settings
- 2.2.2.8 2.2.2.8 Version release of enterprise self-built application
- 2.2.3 2.2.3 JIRA Ding Talk Plugin Configuration
- 3 3 Function Display
1 Technical Programme
1.1 Plugin Overview
JIRA Ding Talk plugin (URANUS DINGTALK) is to connect JIRA and Ding Talk products.
In Ding Talk 's application (mobile and PC), Ding Talk account can be associated with JIRA account, so that Ding Talk users can view, process, and create new JIRA ISSUE information, and the associated issue information can be notified to the relevant Ding Talk users in real time.
In the JIRA product, Ding Talk users can also log in to JIRA to view relevant information by scanning the Ding Talk code.
2 Operate Instructions
2.1 Operate Environment
JIRA Ding Talk plugin (URANUS DINGTALK) supports JIRA (8.0.0) or above.
2.2 Plugin Installation
2.2.1 Prepare for JIRA Plugin Installation
Prepare the downloaded URANUS DINGTALK plugin package, and click the button 
Fig. 2.2.1.1 System Management Menu
Click “Manage Applications” to enter the application management page as shown in Figure 2.2.1.2. At this time, a second password confirmation pop-up will appear, please enter the password of the currently logged-in JIRA account to proceed to the next step.
Fig. 2.2.1.2 Manage Applications
Click "Manage Applications" in the left menu bar to enter the plug-in installation step.
2.2.2 Ding Talk Self-built Application
2.2.2.1 Login Ding Talk open platform
Access Address:
https://open-dev.dingtalk.com/
2.2.2.2 Create an enterprise self-built application for Ding Talk
Login Ding Talk developer background address:
https://open-dev.dingtalk.com/?spm=ding_open_doc.document.0.0.6bc33e7cjsrfB3&hash=%23%2F#/
On the application development page, select internal application > Ding Talk application, and then click create application. As shown in the figure below:
Fill in the name and description of the self-built application.
2.2.2.3 Get the credentials and basic information of the self-built application: corpId, agentId, appSecret and appKey
2.2.2.4 Add application capabilities
1）Add Web Applications
2）Fill in web application information
Fill in baseurl+/plugins/servlet/callback/ddquerycode callback5/auth, all three are the same.
baseUrl is obtained at JIRA.
2.2.2.5 Login and share
Fill in baseurl+/plugins/servlet/callback/ddquerycocallback5/auth at the login and share place.
baseUrl is obtained at JIRA.
2.2.2.6 Permission configuration of self-built application
Click Permission Management, assign permissions, and select all employees within the scope:
2）Open privileges、Privilege information:
Personal cell phone number information
Read permission of personal information of address book
Basic permissions required when using SNS API
E-mail and other personal information
Read permission of address book department information
Read permission of member information
Read permission of address book department members
Read permission of external contacts of the enterprise
Access to industry address book information
Use enterprise API basic rights
Basic permission to get user access credentials of Ding Talk open interface
Ding Talk group basic information management privileges
Permission to use Ding Talk project management related interfaces
Permission to send messages from bots in the enterprise
Read permission of basic information of Ding Talk Group
Permissions to send messages for service groups
Service window send message permission
As shown in the following figure:
2.2.2.7 Security settings
Configure server exit Ip: IP of the server.
Redirect URL:
BaseUrl+/plugins/servlet/callback/ddQueryCodeCallbackH5/auth,
BaseUrl+/plugins/servlet/callback/ddLoginCallbackH5/auth
2.2.2.8 Version release of enterprise self-built application
In Version Management and Publishing, click Create Version to publish this revision.
Apply to all employees, fill in the version number and update instructions and click Save. After saving, click Apply for Online Release.
2.2.3 JIRA Ding Talk Plugin Configuration
After the JIRA plugin is installed, you can see Ding Talk plugin URANUS DINGTALK on the JIRA plugin management page.
2.2.3.1 Ding Talk configuration interface
Click DingTalk Configure to enter configuration interface.
Global Configuration
1）Administrator privilege group：Select to configure a group，the people in this group can make changes to the pinning configuration.
2）Ding Talk ID (corpId) Enterprise cropID
3）Ding Talk application ID (agentId) Ding Talk application id
4）Ding Talk application key (appSecret) Enterprise application secret
5）Ding Talk application key (appKey) Enterprise application appKey
6）Whether or not to enable Ding Talk code scanning login When it is enabled, you can login to JIRA through Ding Talk code scanning
As shown in the figure below:
Function Configuration:
When the scan code login function is turned on, the QR code authorized by Ding Talk will appear in the login interface of JIRA, so you can log in by using the scan code of Ding Talk application.
1）Log in by scanning the code. If there is no user's binding, the login will fail.
2）If scan code login is turned on, JIRA user function will be created when there is no JIRA user. A new JIRA account will be created and bound to the nail account of code scanning.
3）If the default permission group is turned on, the user will be placed under the specified group when the account is created.
2.2.3.2 Ding Talk user binding
Click Ding Talk User Binding of the plugin to enter the Ding Talk User Binding interface of JIRA. The left side of the pin user binding interface shows the users who are not bound to JIRA and Ding Talk, while the right side shows the users who are bound to JIRA and Ding Talk.
Three operation buttons in the center：
1）Default Binding Button: Click the Default Binding button, the plugin will match the email account of the JIRA user with the email account of the Ding Talk user, and if it is the same, then the user will be bound by default.
2）New Binding Button: Select JIRA users and Ding Talk users on the left side, then click New Binding button to bind users manually.
3）Empty Binding Button: Click the Empty Binding button to empty the bound users.
4）On the right side of the bound user, there is also a button to delete the bound user, click Delete to delete the bound user.
As shown in the figure below:
3 Function Display
3.1 JIRA Scan Code Login Display
When the scan code login function is turned on, the QR code authorized by nailing will appear in the login interface of JIRA, so you can log in by using the scan code of Ding Talk application.
1）Log in by scanning the code, if there is no user's binding, you will not be able to log in.
2）If scan code login is turned on, JIRA user function will be created when there is no JIRA user. Create a new JIRA account and bind it with the Ding Talk account that scans the code.
3）If the default permission group is turned on, the user will be placed under the specified group when the account is created.
3.2 User Binding Interface
3.3 Ding Talk Self-built Application Bot Tips Interface
3.4 Terminal Browsing Interface
3.5 Question Browser
1）Click the Question button to enter the Question Browser screen.
2）Click on a question to edit it, modify it, upload attachments and comments, etc.
3）Click the + button to create the question.
3.5 Viewing Personal Information
Click on the “My” button to display your personal information, or to prevent JIRA issues from being updated by sending a message.