To learn more about Tempo products, please visit our Help Center. For support, see our Support Portal.

Exporting plans to a CSV file

Owned by Hildur Nanna Eiríksdóttir (Deactivated)
Last updated: Apr 02, 2024 by Jaramy Conners
5 min read

You can export a team's plans to a comma-separated values format (.csv). The data can then be imported to other software, such as spreadsheet software.

You need the View team plans permission to perform this action.

Procedure

To export a team's plans to a .csv file:

  1. Go to the team timeline.

  2. View the period for the plans you want to export.

  3. Click the export icon  at the top-right, and then select Export data.

  4. Save the .csv file.

 Please note that only Plans that were created in the Team Timeline view are included in the .csv file. Plans that were created in the Resource Planning view or in the My Work, Calendar view will not be included.

Plans for members of multiple teams.

  • If users are members of team A and team B, their plans in team B are also displayed on the 'Team A' timeline. Similarly, when you export plans from team A, the .csv file also includes the plans from team B for those users.

  • The only team B plans for users that are members of both teams, that are not displayed on the 'Team A' timeline are team plans; that is, plans that were created on the team row (the top row) of the 'Team B' timeline. Although these plans are not displayed on the 'Team A' timeline, they are included in the .csv file.

Example

The following tables show the type of information that the .csv file contains. The fields are explained later on this page.

Planned for

User or team row

Planned for (team ID or username)

Plan item type

Project key

Plan item key

Plan item name

Plan item description

Plan summary

Planned time (hours)

Planned time (fraction of each working day)

Planned for

User or team row

Planned for (team ID or username)

Plan item type

Project key

Plan item key

Plan item name

Plan item description

Plan summary

Planned time (hours)

Planned time (fraction of each working day)

Habib Adebayo

user

habib

issue

TO

TO-15

Design usage reports

As an IOS user I need to be able to see reports about my usage

Preparatory work

16

0.5

GreenCloud Tango

team

5

version

TO



Tango 1.2

Version for June release



132

1

Start

End

Repeated instance of a plan

Repeat frequency

Repeat until

User row of a team plan (team ID)

Plan ID

Parent plan ID

Plan created

Plan created by

Last plan update

Plan last updated by

Scope type

Scope ID

Plan item ID

Start

End

Repeated instance of a plan

Repeat frequency

Repeat until

User row of a team plan (team ID)

Plan ID

Parent plan ID

Plan created

Plan created by

Last plan update

Plan last updated by

Scope type

Scope ID

Plan item ID

11 Apr 2016

14 Apr 2016

FALSE

NEVER





104



24 Mar 2016

jessie

8 Apr 2016

jessie

team

5

10330

13 Apr 2016

15 Apr 2016

FALSE

WEEKLY

25 May 2016



230



24 Mar 2016

jessie





project

10130

10222

The .csv file contains fields that are separated by commas when you view the file in a text editor:

"Planned for","User or team row","Planned for (team ID or username)","Plan item type","Project" ...
"Habib Adebayo","user","habib","issue","TO" ... "GreenCloud Tango","team","5","version","TO" ... ...

Fields

Field

Possible values

Examples of values

Explanation

Field

Possible values

Examples of values

Explanation

Planned for



"Habib Adebayo"

The name of the team member whom the work is planned for or, in the case of team plans, the name of the team.

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.

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.

Tip

You can also know the team ID from the URL of the team members timeline in Tempo Planner.

Plan item type

  • issue

  • project

  • component

  • version

  • sprint



 

Project key



TO

The project key of the project that is associated with the plan item. If the plan item is a project, then the Project key field and the Plan item keyfields contain the same key.

Plan item key



  • TO-15

  • TO



Content varies depending on the plan item type:

  • For components:empty field

  • For issues: Issue key

  • For projects: Project key

  • For sprints:empty field

  • For versions:empty field

Plan item name



  • "Design usage reports"

  • "Tango 1.2"

The name of the issue, project, component, version, or sprint.

Plan item description



  • "As an IOS user I need to be able
    to see reports about my usage"

  • "Version for June release"

The description of the issue, project, component, or version. If the plan item is a sprint, the field is blank.

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 (hours)



  • 16

  • 132

The number of work hours that are planned in the plan.

Planned time (fraction of each working day)



  • "0.75"

  • 1

On 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 is shown as a decimal fraction. For example:

tart



  • "2016-04-11"

  • "2016-04-13"

The start date of the plan.

End



  • "2016-04-14"

  • "2016-04-15"

The end date of the plan.

Repeated instance of a plan

  • FALSE

  • empty field



Repeat frequency

  • NEVER

  • WEEKLY

  • "EVERY TWO WEEKS"

  • MONTHLY

  • empty field



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.

User row of a team plan (team ID)



5

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 has a separate line in the data of the .csv file.

Tip

You can also know the team ID from the URL of the team members timeline in Tempo Planner.

Plan ID



230

Used by the Tempo Support organization for troubleshooting problems.

Parent plan ID



225

The ID of the earliest plan in the series of which the plan is a part. Used by the Tempo Support organization for troubleshooting problems.

Plan created



"2016-03-24"

The date on which the plan was created.

Plan created by



jessie

The Jira username of the person who created the plan.

Last plan update



"2016-04-08"

The date when a user last updated the plan.

Plan last updated by



jessie

The Jira username of the last person that updated the plan.

Scope type

  • folio

  • team

  • project



Used by the Tempo Support organization for troubleshooting problems.

Scope ID



  • 5

  • 10130

Used by the Tempo Support organization for troubleshooting problems.

Plan item ID



  • 10330

  • 10222

Used by the Tempo Support organization for troubleshooting problems. This field is also necessary if you import plans into Tempo Planner from a .csv file.

Importing plans from a CSV file