Issue Tracking Systems
- Copy Page Tree
- Emily Simon
- Muthu Sankaralingam
The Issue Tracking Systems page, which can be accessed through the Administration - Integrations - Issue Tracking Systems menu, allows management of integrations into third-party issue tracking systems. FlexDeploy currently provides out-of-box integration with Atlassian Jira, Redmine, Azure Boards, GitLab @since 5.6.0.1, and GitHub @since 5.6.0.1. You can define a custom implementation using either Java class or Groovy script. FlexDeploy reads ticket(s) from SCM commit message comments during build execution. As an example, if you use SVN when committing a change back to the repository, simply put the issue name in the commit comment (case sensitive). If using Git as your SCM, make sure that the Git executable is installed on the FlexDeploy server and is accessible on the PATH. The Git executable version must be 1.7.9 or higher.
Here are the out-of-box issue tracking systems. To configure, click the name or select a row and click the Edit button. FlexDeploy comes with a Java Implementation to integrate with Jira, Redmine, or Azure Boards, and a Groovy implementation to integrate with GitLab or GitHub. You are not allowed to change the implementation class and change or add new properties for these out-of-box issue tracking systems. You can create an additional Issue Tracking Systems as necessary using the Create button.
.png?version=1&modificationDate=1608555274388&cacheVersion=1&api=v2&width=1400&height=302)
Terminology
| FlexDeploy Term | Description |
|---|---|
| Issue Tracking System | Defines the system used to track the tickets for specific projects or applications using patterns or custom rules. Various providers are available out-of-box, but you can add one or more custom systems using either Java or Groovy script implementation. |
| Issue Tracking System Instance | Instance represents the physical connection details of the Issue Tracking System. |
| Property | Properties are used to define the necessary inputs needed to connect to the system. |
| Status | Status is used to measure the progress of work done, as well as to represent the current stage of the issue. |
Let's review each topic in detail now.
- If you want to configure an issue tracking integration for an out-of-box provider, use the Configure Issue Tracking Systems to make any changes to properties, status, or other configurations
- For adding a custom issue tracking system, follow the steps described in Custom Issue Tracking System
- Once the Issue Tracking System properties are configured, create an instance to integrate with FlexDeploy. Configure Issue Tracking System Instance shows how to set up the instance by providing the server and credential information
- The next steps after creating and testing the instance is to Configure Project for Issue Tracking. Here you can choose any configured issue tracking system instance and define how you want to integrate with the system
- Tickets are associated when a project is built. Associate Issues with Build describes how FlexDeploy processes the tickets
Here is the setup needed for Redmine.
Related content
- style