...
...
...
Prerequisites
This integration needs any Tempo addOn app pre-installed. While some certain routines are very general, some routines specifically other ones target a Tempo addon (e.g. allocations plugin specifically, for example, the allocations routines are available only if a Planner addon is installed) plugin is installed.
Routines
Child pages (Children Display) | ||
---|---|---|
|
...
Structures added into the SIL Simple Issue Language™ by the SIL Tempo Connector add-on:
TempoTeam
Parameter name | Type | Notes |
---|---|---|
id | number | |
name | string | |
mission | string | |
lead | string | User (lead) |
program_id | number | |
program_name | string | |
program_manager | string | User, the Program Manager for the team |
TempoAccount
Parameter name | Type | Notes |
---|---|---|
id | number | |
name | string | |
key | string | |
lead | string | User (lead) |
contact | string | Any contact for the customer set into the account |
status | string | One of: OPEN, CLOSED, ARCHIVED |
customer_id | number | |
customer_name | string | |
customer_key | string | |
category_id | number | |
category_key | string | |
category_name | string | |
monthly_budget | number | |
global | bool | |
billable | bool |
TempoAllocation
Parameter name | Type | Notes |
---|---|---|
id | number | |
parent_id | number | Yeap. allocations Allocations are hierachical |
scope | string | |
plan_item_id | number | |
plan_item_type | string | |
assignee | string | |
assignee_type | string | |
description | string | |
workPerDay | interval | |
startDate | date | |
endDate | date | |
createdBy | string | User who created it |
created | date | |
updatedBy | string | |
updated | date | |
recurring | bool | |
recurrence_ends | date | |
plan_approval_id | number |
...