nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue migration CSV import issues

Aldo Cauchi Savona

Hi,

Migrating issues from JIRA server to cloud..

I created the custom fields on the cloud yesterday.

Today I did an export of 2 issues into a CSV from our JIRA server.

However, in the Map Fields step, the custom fields area that were created yesterday are missing from the JIRA field drop-down list, one that was created on Monday, however, is showing.

With regards to the Created and Creator field, I find no mapping in the list.

The Next button at the bottom of the page is disabled, Even if i mapped 4 fields.

On final query, is it possible to export the comments via a CSV export (all fields) without the use of a plugin?

Thanks.

Accepted answers

All comments

mfabris

Hey Aldo!

When you export to CSV make sure you choose "all fields" and not only the "visible fields".

All the comments will be in the export (you will find a column "comment 1", a column "comment 2" and so on).

When importing into a project, if you want to use a certain field inside the project, you have to go to "Custom fields" and make sure that the context of that custom field is extended to the project where you intend to use it.

If the context of the custom field is restricted and your target project is not included, then you will not find it, like it does not exist.

I hope this helps, good luck with your import

Aldo Cauchi Savona

HI @mfabris , while the comments are being shown correctly as custom fields in the CSV, in the import mapping, I do not get the option one where to place the comment(s).

I also am having trouble importing sub-tasks. I imported the story separately first, no problem, got the issue ID of the story in JIRA cloud and replaced the value in the CSV, but no luck.

Any help please?

Aldo Cauchi Savona

In some issues that have an existing user assigned to the issue, import validation still gives an error of:

Issue can't be created due to the error/s [ User '5ce3b3cb4326200dc97257c9' cannot be assigned issues. ]
Issue can't be created due to the error/s [ User '60e2d919e7b4fd006a53c01b' cannot be assigned issues. ]

how can I convert the weird user number reported into a valid under name, please?

mfabris

I think you should just map "comment" to "comment body" and that's it?

If you want to import tasks with subtasks, the procedure you describe is right...

I am not sure why this does not work in Cloud.

What do you get as an error? no links at all?

Are you actually importing a column "issue-type" that assigns the right issue type (subtask) to your subtasks?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud