Setting up Pivotal Tracker as a Source
Connect your Pivotal Tracker workspace to Guru to surface project management insights, track progress, and enhance collaboration through AI-powered knowledge sharing. This guide walks you through setting up Pivotal Tracker as a source in Guru.
Access RequiredGuru Access: You need to be an Admin, Source Creator, or relevant custom role to set up Sources
Pivotal Tracker Access: You need to have access to generate an API token in Pivotal Tracker.
Setting up Pivotal Tracker as a Source
- In Guru, go to Manage.
- Select Sources, then click Add Source.
- Choose Pivotal Tracker from the list of CRM integrations.
- Authenticate using your Pivotal Tracker API Key. You can find by clicking on your avatar in the top right > Profile > API. Paste your API Token in Guru.
- Add a display name for the Source (optional) and click Connect Source.
- Assign which Guru Groups should have access to this content.
Objects synced from Pivotal Tracker
Primary objects are the objects used to generate the search record.
| Pivotal Tracker Category | Common Model / What You'll See During Setup | Objects/Data Brought In | Key Fields |
|---|---|---|---|
| Stories | Primary Object: Ticket | User stories, bugs, chores, and releases | • Name • Description • Ticket type (String) • Status (Enum) • Priority • Due date • Creator (UUID) • Assignees (Array) • Collaborators • Parent ticket (UUID) • Project (UUID/Unknown) • Collections (Array) • Tags (Array) • Ticket URL • Remote created at • Remote updated at • Remote ID • Remote data |
| Projects | Project / Collection | Pivotal Tracker projects (Note: Project model deprecated, use Collection) | • Name • Description • Parent collection (UUID) • Remote ID • Remote data |
| Comments | Comment | Comments on stories and epics | • Body • User (UUID) • Ticket (UUID) • Remote created at • Remote ID • Remote data |
| Users | User | Pivotal Tracker team members (via account memberships) | • Name • Email address • Remote ID • Remote data |
| Epics | Ticket | Epics (large initiatives containing multiple stories) | • Name • Description • Ticket type (String) • Status (Enum) • Collaborators • Tags (Array) • Ticket URL • Remote created at • Remote updated at • Remote ID • Remote data |
| Memberships | User | Account-level user memberships providing user information | • Name • Email address • Remote ID • Remote data |
Permissions
- When you connect Pivotal Tracker as a source in Guru, you'll permission that content in Guru. Learn more here.
- If someone is not provided with access in Guru to this source, they will not see Pivotal Tracker results in searches or when chatting with Guru.
Updated about 1 month ago
