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; } } }

Why Can't I Update Tasks Via CSV?

Dalectric

I'm sure I've updated tasks in JIRA via CSV before and followed the instructions for doing this as listed here

https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html

If I leave the summary field empty then JIRA says

Issue can't be created due to the error/s [ You must specify a summary of the issue. ]

However if I populate the summary field with the original titles in then creates new tasks instead.

Has something changed with the plugin or is there a setting on my server I need to change?

(Tested on 7.4.4. and 7.6.4)

Edit:

Plugin jira-importers-plugin 7.1.30 & 8.0.4

Further to this the log file has the following

Caused by: com.atlassian.jira.plugins.importer.imports.csv.ImportException: Blank summary detected. Such issue cannot be imported

Accepted answers

Kian Stack Mumo Systems

Dalectric,

Are you using the "Key" field within JIRA? You need to make sure that you have the issue key as a column that you map in JIRA.

Perhaps you could gentrify the CSV and we can see what you are doing?

All comments

Kian Stack Mumo Systems

Dalectric,

Are you using the "Key" field within JIRA? You need to make sure that you have the issue key as a column that you map in JIRA.

Perhaps you could gentrify the CSV and we can see what you are doing?

Dalectric

Thanks for the reply, yep we have the key as the first column (Issue ID)

Your reply has pushed me in the right direction of the fix though.

The import was originally attempted by a user who is only a project admin and not a system admin. Therefore they were using the import from the Issues - Import Issues from CSV menu.

When you are mapping fields there is no option for Issue Key (for whatever reason) - they were using Issue ID as they incorrectly assumed this was the Issue Key field.

2018-04-18 09-03-47-External System Import - JIRA - DSUK.png

However if you do the same thing as a system admin from the System - External System Import - CSV menu you can select Issue Key

2018-04-18 09-06-26-External System Import - JIRA - DSUK.png

So I can now import and update existing tasks. I don't know why this difference exists and it doesn't appear to be mentioned in the documentation so I'll probably contact Atlassian to try and understand the differences.

Thanks for the prompting and getting us looking in the right direction.

Olivia Schultz

Hi there,

Did you manage to find a reason for this?

Dalectric

Hi, not yet as I forgot to follow it up, but I'll try and do that today.

Welcome!

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

Quick Links

Find more posts tagged with

csv

jira