ConnectALL interacts with VersionOne via its ReST API.
Supported Entity Types
Sync Issue Linking
ConnectALL's Dynamic Linking option allows a user to link two existing records, instead of creating a duplicate, by specifying the destination record ID in a custom field. Refer to Dynamic Record Linking feature for more information. ConnectALL's VersionOne adapter is able to perform the dynamic linking based on a readable ID as well as with VersionOne's internal record ID.
Let's say you are synchronizing VersionOne Backlog Items to Jira stories via ConnectALL and you would like to dynamically link a VersionOne record "B-01234 (Story:56789)" to a Jira record "VO-123". For this, you can enter "Story:56789" in a custom field like "CA_External_ID" in Jira and map it to the "ID" field in VersionOne as shown below.
Alternatively, you could enter the readable id "B-01234" in the "CA_Enternal_ID" field and map it to the "Number" field in VersionOne for performing the Dynamic linking.
VersionOne Task (Parent-Child Linking)
The Task type in VersionOne cannot be created directly. For each created task, a corresponding parent record is mandatory. Hence, when a task application link is configured in ConnectALL, the corresponding parent application link (either Story/Defect/Issue) has to be configured for the sync to work. Any other special field mapping is not required.
VersionOne Test Sync (Parent-Child Linking)
The test asset in VersionOne cannot be created directly. For every test created, a corresponding parent record is mandatory. Hence, when a test application link is configured in ConnectALL, the Parent of the test needs to be identified. There are a couple of ways to define the Parent for the Test to be created in VersionOne.
Option 1: Map the Test.Parent field to a custom field in the destination application and enter the VersionOne OID of the record that the given test is to be associated with
Option 2: When synchronizing Tests with a destination application that has the similar parent-child structure like Jira Subtasks, then creating an Application Link to synchronize the Parent Type like Jira stories - VersionOne stories will enable ConnectALL to identify the Parent based on the relationships in the destination application.
Note: A step by step usecase guide for synchronizing VersionOne Test to ALM Testcases using Option 1 is documented in this How to article.
VersionOne Request Sync (Issue Linking)
The entity type "Request" in VersionOne can have an infinite number of Stories/Defects/Issues linked to it. Therefore, for it to work and create an application link in ConnectALL, the "Request" entity type in VersionOne and another application link for the corresponding Story/Defect/Issue in another platform must be there for linking to occur.
When creating a new Story/Defect/Issue by linking it to a "Request", ConnectALL can automatically detect the newly created record from VersionOne and sync it to the corresponding application and create links.
When we try to assign an existing Story/Defect/Issue by linking it to a "Request", then for ConnectALL to read the modified record from VersionOne it is mandatory to edit the linked Story/Defect/Issue in VersionOne. Due to the limitation in the ReST API, this modification is required.
Similarly, when the user tries to add attachments/comments, it is mandatory to edit the corresponding record (any field) in order for ConnectALL to detect the updated changes.
VersionOne PortfolioItem Sync
In VersionOne we can create a PortfolioItem as a separate entity or even we can create a Parent-Child hierarchy.
For example: A PortfolioItem of category Initiative can be created as a child under another PortfolioItem of category Feature and vice versa as listed below.
- All PortfolioItem Category is supported by ConnectALL
- Parent-Child hierarchy is only for PortfolioItem (i.e. both Parent and Child will be created as a VersionOne PortfolioItem)
- Similar to other entities, to sync only a PortfolioItem, create an application link by choosing the entity, and the category can be selected under field configuration.
- To create the parent-child hierarchy as listed above, map the field "Parent" in the field configuration and either pass the value to this field by mapping it to _CONSTANT, or map it with any appropriate field on the other application so that value is passed to this "Parent" field dynamically. In this way, the PortfolioItem item being created will be created under the specified Parent as a child record (as displayed above).
- In the below example, all the PortfolioItems getting created will be created under the Parent PortfolioItem of Id Epic:11165
Jira-VersionOne URL Link
To sync the Jira URL as a link in VersionOne, map the _URL field from Jira fields to the Hyperlink field from VersionOne as follows. This will create an URL link in VersionOne.
Similarly, to sync the VersionOne URL to the destination application, map the _URL field from VersionOne fields to any custom text field on the destination application. In the below example, the _URL field of VersionOne is mapped with a custom field on Jira.
This is how VersionOne URL is synced in Jira. (For security reasons, the actual test URL is obscured.)
VersionOne Link Types
The following table provides the list of ConnectALL supported VersionOne Link Types for each entity.
|ConnectALL Processing Entity Type||Linked Entity Type||Link Type|
|Any other Entity||Dependants|
|Any other Entity||Dependants|
|Any other Entity||BlockedPrimaryWorkitems|
|Any other Entity||PrimaryWorkitems|
|Any other Entity||Subs|
Whenever we try to sync to a VersionOne field from a multi-select field of another application, then the last updated value will be selected and be updated in the drop down.
For example: If a multi-select Jira Version field is mapped with the VersionOne Version drop down field, then the last added value in Jira Version will be chosen in the VersionOne drop down.
VersionOne Team Rooms
In VersionOne, when an entity is created/mapped as part of the Team Room, then to change the Status of the entity, ConnectALL takes care of updating the correct team status by the usual Status field value mapping. When doing the value mapping of a specific Status as shown below, it displays multiple supported Status value id as shown below. No external configuration is required for ConnectALL to handle the team status.
VersionOne Expression(s) can be synced to the destination application as Comments and vice-versa. Map the "Comment" field of VersionOne as shown in the screenshot below to sync the Expression(s)/Comments.
ConnectALL can sync expressions/comments only against the first conversation/expression created in VersionOne or synced to VersionOne.
Time Difference Configuration
To know how to calculate the time difference, and configure it in the ConnectALL UI, read the topic Time Difference Configuration.
Automatic User Value Mapping
ConnectALL supports Automatic user value mapping for ServiceNow. Below is a screenshot that illustrates this; where
For more information on automatic user value mapping and to find out how it works, click here.