Follow

Project: Integrations: ALM

Background: Understand: ALM Integrations 

ALM Integrations

Permission required: Project Roles->Integration->Sync with ALM tools

The ALM integration page lists all active integrations. Users can add new integrations by clicking on the "Add ALM connection button"

Add ALM Connection

To add a new ALM connection, you must select a "Parent" connection which administrators setup using the System->Integration menu. If nothing appears in the "Parent" drop-down box, please contact your administrator to configure a connection.

The "Name" field allows you to name the ALM integration, in case you are synchronizing with multiple ALM tools.

ALM Connection Options

Based on the ALM integration you select, you have different options:

Sync Frequency: The "Sync Frequency" field appears for all ALM tools.

  • "Manually" means you need to click on the corresponding "Synchronize" button in the Integration->ALM Integrations page. The other options specify how frequently SD Elements will synchronize automatically.
  • In most real-world cases, "Daily" is sufficient - however you may wish to select a more frequent interval if development moves quickly in your organization.
  • NOTE: The more frequently you run synchronization, the greater the performance impact on both the SD Elements & ALM servers. This is generally only a concern for large organizations running many synchronizations at once.

ALM-Specific Configuration

The table below describes the different options for each supported ALM.

Mingle
  • Project Identifier
Trac
  • Milestone
GitHub
  • Repository Name
Pivotal Tracker
  • Project Name
Microsoft Team Foundation Server (TFS)
  • Use the Windows Integration Console
 

JIRA

 
  • Project Key: The JIRA Project Key.
  • Parent Issue: (optional) An existing issue identifier under which new sub tasks are created.
  • Custom Fields: (optional) Any non-default custom fields that are required when creating an issue in projects. These fields must be provided as a JSON dictionary similar to the following:

         {"custom_field_name": "field_value"}

         The custom_field_name value is the title of the field you see in the user interface. For example, use "Component/s" for the component field and "Affects Version/s" for the affected version field.

CA Agile Central (Rally)

  • Project: The name of the CA Agile Central (Rally) project
  • Workspace: (optional) The name of the Workspace.
  • Custom Fields: (optional) Any non-default custom fields that are required when creating an issue in projects. These fields must be provided as a JSON dictionary similar to the following:
        {"custom_field_name": "field_value"}
  • Alm parent Issue: (optional) An existing "Story" identifier under which new "Tasks" are created. This field is only applicable if the parent connection is setup to create "Task" issues.

        Example, to sync CA Agile Central (Rally) tasks under user story US617:

  • Choose a Rally Connection having "Task" as its "Issue Type"
  • Set the value of "Alm parent issue" to "US617"

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments