SD Elements
Rally (formerly CA Agile Central)
Technical requirements
The following requirements must be met to integrate Rally 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:
-
Two-way status synchronization
Default Priority Mapping
Rally |
|
9-10 |
Resolve Immediately |
6-8 |
High Attention |
4-5 |
Normal |
1-3 |
Low |
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 Rally 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 Rally. |
Credentials
Enter the credentials needed to authenticate to the server. The connection supports either Basic Authentication or Token Authentication.
Basic Authentication
Username |
Username authorized to connect with the server. This user should be able to create and edit stories/issues in Rally. |
---|---|
Password |
The password used to authenticate to the server |
API Token Authentication
Token |
API Token generated within Rally. This user should be able to create and edit stories/issues in Rally. |
---|
Tasks to Synchronize
Select tasks to synchronize.
Sync all tasks |
Synchronize all tasks from SD Elements. |
---|---|
Sync Risk Policy tasks |
Synchronize only tasks that fall under the risk policy. |
Advanced Rally configuration
Enter advanced configuration options.
Issue Type |
Type of work item that SD Elements will create when creating a task in Rally (Default: |
||
---|---|---|---|
Map a Rally status to an SD Elements status: |
This mapping determines the status to assign an SD Elements task based on its corresponding Rally issue status.
See Status Mapping for more information. |
||
Map an SD Elements status to a Rally status |
This mapping determines the status to assign a Rally issue based on its corresponding SD Elements task status.
See Status Mapping for more information. |
||
Rally Workspace Name (Optional) |
Location where projects are grouped in Rally |
Synchronization
Enter settings for synchronizing SD Elements tasks.
Authoritative Source |
Select the tool that will be the authoritative system of record: Rally or SD Elements. This field is used in case of conflicting statuses between the Rally issue and the SD Elements task. When you first synchronize a TODO task in SD Elements with an issue in Rally, they will have the same status. If you then change the status in one tool, for example by closing the issue in Rally, they will have conflicting statuses. This conflict is resolved when the projects are synchronized. There are two options:
|
---|---|
Include code sample How-To’s in task descriptions |
Whether or not to include detailed code samples and How-To’s in the Rally issue. |
This Issue Tracker server is hosted within a private network and cannot be reached directly by SD Elements. |
Select this option if SD Elements does not have direct network access to the Rally server. For example, if you are using a hosted SD Elements instance but you want to integrate with an internal/protected Rally system, choose this option and run the Remote Integration Agent to perform integration. |
Filter tasks
Select SD Elements tasks to synchronize with the Rally project.
Tasks having a minimum priority |
Only synchronize tasks with a minimum priority, such as 7 or above. This is useful if you want to limit the amount of work for users. (Default: 1) |
---|---|
Tasks with status meaning |
Only synchronize tasks with certain statuses, such as TODO or DONE. (Default: TODO) |
Limit to tasks having these phases |
Only synchronize tasks in certain phases, such as Requirements or Development. (Default: none selected, meaning tasks from all phases will be synchronized) |
Tasks having all of the following tags |
Only synchronize tasks containing certain SD Elements task tags. (Optional) |
Tasks with verification status |
Only synchronize tasks with a specific verification status, such as Pass or Fail. (Default: none selected, meaning tasks with any verification status will be synchronized) |
Advanced Issue Tracker options
Enter advanced configuration options.
Issue Tracker Title Format |
Issues created in Rally will be given titles that match this format. (Default: "T21: Task Title") |
||
---|---|---|---|
Bypass server certificate validation for HTTPS (insecure, only used for testing purposes). |
Check this option if you need to test a connection without the proper SSL/TLS certificates. |
||
Issue Labels / Tags |
Tag value assigned to Rally issues (Default: SD-Elements) |
||
Issue Tracker parent issue |
Rally issue ID to use as the parent issue. SD Elements tasks are created as children of this parent issue. This is only applicable when creating issue types of "Story" whose parent is "User Story" or "Feature", or creating issue types of "Task" whose parent is "User Story". This takes the prefixed ID, such as "US1234" or "F567". |
||
Issue Tracker context |
Bind a set of tasks using a certain value. This is applicable only when custom titles are selected having the entry "Context" |
||
Custom Priority Mapping |
By default Rally does not expose a priority field. However, an integration can still map the SD Elements priority to a field in Rally Generally, you should follow these steps:
|
||
Custom Fields Mapping |
In addition to the default-assigned fields, you can map additional SD Elements fields to Rally fields.
For example, you may have a required field in your Rally 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 Rally 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 Rally 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 Issue Tracker Integrations page in order to synchronize the projects. This is the default value. |