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
Behavior
The integration supports the following:
-
Two-way status synchronization
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 (Example: |
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. |
Credentials
Enter the token needed to authenticate to the server.
Token |
API Token generated within the Pivotal Tracker user profile page. The user should have access to create and update issues in anticipated projects. |
|---|
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: |
|---|---|
Open a story in Pivotal Tracker with the following state |
Status to assign to new issues (Default: |
States that map to DONE in SD Elements |
Comma-separated list of states that will be mapped to DONE in SD Elements. (Default: |
Label to assign to issues |
Apply a specific tag to issues |
Synchronization
Enter settings for synchronizing SD Elements tasks.
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 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:
|
|---|---|
Include code sample How-To’s in task descriptions |
Whether or not to include detailed code samples and How-To’s in the Pivotal Tracker 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 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 Client to perform integration. |
Tasks to synchronize
Select the SD Elements tasks that are synchronized with the Pivotal Tracker 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) |