Why do I need a Summary Mapping when I'm already providing an Issue Key Mapping?

When I'm performing an Import from a CSV file, why do I need a Summary Mapping when I'm already providing an Issue Key Mapping?

 

The data I'm trying to map to the current issues does not have the Summary field so this is impossible to import the data.

1 answer

0 votes

Summary is the only field in JIRA that you absolutely have to fill in when doing an import from CSV (and the rest of the time actually).  It can never be left blank.

No, that's not what I said.  Summary is mandatory, but it's not a key.

But why? I'm supplying the Issue Key, so the importer should know which issue to put the Comment Body against. It makes no sense to require the summary too. The Comments I'm trying to import and stored in a table that links via the Issue Key, so the Summary isn't available.

Ah, you don't need the summary if all the updates have a key so that it's clearly an update.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,333 views 12 19
Read article

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