...
Note that the structure fields can be modified, but the changes are not saved in the database. If you change a field for a project version variable, the project version will not be affected. Simply put, the structures are 'detached'.
| Excerpt |
|---|
Name | Field | Type | Notes |
|---|
| TempoAccount | id | number |
| key | string |
| name | 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_key | string |
| customer_name | string |
| category_id | number |
| category_key | string |
| category_name | string |
| monthly_budget | number |
| global | boolean |
| billable | boolean |
| | Anchor |
|---|
| TempoAllocation |
|---|
| TempoAllocation |
|---|
|
TempoAllocation | id | number |
| parentId | number | Allocations are hierachical | scopeId | number |
| scopeType | string | list of values: "account", "board", "project", "team", "folio", "none" | planItemId | number |
| planItemType | string | list of values: "component", "epic", "issue", "project", "sprint", "version" | assignee | string |
| assigneeType | string | list of values: "team", "user" | commitment | number |
| description | string |
| workPerDay | number | number of hours | includeNonWorkingDays | boolean |
| startDate | date |
| endDate | date |
| createdBy | string | User who created it | created | date |
| updatedBy | string |
| updated | date |
| recurring | boolean |
| recurrenceRule | string | list of values: "NEVER", "WEEKLY", "BI-WEEKLY", "MONTHLY" | recurrenceEnds | date |
| planApprovalId | number |
| planApprovalReviewer | string |
| | TempoTeam | id | number |
| name | string |
| mission | string |
| summary | string |
| lead | string | User (lead) | program_id | number |
| program_name | string |
| program_manager | string | User, the Program Manager for the team |
|