How to Import worklogs into Jira using CSV Edited

Hi,

One of the team member has accidentally deleted around 3000 + worklog records from the production system. We have the data backup and trying to import them back to Jira and we are facing the below issue while doing this.

1. We use Tempo and trying to import the work logs
2. We have understood that tempo doesn't provide bulk import of work logs through excel/csv
3. We are using External system import, and are unable to map different users for the same issue in the mapping section. For example, an issue contains 10 users and their corresponding logged work but we are finding difficulty to map to different users.

The fields which are facing difficulty are 'Log-work ' fields which we are unable to during mapping [kindly see the atatched for reference]

 

Worklog_1.PNG

Any information or help provided will be really appreciated.

 

Thanks,

Vijay

3 answers

This widget could not be displayed.
This widget could not be displayed.

Hello Vijay

 

Here is my sample for worklog CSV import. The first line is the CSV header, the next lines are the data for worklog entries.

What is important for worklog import is that there are some required columns for the CSV importer, you have to place in your CSV. That is why the "pj_name", "pj_type", "pj_key", and "Summary" columns are in the CSV.

What info do you need for a worklog entry?

1.) which ISSUE is the task the user worked on->issue_key column

2/a worklog entry description
2/b Day of work
2/c time the work started 
2/d user who worked 
2/e work duration (JIRA only accepts in seconds)

the 2.) a+b+c+d+e data is in the "Worklog" column

You can see, the column delimiter is (,), but inside the "Worklog" column the worklog entry data delimiter is (;)

Unfortunately JIRA CSV import documention does not really describes it. 

So the sample CSV below contains the necessary columns for the CSV importer ("pj_name", "pj_type", "pj_key", and "Summary"), and contains the necessary columns for the worklog entry ("issue_key" and "Worklog")

The Summary column contains the summary field text of the ISSUE where you want to import the worklog entry.

issue_key,pj_name,pj type,pj_key,Summary,Worklog
RRIMPF03-10,RR-IMP-F03 RFP,software,RRIMPF03,Summary of the ISSUE,worklog entry description1;2017.11.09 12:30;mlipcsik;3600
RRIMPF03-10,RR-IMP-F03 RFP,software,RRIMPF03,Summary of the ISSUE,worklog entry description2;2017.11.09 13:30;mlipcsik;3600
RRIMPF03-10,RR-IMP-F03 RFP,software,RRIMPF03,Summary of the ISSUE,worklog entry description3;2017.11.09 14:30;mlipcsik;3600
RRIMPF03-10,RR-IMP-F03 RFP,software,RRIMPF03,Summary of the ISSUE,worklog entry description4;2017.11.09 12:30;mlipcsik;3600

 

CSV import steps:

1.) Select the CSV file and [Next] button

2.) Select "Defined in CSV" on the "Import to project" option

3.) Date format is dispayed the system default date format, and you have to use the same format in your CSV. My date format is "yyyy.MM.dd HH:mm", that is why I use "2017.11.09 12:30" in my CSV

[Next] button

4.) JIRA field mapping page, map the fields like this:

CSV field - JIRA field

Summary - Summary

Worklog - Worklog (in seconds)

issue_key - Issue Key

pj type - Project type

pj_key - Project key

pj_name - Project name

I did not checked any "Map field value" options, but it also works, if you check it.

[Next] button

[Begin import]

That is all.

Hope this helps you for your worklog entry import. 

This widget could not be displayed.

Here is my sample for worklog CSV import. The first line is the CSV header, the next lines are the data for worklog entries.

What is important for worklog import is that there are some required columns for the CSV importer, you have to place in your CSV. That is why the "pj_name", "pj_type", "pj_key", and "Summary" columns are in the CSV.

What info do you need for a worklog entry?

1.) which ISSUE is the task the user worked on->issue_key column

2/a worklog entry description
2/b Day of work
2/c time the work started 
2/d user who worked 
2/e work duration (JIRA only accepts in seconds)

the 2.) a+b+c+d+e data is in the "Worklog" column

You can see, the column delimiter is (,), but inside the "Worklog" column the worklog entry data delimiter is (;)

Unfortunately JIRA CSV import documention does not really describes it. 

So the sample CSV below contains the necessary columns for the CSV importer ("pj_name", "pj_type", "pj_key", and "Summary"), and contains the necessary columns for the worklog entry ("issue_key" and "Worklog")

The Summary column contains the summary field text of the ISSUE where you want to import the worklog entry.

issue_key,pj_name,pj type,pj_key,Summary,Worklog
RRIMPF03-10,RR-IMP-F03 RFP,software,RRIMPF03,Summary of the ISSUE,worklog entry description1;2017.11.09 12:30;mlipcsik;3600
RRIMPF03-10,RR-IMP-F03 RFP,software,RRIMPF03,Summary of the ISSUE,worklog entry description2;2017.11.09 13:30;mlipcsik;3600
RRIMPF03-10,RR-IMP-F03 RFP,software,RRIMPF03,Summary of the ISSUE,worklog entry description3;2017.11.09 14:30;mlipcsik;3600
RRIMPF03-10,RR-IMP-F03 RFP,software,RRIMPF03,Summary of the ISSUE,worklog entry description4;2017.11.09 12:30;mlipcsik;3600

 

CSV import steps:

1.) Select the CSV file and [Next] button

2.) Select "Defined in CSV" on the "Import to project" option

3.) Date format is dispayed the system default date format, and you have to use the same format in your CSV. My date format is "yyyy.MM.dd HH:mm", that is why I use "2017.11.09 12:30" in my CSV

[Next] button

4.) JIRA field mapping page, map the fields like this:

CSV field - JIRA field

Summary - Summary

Worklog - Worklog (in seconds)

issue_key - Issue Key

pj type - Project type

pj_key - Project key

pj_name - Project name

I did not checked any "Map field value" options, but it also works, if you check it.

[Next] button

[Begin import]

That is all.

Hope this helps you for your worklog entry import. 

Naveen I'm New Here May 02, 2018

Hi Marton,

I didn't find Work log in JIRA field mapping page, is that a custom field.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

175 views 2 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you