...
There are two possible field options:
native external tool fields - they display the value from an external platform; if the value is unavailable, it is left empty (if a column is supposed to display Jira “Start Date,” nothing can be displayed for a Trello task - the task doesn’t exist in Jira, so the App can’t find a value for it)
Builtbuilt-in fields.
Built-in fields are capable of taking can take information from various external platforms and mapping them map it to a built-in field, effectively letting you see a single column showing values for multiple types of tasks coming from a multitude of external platforms and from native BigPicture elements.
...
You can check these fields by navigating to Jira to Jira administration (cog icon) > Issues > Custome fields and search searching by SoftwarePlant or BigPicture.
...
The table below provides you with an overview of how built-in fields function in the App.
Task Attribute | Mapped to External Platform | Mapped to External Platform | Available for Basic Tasks | Comment | ||
---|---|---|---|---|---|---|
Icon | YES | NO | YES | If an icon is not available on the external platform, the default icon will be used (same as for Basic Tasks) | ||
Key | YES | NO | YES | The built-in “Key” column will aggregate issue/task/card keys from different platforms and display them in a single column. A “Key” field cannot be modified to display any different value.
| ||
Summary | YES | NO | YES | A built-in summary field cannot be removed. The mapping of the field can’t be changed.
| ||
Start date | YES | YES | YES | The mapping of the start date (built-in) field for Jira can be changed in the App Configuration. Trello cards don’t have a start date. A built-in field uses the due date value (effectively, built-in field start and end dates of Trello cards are both mapped to Trello due date). Basic Task dates are displayed in a built-in Start date column.
| ||
End date | YES | YES | YES | |||
Baseline start date | YES | YES | YES | |||
Baseline end date | YES | YES | YES | |||
Progress | YES | YES | YES | |||
Milestone | YES | YES | YES | Native App field. It exists only as a built-in field, but its value can be mapped to display a Jira value.
| ||
Period mode | YES | YES | YES | |||
Color | NO | NO | YES | Native App field. It can’t be mapped to display values from external tools. | ||
Task ID | NO | NO | YES | Native App field. It can’t be mapped to display values from external tools. | ||
Assignee | YES | NO | NO | |||
Skills | NO | NO | YES | Native App field. It can’t be mapped to display values from external tools. | ||
Status | YES | NO | NO | |||
Duration Calendar Days | NO | NO | YES | Based on the number of calendar days (start to end date). |
| ||||
Duration working days | NO | NO | YES | Based on the number of working days (non-working days excluded).
|
Outline level | NO | NO | YES | Dynamically built Data Type - the values aren't permanently associated with tasks; the field value adjusts to reflect WBS changes. Display Options:
|
Outline level → shows how deep the task is in the tree structure (WBS). Sequential Index → shows where the task is located in the WBS structure (similar to the notation of the table of contents in the book) |
Note: filtering does not affect the Sequential Index. | |||
Overdue Start/End Date | NO | NO | NO |
The Overdue Start Date field calculates the difference between the current task Start Date (when status category is To Do).
| ||||
Team | NO | NO | YES | The Team field is based on the Team data type. Team created in BigPicture is visible in a column view on Gantt and Scope modules and is inline edited. The field can also be used even not synchronized. Check App Configuration > General > Fields > General mapping. |
Workload Contouring Mode | NO | NO | YES | The Workload contouring allows to spread the effort of the task over its duration. There are three automatic options and one manual mode to choose from.
|
Basic Tasks
A built-in field lets you easily visualize all data related to Basic tasks native to the BigPicture App itself. Some values, such as Assignee, are not available (because this attribute doesn’t exist for them), but all existing attributes of Basic Tasks can be displayed using built-in fields.
...