Exporting Team Plans

Abstract

How to export Team Plans

Important

Exporting plans requires the View plans permission.

You can export a team's plan for a selected period to a comma-separated values (.CSV) file format and import the file into other software. 

  1. Select Planning planner_icon.png in the Tempo sidebar.

  2. Click ellipsis-button.png in the upper-right and select Timeline.

  3. Select a period and other view options.

  4. Click export-button.png and then Export data.

    Table 8. Fields in the export file

    Field

    Possible values

    Examples of values

    What it is

    Planned for

    "Habib Adebayo"

    The name of the team member for whom the time is planned, or the name of the team if it's a team plan.

    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.

    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 user name of the team member for whom the time is planned, or the team ID in the case of team plans.

    You can also find 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 Jira project that is associated with the plan item. If the plan item is a project, then the Project key field and the Plan item key fields 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

    Planned time shown as a decimal fraction.

    Start

    - "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

    - 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

    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.

    Repeat MONTHLY

    Plans are repeated based on the number of days in the original plan. 

    If a plan's repetition occurs on a weekend it will not be visible in the timeline. For example, if a plan is created on January 1, 2020 and is set to repeat monthly and end on March 31st, 2020, then the plans will not be visible since the 1st of both February and March occur on a weekend.

    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.

    - A team plan in the team row: empty field

    - A team plan in a user row: Team ID

    - An individual plan in a user row: empty field

    Plan ID

    230

    Used by Tempo Support 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 Tempo Support for troubleshooting problems.

    Plan created

    "2016-03-24"

    The date on which the plan was created.

    Plan created by

    jessie

    The Jira user name 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 user name of the last person who updated the plan.

    Scope type

    - folio

    - team

    - project

    Used by Tempo Support for troubleshooting problems.

    Scope ID

    - 5

    - 10130

    Used by Tempo Support for troubleshooting problems.

    Plan item ID

    - 10330

    - 10222

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