ALM Management

Important Note: The actions described here are available only to Org Administrators. General ARM users cannot access 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.

Register an ALM

  1. Log in to ARM as an administrator.

  2. Navigate to Admin › ALM Mgmt.

  3. Click Register ALM.

    Register ALM button on the ALM Mgmt screen

  4. Fill the form:

    IBM RTC, CA Agile Central, VersionOne, or Azure DevOps

    ALM registration form for Azure DevOps

    • ALM Name – friendly label.

    • ALM Type – choose the platform.

    • ALM URL – base server URL.

    • Credentials – select stored credentials (see Credential Manager).

    Jira

    Jira registration with Standard and OAuth access types

    • ALM Name – friendly label.

    • ALM Type – Jira.

    • Access Type –

      • Standard – enter ALM URL and credentials.

      • OAuth – pick OAuth, click Validate & Save, and grant access in the Jira pop-up.

  • Jira OAuth is supported for Cloud editions only.

  • OAuth appears only after you register Jira OAuth credentials in ALM Settings. Learn how here.

  • Access Token expires after 1 hour; Refresh Token after 90 days.

  1. Click Test Connection to verify access, then Save.

Troubleshooting Authentication An Authentication Failed error on the EZ-Commit screen often stems from VPN issues or outdated credentials.

  1. Go to My Account › ALM Configuration.

  2. Click Test Connection to re-authenticate.

  3. If it still fails, create a new credential and relink the ALM.

  1. The new ALM appears in the ALM List.

    • Toggle AR Comments to disable AutoRABIT-generated comments in Jira.

    • For Jira, you can switch Access Type between Standard and OAuth and click Re-Authenticate when tokens expire.

Limitation: Jira OAuth is Cloud-only and enabled on request. Contact [email protected] if you need it.

Integration Settings

Configure how work items are shown and filtered:

  1. Display work items from inactive sprints – include backlog items.

  2. Enable global filter criteria on work items – add column filters as needed.

  3. Click Save Settings.

Integration Settings panel

To remove a field’s filter, click the trash-can icon next to the rule.

Smart Commits

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


git commit -m "\[PROJECT-123] add README"
Smart Commits pattern settings

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

  • A mapping is required for smart-commit syncing.

  • Status changes apply only to merges performed through merge requests.

  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

    ALM status mapping dialog

  5. Click Save.

Branches and repos you can’t access won’t appear in the dropdowns.

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

Notify exception status updates field
PreviousSearch and SubstituteNextGetting Set Up

Last updated

Was this helpful?