| Active with remarks |
|---|
| This application needs additional settings. Please follow the documentation below to create your own connectionUnique, active service acces point to a network. There are different types of connections (API key, Oauth…). More. |
The Pivotal Tracker modulesThe module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts) More allow you to monitor, create, update, list, retrieve, and delete the projects, and stories in your Pivotal Tracker account.
Prerequisites
-
A Pivotal Tracker account
In order to use Pivotal Tracker with Boost.spaceCentralization and synchronization platform, where you can organize and manage your data. More IntegratorPart of the Boost.space system, where you can create your connections and automate your processes. More, it is necessary to have a Pivotal Tracker account. If you do not have one, you can create a Pivotal Tracker account at pivotaltracker.com.
To connect your Pivotal Tracker account to Boost.space Integrator you need to obtain the API Key from your Pivotal Tracker account and insert it in the Create a connection dialog in the Boost.space Integrator moduleThe module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts) More.
1. Log in to your Pivotal Tracker account.
2. Click Your Account Name > Profile.
3. Navigate to the API TokenThe API token is a multi-digit code that allows a user to authenticate with cloud applications. More section and copy the tokenThe API token is a multi-digit code that allows a user to authenticate with cloud applications. More to your clipboard.
4. Go to Boost.space Integrator and open the Pivotal Tracker module’s Create a connection dialog.
5. In the Connection name field, enter a name for your connection.
6. In the Pivotal Tracker API Token field, enter token copied in step 3, and click Continue.
The connection has been established.
TriggersEvery scenario has a trigger, an event that starts your scenario. A scenario must have a trigger. There can only be one trigger for each scenario. When you create a new scenario, the first module you choose is your trigger for that scenario. Create a trigger by clicking on the empty module of a newly created scenario or moving the... when a new project is created.
|
Connection |
|
|
Limit |
Set the maximum number of projects Boost.space Integrator should return during one execution cycleA cycle is the operation and commit/rollback phases of scenario execution. A scenario may have one or more cycles (one is the default).. |
|
Output Properties |
Select or map the property details you want to retrieve. |
Retrieves a list of all your active projects.
|
Connection |
|
|
Limit |
Set the maximum number of projects Boost.space Integrator should return during one execution cycle. |
|
Output Properties |
Select or map the property details you want to retrieve. |
|
Account IDs |
Add the accounts whose projects you want to list. |
Creates a new project.
|
Connection |
|
|
Project Title |
Enter (map) the name of the project. |
|
Description |
Enter (map) the project details. |
|
Account |
Select or map the account to which the project belongs to. |
|
Output Properties |
Select or map the properties you want to retrieve for the project. |
Gets the information of a project.
|
Connection |
|
|
Project ID |
Select or map the Project ID whose details you want to retrieve. |
|
Output Properties |
Select or map the properties you want to retrieve for the project. |
Updates the settings of a project.
|
Connection |
|
|
Project Title |
Enter (map) the name of the project. |
|
Description |
Enter the project details. |
|
Account |
Select or map the account to which the project belongs to. |
|
Enable Tasks |
Select whether you want to enable the tasks. |
|
Public Access |
Select whether the project can be accessed publicly. |
|
Start Iteration on |
Select or map the day in the week on which the project’s iterations start. |
|
Enter (map) the date on which the project work begins. |
|
|
Iteration Length |
Enter (map) the number of weeks in the project iteration. For example, |
|
Point Scale |
Enter (map) the specification available for entering story estimates within the project. You can specify a comma-delimited series of values on the Project Settingspage of the Tracker web application.
If another comma-separated point-scale string is passed, it will be treated as a custom point scale. |
|
Initial Velocity |
Enter (map) the number that will be used as the project’s velocity when there are not enough recent iterations with Done stories for an actual velocity to be computed. |
|
Velocity Strategy |
Select or map the number of iterations that should be used when averaging the number of points of Done stories when calculating the project’s velocity. |
|
Number of Done Iterations to Show |
Enter (map) the maximum number of done iterations that will be loaded/shown/included in these areas. There are areas within the Tracker UI and the API in which sets of stories automatically exclude the Done stories contained in older iterations.For example, in the web UI, the DONE panel does not show all the Done stories by default and provides a link to click to cause the full story set to be loaded/displayed. |
|
PlanCombination of a license (enabled features) and tier (numeric limits) and a subscription period (monthly / yearly). Current Iteration Automatically |
Select whether you want the Tracker to perform the project iteration planning based on the project’s velocity, and allow usersCan use the system on a limited basis based on the rights assigned by the admin. More to manually control the set of unstarted stories included in the current iteration. For more information, see the FAQ. |
|
Enable Incoming Emails |
Select whether you want the project to accept the incoming email responses to Tracker notification emails and convert them to comments on the appropriate stories. For more information, see the FAQ. |
|
Bugs and Chores May Be Given Points |
Select whether the tracker should allow the estimates to be set on the bug and chore-type stories. Pivotal Tracker does not recommend the userCan use the system on a limited basis based on the rights assigned by the admin. More to set true for this option. For more information, see the FAQ. |
|
Output Properties |
Select or map the properties you want to retrieve for the project. |
Deletes a project.
|
Connection |
|
|
Project ID |
Select or map the Project ID you want to delete permanently. |
Triggers when a new story is added to a project.
|
Connection |
|
|
Project ID |
Select or map the Project ID whose stories you want to watch. |
|
Limit |
Set the maximum number of stories Boost.space Integrator should return during one execution cycle. |
|
Output Properties |
Select or map the property details you want to retrieve. |
Retrieves a list of the stories of a project.
|
Connection |
|
|
Limit |
Set the maximum number of projects Boost.space Integrator should return during one execution cycle. |
|
Project ID |
Select or map the Project ID whose stories you want to list. |
|
Output Properties |
Select or map the property details you want to retrieve. |
Create a new story in a project.
|
Connection |
|
|
Project ID |
Select or map the Project ID for which you are creating the story. |
|
Name |
Enter (map) the project name. |
|
Description |
Enter (map) the details of the project. |
|
Estimate |
Select or map the number of points for the story. |
|
Story Type |
Select or map the story type. For example, |
|
LabelsA label is a “tag” that can be added to items within a module. It's a flexible tool used to categorize and organize data, making it easier to customize workflows and processes. More |
Add the labels for the story. For example, |
|
Requested By |
Select or map the user who requested this story. For example, |
|
Linked Project Integration |
Select or map the link of this story to other tools, such as Jira. For more information, see the Pivotal Tracker documentation about using project integrations. |
|
Output Properties |
Select or map the properties you want to retrieve for the project. |
Gets the information of a story.
|
Connection |
|
|
Project ID |
Select or map the Project ID for which you are creating the story. |
|
Story ID |
Select or map the Story ID whose details you want to retrieve. |
|
Output Properties |
Select or map the properties you want to retrieve in the story details. |
Updates the parameters of a story.
|
Connection |
|
|
Project ID |
Select or map the Project ID for which you are creating the story. |
|
Story ID |
Select or map the Story ID whose details you want to update. |
|
Project ID |
Select or map the new Project ID with which you want to associate the story. |
|
Name |
Enter (map) the new name for the story. |
|
Description |
Enter (map) the details of the project. |
|
Story Type |
Select or map the story type. For example, |
|
State |
Select or map the statusCreate statuses for each module separately to create an ideal environment for efficient and consistent work. More of the story. For example, |
|
Estimate |
Select or map the number of points for the story. |
|
Labels |
Add the labels for the story. For example, |
|
Requested By |
Select or map the user who requested this story. For example, |
|
Integration |
Select or map the linked integration of this story to other tools, such as Jira. For more information, see the Pivotal Tracker documentation about using project integrations. |
|
Output Properties |
Select or map the properties you want to retrieve for the project. |
Deletes a story.
|
Connection |
|
|
Project ID |
Select or map the Project ID whose story you want to delete |
|
Story ID |
Select or map the Story ID you want to delete. |
Triggers when any new activity happens within a project.
![[Note]](https://docs.boost.space/wp-content/themes/bsdocs/docs-parser/HTML/css/image/note.png) |
Note |
|---|---|
|
You do not have to add the webhooksA webhook is a way for an app to send real-time information to a specific URL in response to certain events or triggers. in the Pivotal Tracker as it is automatically done for you once you add and save an instant triggerEvery scenario has a trigger, an event that starts your scenario. A scenario must have a trigger. There can only be one trigger for each scenario. When you create a new scenario, the first module you choose is your trigger for that scenario. Create a trigger by clicking on the empty module of a newly created scenario or moving the... module to your scenarioA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive. More. |
|
WebhookA webhook is a way for an app to send real-time information to a specific URL in response to certain events or triggers. Name |
Enter a name for the webhook. |
|
Connection |
|
|
Project ID |
Select or map the Project ID whose story you want to delete |
Performs an arbitrary API call.
|
Connection |
|
|
URL |
Enter a path relative to For the list of available endpoints, refer to the Pivotal Tracker API Documentation. |
|
Method |
Select the HTTP method you want to use: GETto retrieve information for an entry. POSTto create a new entry. PUTto update/replace an existing entry. PATCHto make a partial entry update. DELETEto delete an entry. |
|
Headers |
Enter the desired request headers. You don’t have to add authorization headers; we already did that for you. |
|
Query String |
Enter the request query string. |
|
Body |
Enter the body content for your API call. |
The following API call returns all the stories from your Pivotal Tracker account:
URL:/v5/projects/{projects_id}/stories
Method:GET
Matches of the search can be found in the module’s Output under BundleA bundle is a chunk of data and the basic unit for use with modules. A bundle consists of items, similar to how a bag may contain separate, individual items. More > Body.In our example, 3 stories were returned:
