Issue Tracking Systems

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, and Azure Boards. You can define 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 is the out of box issue tracking systems. To configure, click the name or select a row and click the Edit button. FlexDeploy comes with Java Implementation to integrate with Jira, Redmine, or Azure Boards. 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 System as necessary using the Create button.


FlexDeploy TermDescription
Issue Tracking SystemDefines the system used to track the tickets for specific projects or applications using patterns or custom rules. Jira, Redmine, and Azure Boards are available out-of-box, but you can add one or more custom systems using either Java or Groovy script implementation.
Issue Tracking System InstanceInstance represents the physical connection details of the Issue Tracking System.
PropertyProperties are used to define the necessary inputs needed to connect to the system
StatusStatus 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.

Here is the setup needed for Redmine.

The following macros are not currently supported in the footer:
  • style