Pivotal Tracker

Technical requirements

The following requirements must be met to integrate Pivotal Tracker with SD Elements.

  • A Pivotal Tracker API token with permission to create issues and update issue status in a target project.

Default assigned fields

The following fields are set by default:

  • Name

  • Description


The integration supports the following:

  • Two-way status synchronization

Default Priority Mapping

SD Elements

Pivotal Tracker







Connection details

Enter the connection details for the server.


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


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

Context Root

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.


Enter the token needed to authenticate to the server.


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

Countermeasures to Synchronize

Select Countermeasures to synchronize.

Sync all Countermeasures

Synchronize all Countermeasures from SD Elements.

Sync Risk Policy Countermeasures

Synchronize only Countermeasures that fall under the risk policy.

Project details

Enter the project-level details.

Pivotal Tracker Project

The name of the project where issues should be created.

Advanced Pivotal Tracker configuration

Enter advanced configuration options.

Story Type

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

Map a Pivotal Tracker status to an SD Elements status

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

See Status Mapping for more information.

Map an SD Elements status to a Pivotal Tracker status

This mapping determines the status to assign a Pivotal Tracker issue based on its corresponding SD Elements Countermeasure 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".

'Incomplete', 'Complete', and 'Not Applicable' SD Elements statuses must have a mapping. Any unmapped custom SD Elements statuses will use these mappings based on their meaning.

Unmapped Status Fallback (Optional)

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

Closed Issue Status

The name of a status in Pivotal Tracker to use when its corresponding SD Elements Countermeasure is removed from the project.

Pivotal Tracker label for stories generated by SD Elements (Optional)

Apply a specific tag to issues


Enter settings for synchronizing SD Elements Countermeasures.

Authoritative Source

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 Countermeasure. When you first synchronize a TODO Countermeasure 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:

  • Issue Tracker (default): The SD Elements Countermeasure will be updated to match the status in Pivotal Tracker. This is relevant to most workflows.

  • SD Elements: The Pivotal Tracker status will be updated to match the SD Elements status.

Include code sample How-To’s in Countermeasure descriptions

Whether or not to include detailed code samples and How-To’s in the Pivotal Tracker 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 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.

Filter Countermeasures

Select SD Elements Countermeasures to synchronize with the Pivotal Tracker project.

Countermeasures having a minimum priority

Only synchronize Countermeasures 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)

Countermeasures with status meaning

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

Limit to Countermeasures having these phases

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

Countermeasures having all of the following tags

Only synchronize Countermeasures containing certain SD Elements Countermeasure tags. (Optional)

Countermeasures with verification status

Only synchronize Countermeasures with a specific verification status, such as Pass or Fail. (Default: none selected, meaning Countermeasures with any verification status will be synchronized)

Advanced Issue Tracker options

Enter advanced configuration options.

Issue Tracker Title Format

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

Enforce Certificate Validation

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

Custom Priority Mapping

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

Custom Fields Mapping

In addition to the default-assigned fields, you can map additional SD Elements fields to other Pivotal Tracker text-based 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 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.

Sync frequency

Select how frequently the SD Elements and Pivotal Tracker 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 Pivotal Tracker 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.


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

results matching ""

    No results matching ""