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: 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.

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: bug)

Open a story in Pivotal Tracker with the following state

Status to assign to new issues (Default: unscheduled)

States that map to DONE in SD Elements

Comma-separated list of states that will be mapped to DONE in SD Elements. (Default: accepted)

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:

  • ALM (default): The SD Elements task 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 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)

Advanced ALM options

Enter advanced configuration options.

ALM Title Format

Issues created in Pivotal Tracker will be given titles that match this format. (Default: "T21: Task 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 task 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.

Manually

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

results matching ""

    No results matching ""