ALM Management

Why Integrate an ALM?

AutoRABIT can connect to popular Application Lifecycle Management (ALM) platforms—Jira, Azure DevOps, IBM RTC, CA Agile Central (Rally), and VersionOne—to:

• Surface active and inactive sprints in one place.

• Sync work-item status automatically during merges, commits, and CI jobs.

• Enforce release governance with smart-commit patterns and webhook automation.

The ALM Management page (added in ARM 21.6) lives under Admin and lets you register new ALM connections, set integration rules, and manage repository mappings.

Registering an ALM

1. Log in to ARM as an admin.

2. Navigate to Admin > ALM Mgmt.

3. Click Register ALM on the ALM Mgmt. screen.

1. Configure the following settings:

   1. For IBMRTC, CA Agile Central, VersionOne, and Azure DevOps:

      • ALM Name: Enter a name for your ALM connection.

      • ALM Type: Select the ALM type.

      • ALM URL: Add the ALM server URL.

      • Credentials: Specify your credentials. Refer to the Credential Manager section for more info on creating and storing your credential inside ARM.

      
   2. For JIRA:

      

      • ALM Name: Enter a name for your ALM connection.

      • ALM Type: Select JIRA.

      • Access Type:Select one of the following:

        • Standard: Add the ALM URL and specify your Credentials.

        • OAuth: Select the access type as OAuth, and click on Validate & Save. You will be redirected to the ALM's website to authenticate your credentials and grant permission.

1. Click on Test Connection to authenticate your credentials.

2. Click Save.

1. Once your ALM is registered successfully, you can view it in the ALM List menu.

2. Use the AR Comments toggle button to turn off the Jira comments from AR. By default, the Jira comments are ON for newly registered and existing ALMs.

3. Use the Access Type drop-down list to switch between Standard and OAuth. Click on Re-Authenticate if your credentials have expired. This is only applicable to Jira ALMs.

For Salesforce as ALM

1. Log in to ARM as an administrator.

2. Navigate to Admin › ALM Mgmt.

3. Click Register ALM.\

   
4. Fill the form:

   1. ALM Name – friendly label.

   2. ALM Type – choose the platform.

Field Mapping for Work Item Updates in Salesforce

To enable AutoRABIT to update your Work Items (e.g., User Stories or Bugs) based on commit actions, please configure the following fields from your registered Salesforce Org: \

c. Salesforce Org Select the Salesforce Org from your list of registered orgs where the work item updates should be applied.

d. Custom Object / Work Item Type Choose the Custom Object that represents your Work Items (e.g., User_Story__c, Bug__c). This is where the Work Item ID will be updated.

e. Title Field Map the field that represents the project or feature to which the Work Item belongs. This is usually a custom text field like Project__c.

f. Assignee Field Select the custom field that stores the user assigned to the Work Item. This allows AutoRABIT to track ownership of the User Story or Bug.

g. Status Field Choose the custom field that reflects the current status of the Work Item (e.g., New, In Progress, Ready for QA, Closed). This field can be updated automatically based on the commit action.

h. Comment Field Select the custom field where commit-related comments should be posted. The system will populate this with detailed commit information after the action is performed. 1. Select Post Commit Action Under the Post Commit section, select:

2. Update ALM Work Item Status

Configure ALM Fields Fill in the required fields to ensure the correct ALM Work Item is updated post-commit:

ALM Type: Choose the integrated ALM tool (e.g., Salesforce).

• ALM Label: Select the applicable label for this commit operation.

• ALM Project: Pick the project or module name (e.g., User Story, Bug).

• ALM Work item: Select the Work Item ID you wish to update.

• ALM Work Item Status: Choose the new status you want to set (e.g., To Do, In Progress, Done).

• Current Status: Shows the status of the item (e.g., In Testing).\

  

Complete the Commit Click Commit after configuring all required fields. The system will:

• Perform the commit action.

• Post-commit, automatically update the ALM Work Item to the new selected status.

• Add relevant commit information to the comment field (if configured), including metadata, user, and validation results.

Sample Outcome Post Commit Comment Format: The selected Work Item will reflect the updated status in your ALM tool and include commit metadata like:

[Message] [************]# Saas tool Integration-2

[Repository] **********;

[Branch] 18235_test

[Revision] 3637289

[Committed by] ******@.com

[Committed metadata members] {Apex Class=[A000, A0000]}

[Pre-validation Results]

Label Name = **********.**

Apex Test Results = NA

Static Analysis = NA

Deployment Org = NA

Overall Validate Deployment Status = NA

Approved By = .@***.com

Integration Settings

By default, we do not display the work items from the inactive sprints; however, if you want to view the hidden items, you can do so from this section.

1. Select the following checkbox to view the work items from the inactive sprints: Display work items from inactive sprints (we recommend setting up global filter criteria if are enabling this)

2. Enable global filter criteria on work items: This checkbox allows you to specify filter criteria.

   • You can select which fields are displayed by selecting the necessary column/field. However, you can refine the list of work items displayed by configuring a worklist filter.

   • Repeat these steps for each field if you want to set filter criteria.

3. Click Save Settings.

Smart Commits

Define the pattern AutoRABIT uses to parse work-item references in commit messages—for example:

git commit -m "\[PROJECT-123] add README"

• Enable auto update on webhook – reveals a webhook URL you can add to your VCS so external commits update the ALM automatically. See setup guides here.

• Optionally sync external smart commits made outside AutoRABIT.

Repository Mappings

Repository mappings let AutoRABIT update ALM work-item status after a successful merge.

1. Choose the version-control Repository.

2. Select the Source Branch (click Register here if it’s missing).

3. Pick the ALM Project.

4. In ALM Work Item Status, define:

   • Work Item Type

   • Current status

   • Target status after merge

   
5. Click Save.

1. Suppress ALM email noise by listing addresses in Notify exception status updates to.