CA Agile Central (formerly Rally)

Technical requirements

The following requirements must be met to integrate CA Agile Central with SD Elements.

  • Basic authentication must be enabled.

  • The user configured for the connection should:

    • Be a member of the project

    • Have permission to create, tag, transition and close work items.

    • Specific permissions:

      • User role in workspace

      • Editor role in project

Default assigned fields

The following fields are set by default:

  • Name

  • Description

  • Tags

  • Priority

Behavior

The integration supports the following:

Connection details

Enter the connection details for the server.

Protocol

Select the protocol for the connection (HTTPS or HTTP) (Default: HTTPS)

Server

The domain name or IP address of the server

Context Root

Top-level location where CA Agile Central is installed on a server. The value for this may be dependent on the configuration of an internal corporate proxy or where an administrator has installed CA Agile Central.

Credentials

Enter the credentials needed to authenticate to the server.

Username

Username authorized to connect with the server. This user should be able to create and edit stories/issues in CA Agile Central.

Password

The password used to authenticate to the server

Advanced CA Agile Central configuration

Enter advanced configuration options.

Issue Type

The name of the issue type to create in CA Agile Central (Default: Story)

Open a story in CA Agile Central with the following status

Status to assign to new issues created in CA Agile Central (Default: Defined)

States that map to DONE in SD Elements:

Comma-separated list of states in CA Agile Central that will be mapped to DONE in SD Elements. (Default: Completed,Accepted)

Workspace

Location where projects are grouped in CA Agile Central

Synchronization

Enter settings for synchronizing SD Elements tasks.

Authoritative Source

Select the tool that will be the authoritative system of record: CA Agile Central or SD Elements. This field is used in case of conflicting statuses between the CA Agile Central issue and the SD Elements task. When you first synchronize a TODO task in SD Elements with an issue in CA Agile Central, they will have the same status. If you then change the status in one tool, for example by closing the issue in CA Agile Cenral, they will have conflicting statuses. This conflict is resolved when the projects are synchronized. There are two options:

  • ALM (default): The SD Elements task will be updated to match the status in CA Agile Central. This is relevant to most workflows.

  • SD Elements: The CA Agile Central status will be updated to match the SD Elements status.

Include code sample How-To’s in task descriptions

Whether or not to include detailed code samples and How-To’s in the CA Agile Central issue.

This server is not accessible from the SD Elements server

Select this option if SD Elements does not have direct network access to the CA Agile Central server.

For example, if you are using a hosted SD Elements instance but you want to integrate with an internal/protected CA Agile Central system, choose this option and run the Remote Integration Client to perform integration.

Tasks to synchronize

Select the SD Elements tasks that are synchronized with the CA Agile Central project.

Tasks having a minimum priority

Synchronize tasks with a minimum priority (for example, 7 or above). This is useful if you want to limit the amount of work for users. (Default: 7)

Tasks with status

Synchronize only tasks with certain statuses, such as TODO or DONE. (Default: TODO)

Tasks having phase

Synchronize only tasks in certain phases, such as Requirements or Development. (Default: Requirements, Architecture & Design, Development)

Tasks having all of the following tags

Synchronize only tasks containing certain SD Elements task tags. (Optional)

Tasks with verification status

Synchronize only tasks with a specific verification status, such as Pass or Fail. (Default: None, Partial Pass, Pass, Fail)

Advanced ALM options

Enter advanced configuration options.

ALM context

Bind a set of tasks using a cetain value. This is applicable only when custom titles are selected having the entry "Context"

Custom Priority Mapping

By default CA Agile Central does not expose a priority field. However, an integration can still map the SD Elements priority to a field in CA Agile Central

Generally, you should follow these steps:

  1. Identify the field in CA Agile Central you want to populate.

    • The integration supports "Priority" by default.

    • If a different field is desired, such as "Priority Field" then add it to Custom Fields Mapping. Associate the field to value $task_priority_translated.

  2. Update Custom Priority Mapping with the mapping between SDE priorities and the desired field value.

Custom Fields Mapping

In addition to the default-assigned fields, you can map additional SD Elements fields to CA Agile Central fields.

 Fields that are not required or have default values do not need to be set.

For example, you may have a required field in your CA Agile Central project that is not set by default. Custom field mappings can be set at both the system connection and project connection levels. Mappings set in a project connection override mappings set in the system connection.

For more details refer to section Advanced field support.

Sync frequency

Select how frequently the SD Elements and CA Agile Central projects are synchronized. You can choose from the following options. The more frequently you run synchronization, the greater the performance impact on both the SD Elements and CA Agile Central servers. This is generally only a concern for large organizations running many synchronizations at once.

Hourly, Daily, Weekly, or Monthly

The projects will synchronize automatically every hour, day, week or month. Daily synchronization is typically sufficient. However, you may want to select a more frequent interval if development moves quickly in your organization.

Manually

You must click the Sync button on the ALM Integrations page in order to synchronize the projects. This is the default value.

results matching ""

    No results matching ""