The App visiualizes Information based on the tool connections you have set up. Values of fields in Jira, Trello etc. have to be mapped to fields available within the App. Information about the data source can be listed in the “origin” column and shown as an appropriate icon. 

There are two possible field options:

  • native external tool fields - they display the value from an external platform; if 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)

  • Built-in fields

In BigPicture 8 we have added "built-in" fields, which are capable of taking information from various external platforms and mapping them 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.

For example, scope of the "EMEA Initiative" Box consists of Jira issues, Trello cards and Basic tasks. When you try to add an "Icon" column the App presents you with following options:

When you are adding a column, the icon on the right indicates what data will be shown - will it be based on a value of a Jira field, Trello field, or is it a built-in field (the last option in the picture above).

In the below example, three icon columns have been added to show the difference between them.

  • Left = Jira
  • Middle = Trello
  • Right = Built-in 

The Jira icon column displays values coming from Jira only. This means, that for Trello cards and Basic tasks nothing is displayed. 

The Trello icon column displays values coming from Trello only. This means, that for Jira issues and Basic tasks nothing is displayed.

The Built-in icon column displays all values; it finds the appropriate field value in both Jira and Trello and displays them. Native BigPicture Basic tasks are also included.


Hover your cursor over any field value to see present setup of the column.

For example, the "Assignee" column below is using a built-in field.

Mapping Options for Built-in Fields

Built-in fields can function in following ways:

  • configurable fields (e.g. End Date)
  • non-configurable fields (e.g. summary)
  • native App fields (don't correspond to any external tool)
  • fields that vary depending on the external platform (for example, mapping of a field can be changed for Jira but not for Trello; or a field exists in one external platform but not in another)

Configurable Fields

For some fields, you are able to select what value you want to use.

For example, in the Technical Configuration of the App you define synchronization rules - "End date" could be mapped to Jira "Due date" field → in such case, the built-in end date of the App effectively displays the same value as Jira due date.



Available options vary across different external platforms (something can be ‘mappable’ in Jira but not in Trello). You can change the mapping of an "End date" for Jira and decide to use the "Due date" Jira value as an end date, but you can't change settings for Trello.
Effectively, the built-in "End date" field will display:

  • For Jira, what has been specified in Technical Configuration of the App (in the example below "Due date" has been used)
  • Trello due date (Trello doesn't have an "End Date" - due date will be always used to populate the built-in "End date" field)
 Click here to expand...

"Due date" exists in Jira and Trello. There is no built-in due date field.

Jira "Due date" column displays Jira values. Trello "Due date" column displays Trello values. Basic Task won't be included in any of those.

When you add the built-in "End date" column:


Non-Configurable Fields

You can't change the mapping. 

For example, Summary in Jira = summary built-in, and this cannot be changed. You can't decide that built-in "summary" will display "description" or anything else. Built-in summary will always display the same value as Jira summary.

Native App Fields

The field exists only in the App and can't be found in Jira, Trello, or any other of the connected tools.

For example, "Color" field.

Some native fields, such as "Milestone", can be mapped to external tools in Technical Configuration.


Fields that vary depending on the external tool

Some fields, depending on the external platform, may not have an easy corresponding value. For example, Assignee is easily found in Jira (the built-in field can display the value) but Trello doesn't have a corresponding field (Members can be added to a card, but there is no single person assigned to it). This is why a built-in Assignee column will not display any value for Trello cards. Basic Tasks also don't have an assignee that could be listed in the column.  

Built-in fields matrix

Table below provides you with an overview of how built-in fields function in the App.

Task AttributeMapped to External Platform
(non-configurable)
Mapped to External Platform
(configurable)
Available for Basic Tasks
(tasks that exist only in the App)
Comment
IconYES
YES

If an icon is not available in the external platform the default icon will be used (same as for Basic Tasks)

Key

YES
YES

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.

 Click here to expand...

SummaryYES
YES

A built-in summary field cannot be removed. Mapping of the field can't be changed.

 Click here to expand...

Start dateYESYESYES

Mapping of a start date (built-in) field for Jira can be changed in Technical Configuration of the app.

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.

 Click here to expand...

End dateYESYESYES
Baseline start dateYESYESYES
Baseline end dateYESYESYES
ProgressYESYESYES
MilestoneYESYESYES

Native App field. It exists only as a built-in field, but its value can be mapped to display a Jira value.

 Click here to expand...


Period modeYESYESYES
Color

YESNative App field. It can't be mapped to display values from external tools.
AssigneeYES


Skills

YESNative App field. It can't be mapped to display values from external tools.
StatusYES



Basic Tasks

A built-in field lets you easily visualize all data related to Basic tasks, that are 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 a Basic Tasks can be displayed using built-in fields.