Synchronize your ALM Octane workspaces with your ALM or JIRA projects to view and update your releases, backlog, and defects in both endpoints.
ALM Octane Synchronizer enables administrators to configure synchronization between ALM Octane and ALM or JIRA from the ALM Octane settings area.
When you synchronize with ALM, your ALM Octane user stories, features, and epics are all synchronized as requirements in ALM. When you synchronize with JIRA, your ALM Octane user stories and features are synchronized as user stories and epics in JIRA. Epics in ALM Octane are not synchronized in JIRA.
ALM Octane Synchronizer checks ALM Octane and ALM or JIRA for recent updates in the synchronized items, and updates the other endpoint accordingly. You can configure the direction in which changes are synchronized between the endpoints: from ALM or JIRA to ALM Octane, from ALM Octane to ALM or JIRA, or in both directions.
Before setting up synchronization you should be aware of the following:
Rules. When synchronizing with ALM, ALM Octane rules are activated during synchronization. For example, if setting a value in one field makes another required, synchronization will fail if the endpoint does not provide a value for the newly required field.
When synchronizing with JIRA, ALM Octane rules are not activated. For example, if a field is mandatory in ALM Octane and missing in JIRA, the JIRA entity is still copied to ALM Octane.
Workflow. When synchronizing with ALM, workflow procedures defined on either endpoint are ignored while creating and updating synchronized data. For example, the workflow normally prohibits updating a defect phase from New to Fixed. However, if Synchronizer needs to assign a Fixed value to a New defect, it will succeed.
When you add or delete a phase in the ALM Octane workflow settings, it takes up to 5 minutes to see the change in Synchronizer phase value mapping.
When synchronizing with JIRA, the Synchronizer creates "dummy" entities to learn the JIRA workflow for the status field, for the relevant issue types. As a result, Synchronizer supports status changes that should contain several status transitions to reach a desired state, because Synchronizer moves the entity to the correct phase or status according to the allowed path in the workflow.
Quality stories in ALM Octane are not synchronized.
Synchronization is defined by links, which you create and manage in the ALM Octane Synchronizer settings page. This settings page can be accessed only by Synchronizer Admin users.
Links are created between a pair of endpoints, namely an ALM or JIRA project and an ALM Octane workspace. You can set automatic synchronizations, or run manual synchronizations to synchronize records between the endpoints.
Each synchronization link defines the following:
The directions in which the endpoints are updated (ALM or JIRA > ALM Octane, ALM Octane > ALM or JIRA, or both).
The favorites used to find records with new data in each endpoint.
Creating multiple links
Each link synchronizes a specific entity type between a single ALM or JIRA project and a single ALM Octane workspace. Create separate links to synchronize defects, requirements, and releases between the same two endpoints.
You can create multiple links between a single ALM Octane workspace and multiple ALM or JIRA projects, even if the projects are stored in different versions of ALM or JIRA. In such a case, use ALM Octane favorites to separate the synchronized data inside the workspace.
To prevent data leaks between workspaces, ALM Octane Synchronizer does not support multiple links between a single ALM or JIRA project and multiple ALM Octane workspaces in the same site.
For details on the ALM and JIRA versions supported by ALM Octane synchronization, see Installation, setup, and synchronization.
Unless otherwise specified, references to ALM in this Help Center apply to all currently supported versions of ALM and Quality Center. Note that some features and options may not be supported in the specific edition of ALM or Quality Center that you are using.
If you synchronize with an ALM project that uses version control, ALM Octane Synchronizer conforms to the versioning rules. Changes made by the synchronization process are checked in with a comment:
Modified by Synchronizer.
During synchronization, ALM Octane connects to ALM using the credentials of an ALM user that you specify.
When synchronizing an entity that is checked out by that user, the entity is updated and checked in.
When synchronizing an entity that is checked out by a different user, the ALM entity is not modified.
If the synchronization is governed by the ALM Octane side, a synchronization error occurs due to the locked entity in ALM.
If the synchronization is governed by the ALM side, the ALM Octane entity is updated based on the last checked-in version on ALM.