Import worklogs using the native JIRA csv import - JIRA Cloud

Worklogs can be imported into Tempo using the native Jira .csv import functionality when no worklogs attributes are added to your Tempo instance.
The Jira .csv import does not support Tempo worklog attributes, so if you need to import worklogs with worklog attribute values, you will need to use the Tempo Cloud REST API with a tool like Postman or by using the command line.

More information for the csv import options in Jira can be found in the Atlassian documentation

When importing worklogs into Jira, you need to prepare a csv file. This can be done in a text editor/spreadsheet that offers the option to save a file in .csv format (e.g. Excel).
The first line of the file will be used for the header row in your .csv output file or Excel.
The .csv header looks like this:

Project Name,Project Key,Issue Key,Summary,Worklog,Project Type

This is how the csv  file should look when opened in a spreadsheet:

You will need to put the strings together separated by a “,” as it acts as the delimiter in the .csv file. The entries for the worklog  information is split into 4 sections which are separated by a ";"

1. Worklog description

2. Worklog date

3. Worklog author (Atlassian user account id)

4. Worked seconds

When opening the file in a text editor, the information should look like the example below

Project Name,Project key,Issue Key,Summary,Worklog,Project Type
Tango OnDemand,TO,TO-23,Account field not populated,Branching;2022-05-08;557058:1878e103-4b49-40f9-bd1b-9aad9d0b1234;14400,software
Tango OnDemand,TO,TO-26,another try to add a team field,Testing during the webinar;2022-05-08;567058:0078e103-4b49-40f9-bd1b-9aad9d0b1234;3600,software

This file can then be used to import the data in Jira Settings, System, External System Import, CSV, and following the steps that are provided in the import wizard.