You can import plans to the team members timeline from a comma-separated values (.csv) file that, for example, you exported from other software, such as spreadsheet software.
If field content contains double quotation marks, the double quotation marks in the content are doubled.
For example:
"Develop prototype for customer ""A"" in Malaysia."
When this example is imported, the following data is displayed in Tempo Planner: Develop prototype for customer "A" in Malaysia.
Ensure that the .csv file contains fields that correspond to the following Tempo Planner fields.
Tip
You are not required to change the field names (column headers) in the .csv file to match the Tempo Planner field names because, in a later step, you map the .csv fields to the Tempo Planner fields.
Tempo Planner Fields
Field
Possible values
Examples of values
Explanation
User or team row
user
team
In Tempo Planner, on the team members timeline, the top row is the team row. The other rows are user rows, which correspond to individual JIRA users.
Type and position of plan
User or team row field
A team plan in the team row
team
Copy of a team plan in a user row
user
An individual plan in a user row
user
Planned for (team ID or username)
habib
5
The JIRA username of the team member whom the work is planned for or, in the case of team plans, the team ID (a number).
Tip
When you import data later in this procedure, the following rules are applied:
If a username from the .csv file is a JIRA username, but the user is not a member of the team that you are importing plans for, the user is added to the team
If a username from the .csv file does not match a JIRA username, a new row is added to the team members timeline for a future user.
All team IDs change to the team ID of the team that you are importing plans for. You can know the team ID of the team that you are importing plans for from the URL of the team members timeline in Tempo Planner.
Plan item type
issue
project
component
version
sprint
Plan summary
"Preparatory work"
In Tempo Planner, if a plan has a plan summary, the plan summary is displayed on the plan on the timeline.
Planned time (fraction of each working day)
"0.75"
In the 'Plan details' sidebar in Tempo Planner, the planned time is shown as a percentage of the working day. However, in the .csv file, the planned time must be shown as a decimal fraction. For example:
Planned time
'Plan details' sidebar in Tempo Planner
.csv file
50%
0.5
75%
0.75
100%
1
Start
"2016-04-11"
The start date of the plan. All dates in the .csv file must have a consistent format. Ensure that the format conforms with one of the formats in the JAVA standards. Later in this procedure, you specify in Tempo Planner the date format that you used in the .csv file.
End
"2016-04-14"
The end date of the plan.
All dates in the .csv file must have a consistent format. Ensure that the format conforms with one of the formats in the JAVA standards. Later in this procedure, you specify in Tempo Planner the date format that you used in the .csv file.
Repeated instance of a plan
FALSE
any value
empty field
Type of plan
Repeated instance of a plan field
Note
A single plan that is not repeated
FALSE
The first plan in a series of repeated plans
FALSE
Although the plan is repeated, the plan is the original plan, not a repeated instance.
Part of a series of repeated plans but not the first plan in the series
empty field or any value other than FALSE
As long as the value is not FALSE, the value is ignored in the import process and effectively becomes TRUE in Tempo Planner.
Repeat frequency
NEVER
WEEKLY
"EVERY TWO WEEKS"
MONTHLY
any value
empty field
Type of plan
Repeat frequency field
Note
A single plan that is not repeated
NEVER
The first plan in a series of repeated plans
WEEKLY, "EVERY TWO WEEKS", or MONTHLY
Part of a series of repeated plans but not the first plan in the series
empty field, or NEVER, or any value other than the values in the above row
If the value is not one of the values NEVER, WEEKLY, "EVERY TWO WEEKS", or MONTHLY, the value is ignored in the import process and effectively becomes NEVER in Tempo Planner. The logic is that, although the first plan is repeated one or more times, the repeated instances are not repeated.
Repeat until
"2016-05-25"
If the plan is the first plan in a series of repeated plans, the Repeat until field indicates the latest possible start date of a repeated plan.
All dates in the .csv file must have a consistent format. Ensure that the format conforms with one of the formats in the JAVA standards. Later in this procedure, you specify in Tempo Planner the date format that you used in the .csv file.
User row of a team plan (team ID)
5
empty field
In Tempo Planner, on the team members timeline, any plan that is created on the first row (that is, the team row) is also displayed on each user row (unless the user's individual plans take up the whole working day). Each user-row instance of a team plan is considered to be a plan and must have a separate line in the data of the .csv file.
Type and position of plan
User row of a team plan (team ID) field
A team plan in the team row
empty field
Copy of a team plan in a user row
Team ID
An individual plan in a user row
empty field
Tips
When you import data later in this procedure, all team IDs change to the team ID of the team that you are importing plans for. You can know the team ID of the team that you are importing plans for from the URL of the team members timeline in Tempo Planner.
Plan item ID
10330
The ID number of the JIRA issue, project, component, version, or sprint that is planned.
Tip
If the Plan item ID field is empty for a plan in the .csv file, or if the field contains an ID that is not the ID of any JIRA issue, project, component, version, or sprint, you can still import the plan into Tempo Planner, but the plan will not be associated with a plan item. In Tempo Planner, you can associate the plan with a plan item by editing the plan.
In Tempo Planner, go to the team members timeline of the team that you want to import plans for.
On the menu bar that is immediately above the timeline, click the three-dots icon > Import data.
In the Import Plans window, browse for the .csv file, and fill in the requested information:
Date Format
Type the format that is used for dates in the .csv file; for example, dd-MM-yyyy or MM/dd/yyyy. Ensure that you type the same date separator that is used in the .csv file; for example, - or /
Grouping Separator
The character that is used in the .csv file to separate groups of thousands in a number. For example, in the following number, the grouping separator is a comma: 9,999,999.99
Decimal Separator
The character that is used in the .csv file to separate the integer part of decimal numbers from the fractional part. For example, in the following number, the decimal separator is a dot: 9,999,999.99
Click Next.
In the 'Import Plans: Map Fields' window, in the Tempo Planner Field column, select the Tempo Planner fields that match the fields from the .csv file.
Tip
Your .csv file might contain extra fields, which are not imported into Tempo Planner.
Click Import.
The plans from the .csv file are imported into Tempo Planner.
Tip
Messages are displayed that indicate the number of rows that were processed and the number of rows that were imported successfully.
These messages refer to rows in the .csv file. The number of rows does not count the following rows:
Rows that are repeated instances of a plan
Rows that correspond to user rows of a team plan
If an error message is displayed, see the related topic about error messages below.
