A typical use of ConnectALL is to create an application link for each "Project" and "Issue type" combination. However, if you have a large number of projects with the same field templates then ConnectALL will let you configure one application link that will sync multiple projects for a given issue type. Such Multi-Project support make sense, naturally, only for those applications that have something like the concept of projects.


  • As of version 2.10.0, you no longer have to enable the Multi-Project support feature — as it is automatically enabled.
  • You will be able to convert a single-project app-link to a Multi-Project supported app-link. When you convert, use the same template project that was configured in the single-project application link to ensure smooth synchronization. But note that this is not the same as combining multiple app-links into a single Multi-Project app-link, which is not supported. The best way to manage multiple individual application links is via the Bulk link configuration feature.

Configuring application link for multi-project synchronization

  1. Select the option Multiple from the project drop-down list.

  2. Select the project from the Template Project drop-down list (above image). The field configurations will be pulled based on the template project information. Only when you enable the Multi-Project configuration feature (by selecting Multiple for the project), you will be able to see the project field in the field configuration grid for mapping.
  3. In the Field Mapping tab, map the Project field for the Multi-Project supported application.

  4. Once the field configuration is added between the Project fields, add value mappings to map the projects. 

  5. Click Save Mappings and save the app-link. 

Important Info — Template Project Selection in Version and Later Versions

Starting from version, ConnectALL allows you to select a template project from a drop-down list field or Search List field (depending upon the application). In the below image, the app-link is between Atlassian Jira and VersionOne. Notice the drop-down list field that is displayed for Atlassian Jira and the Search List field displayed for VersionOne.


Configuring application link between Multi-Project Supported Application and Regular Application

You can configure an app-link between a Multi-Project supported application (like MicroFocus ALM, VSTS etc.) and a regular application (like Salesforce, Tricentis Tosca etc.) This can be achieved by mapping the Project field from the Multi-Project supported application and a drop-down field on the Regular Application and map the values. Based on the selected values from the drop-down, the records will be synchronized to the appropriate project.

  1. Select the Multiple option on the Multi-Project supported application and the specific project on the Regular application.

  2. Key in the template project info in the Custom Configurations section of the Entity Mapping tab for the Template Project field.
  3. Map the project field with a drop-down field in the other application. 
  4. Once the field configuration is added between the Project field and the drop-down field, then add the value mapping. 


  5. Save the app-link.

Moving Issues

Moving issues is a popular term that you would have come across in applications such as Jira and AzureDevOps. In Jira, if you have created an ‘Issue’ selecting a wrong project or an ‘Issue Type’, you will be able to move that issue to another project or issue type. Similarly, AzureDevOps also allows you to move work items that belong to the wrong work item type (WIT) or an incorrect project.

  • Moving of issues between the project in the Multi-Project configuration is only supported for the below applications in ConnectALL:
    • Atlassian Jira
    • Azure DevOps (from version 2.10.17)
    • VersionOne
  • To enable the 'Move issue' feature in Jira, please look at the 'Move issue' topic in the "Atlassian Jira" page.
  • Make sure to have the bi-directional option selected for this field. The bi-directional mapping is mandatory for this feature to work correctly.
  • If you change the project of an issue, that issue will automatically sync with the new project's destination in the app-link. 

If you need to achieve multi-project functionality using the PUSH service, click here.

Example Usecases

ALM <=> Jira

The testing team uses a single project in ALM for tracking defects, and the development team accesses multiple projects for tracking bugs. When a testing team raises a defect in ALM the user will select to which Jira project this defect is related to, and ConnectALL will sync the bug to the project selected by the user.

Jira <=> Jira 

Jira Federation, where the users create bugs, and stories in the external Jira instance, which will be synchronized to the corresponding project in the Internal Jira.

VersionOne <=> Jira

Users want to have one application link for all the projects created from VersionOne, to Jira with multiple projects. 

Configuring Many-To-One Project Mapping

Starting from version, ConnectALL allows you to set up the many-to-one mapping of projects unidirectionally. This is useful in scenarios where you have multi-project app-links and you will now be able to map multiple projects to a single project. This is explained through the below example where you have a Project <> Project field mapping and the linked value mapping for this Project field has multiple project mappings. This scenario is illustrated in the below images and discussed further below.

The above Value Mapping screen (right sided image) has the following many-to-one project mappings:

Project A   —> Project 1

Project B   —> Project 1

Project C <—> Project 1

Project D <—> Project 2

Project E  <— Project 3

  • In the above mappings, Project A and B both are mapped to Project 1 unidirectionally, and Project C is also mapped to Project 1, but bi-directionally.
  • Let's say there is a Project F and you want to map Project 1 to it as  Project F <— Project1. Such a mapping will not be possible. The reason is that Project 1 is already mapped in a bi-directional way to Project C and in a left-to-right with projects A and B.
  • Also, if you are trying to map Project F to Project 1 (Project F <—> Project 1 (bi-directionally)), it is not possible due to the presence of Project C <—> Project 1 bidirectional mapping.
  • If you have mapped Project A —> Project 1, where a record gets synced into Project 1, and when you update that record in Project 1, the record will get updated in Project A as well.
  • The direction of the mapping decides the creation and update of records.