...
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 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.
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. 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 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. |
...
- If you want to configure Jira or Redmine, or Azure Boards 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
- Tickets are associated when a project is built. Associate Issues with Build describes how FlexDeploy processes the tickets
...