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 Required

Guru 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

  1. In Guru, go to Manage.
  2. Select Sources, then click Add Source.
  3. Choose Pivotal Tracker from the list of CRM integrations.
  4. 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.
  5. Add a display name for the Source (optional) and click Connect Source.
  6. 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 CategoryCommon Model / What You'll See During SetupObjects/Data Brought InKey Fields
StoriesPrimary Object: TicketUser 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
ProjectsProject / CollectionPivotal Tracker projects (Note: Project model deprecated, use Collection)โ€ข Name โ€ข Description โ€ข Parent collection (UUID) โ€ข Remote ID โ€ข Remote data
CommentsCommentComments on stories and epicsโ€ข Body โ€ข User (UUID) โ€ข Ticket (UUID) โ€ข Remote created at โ€ข Remote ID โ€ข Remote data
UsersUserPivotal Tracker team members (via account memberships)โ€ข Name โ€ข Email address โ€ข Remote ID โ€ข Remote data
EpicsTicketEpics (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
MembershipsUserAccount-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.