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

The domain name or IP address of the server (Example: www.pivotaltracker.com)

Top-level location where Pivotal Tracker 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 Pivotal Tracker.

API Token generated within the Pivotal Tracker user profile page. The user should have access to create and update issues in anticipated projects.

Synchronize all tasks from SD Elements.

Synchronize only tasks that fall under the risk policy.

The name of the project where issues should be created.

Name of the issue type to create in Pivotal Tracker (Default: bug)

This mapping determines the status to assign an SD Elements task based on its corresponding Pivotal Tracker issue status.

See Status Mapping for more information.

This mapping determines the status to assign a Pivotal Tracker issue based on its corresponding SD Elements task status. All Pivotal Tracker statuses in this mapping should be a single transition away from every other status in the mapping, as well as from the default status for new issues in your Pivotal Tracker project workflow. For example, a "Finished" Feature should be mapped so that it transitions to "Delivered" first, then "Accepted".

The SDE status to map to when encountering an unmapped Pivotal Tracker status (Default: Incomplete)

The name of a status in Pivotal Tracker to use when its corresponding SDE task is removed from the project.

Apply a specific tag to issues

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

Whether or not to include detailed code samples and How-To’s in the Pivotal Tracker issue.

Select this option if SD Elements does not have direct network access to the Pivotal Tracker server.

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

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)

Only synchronize tasks with certain statuses, such as TODO or DONE. (Default: TODO)

Only synchronize tasks in certain phases, such as Requirements or Development. (Default: none selected, meaning tasks from all phases will be synchronized)

Only synchronize tasks containing certain SD Elements task tags. (Optional)

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)

Issues created in Pivotal Tracker will be given titles that match this format. (Default: "T21: Task Title")

Uncheck this option if you need to test a connection without proper SSL/TLS certificate validation.

By default, a label "High", "Medium" or "Low" is assigned to Pivotal Tracker issues. Customize the labels by remapping SD Elements task priorities to another name.

In addition to the default-assigned fields, you can map additional SD Elements fields to other Pivotal Tracker text-based fields.

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

For more details refer to section Advanced field support.

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.

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