A typical use of ConnectALL is to create an automation 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 automation that will sync multiple projects for a given issue type. Such Multi-Project support make senseonly for those applications that have something like the concept of projects.


You will be able to convert a single-project automation to a Multi-Project supported automation. When you convert, use the same template project that was configured in the single-project automation to ensure smooth synchronization. But note that this is not the same as combining multiple automations into a single Multi-Project automation, which is not supported. The best way to manage multiple individual automations is via the Bulk link configuration feature.

Configuring automation 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. The field configurations on the Field Mapping screen will be pulled based on the template project you select. 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. Choose the template project from the dropdown. Repeat for the other application if Multi-Project is enabled for both.

  3. In the Field Mapping tab, map the Project field for the Multi-Project supported application. See here for more details on field mapping if needed.

  4. Once the field configuration is added between the Project fields, click the Modify tab to add value mappings for the required projects. See here for more details on value mapping if needed.

  5. Click Save Mappings and save the automation. 

Configuring automation between Multi-Project Supported Application and Regular Application

You can configure an automation 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. Select the template project from the dropdown under the Template Project field for the application set to Multi-Project. This field is grayed out for the single project.

  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 automation.

Moving Issues

Moving issues is a popular term that you would have come across in applications such as Jira and Azure DevOps. 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, Azure DevOps 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
    • 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 automation. 

If you need to achieve multi-project functionality using the PUSH service, learn more 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 automation for all the projects created from VersionOne, to Jira with multiple projects. 

Configuring Many-To-One Project Mapping

ConnectALL allows you to set up the many-to-one mapping of projects unidirectionally. This is useful in scenarios where you have multi-project automations 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 image and discussed further below.

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

Trainee-1   —> Training-Admin

Trainee-2   —> Training-Admin

Trainee-3 <—> Training-Admin

Trainee-4 <—> Trainee-6

Trainee-5  <— Trainee-7

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