[Import CSV] Error importing issue

[RIZKY JTUASIKAL]

when we tried to import CSV into jira, we got the following error:

and we also attached the log.

A few days ago, we were able to import CSV into Jira.

However, as of today, we always get an error when importing.

[Jovin]

Hi @RIZKY JTUASIKAL 

Can you share your CSV file? Have you tried importing to a blank project to test if the file works?

[RIZKY JTUASIKAL]

Hi @Jovin ,

because I can't attach the CSV file here, Here's the data in our CSV file:

Issue type

Summary

Issue id

Parent

URL MoA

Supporting Documents of Approved Budget

MoA Signed Date

Proposed Budget - Hardware Server

Proposed Budget - Hardware Non Server

Proposed Budget - Software / Development Fee

Proposed Budget - Professional Service

Proposed Budget - From Previous Project

Budget Year

Budget Plan Name

MoA Number

MoA Title

Sisa MoA Total

Proposed Budget

IT Business Alliance

Status

Process Type

Linked Issue

MoA Project

NO 1 - Testing MoA Title

TPTM-1

https://jenius.atlassian.net/jira/software/c/projects/BTPNI/settings/details

https://jenius.atlassian.net/jira/software/c/projects/BTPNI/settings/details

17-Jul-24

10000000

0

0

0

10000000

2024

Testing

NO 1

Testing MoA Title

10000000

15

norbertus.wusana@btpn.com

In Progress

Project

TBSM-36

MoA Project

NO 2 - Testing MoA Title

TPTM-1

https://jenius.atlassian.net/jira/software/c/projects/BTPNI/settings/details

https://jenius.atlassian.net/jira/software/c/projects/BTPNI/settings/details

17-Jul-24

10000000

0

0

0

0

2024

Testing

NO 2

Testing MoA Title 2

10000000

10

norbertus.wusana@btpn.com

In Progress

Project

TBSM-36

hope it helps

[RIZKY JTUASIKAL]

Here's how it looks when we're mapping values

[Jovin]

Hey @RIZKY JTUASIKAL 

Apologies for the delay - could you perhaps remove the column for issue-id and make sure your URL are inside "" inside the ,, (e.g.

Issue Type,Summary,Parent,URL MoA,

MoA Project,NO 1 - Testing MoA Title,TPTM-1,"https://aosidjoaisjd"

Other than that, all I could suggest would be limiting down some of the fields and testing which one is incorrect. But from the logs it looks like it's the insert of the issue ID that's causing problems. 

[Jovin]

@RIZKY JTUASIKAL - How'd you go? Did removing issue ID from the import work?

[RIZKY JTUASIKAL]

Hi @Jovin ,

is still not working. :(

But we found another way, and we think it's enough to continue the process.

Thanks for your help, Jovin

I really appreciate it.

[John Funk]

Hi Rizky

Are there any other required fields to create a new issue for that Project and Issue Type? In other words, if you clicked the Create button on the screen and entered just those fields would it create the issue? 

[RIZKY JTUASIKAL]

Hi @John Funk ,

"if you clicked the Create button on the screen and entered just those fields would it create the issue? "
>> Yes, it will create the issue

[John Funk]

That screen print just shows the list of fields on the screen. Did it actually create a new issue? Can you share that with the field field in? 

[RIZKY JTUASIKAL]

Hi @John Funk ,

Here's a capture of the field information when creating the subtask:

[John Funk]

There's a lot more fields populated that then just the 3 in your spreadsheet. Can you Create an Issue by ONLY populating the fields in your spreadsheet?

[RIZKY JTUASIKAL]

Hi @John Funk ,

Sorry for the late update,

We found another way and we think it's enough to continue the process.

Thanks for your help, and I really appreciate it.

[John Funk]

Great- glad you can move forward.