We have a JIRA 7.10. project up and running in Production and as jira-administrator, just tried to import 100 new Issues by going to Admin->External Import and selected CSV <= the actual wording might be a little off.The 1st thing we noticed was our saved configuration file only mapped to a handful of custom fields whereas all fields had previously mapped - so we manually remapped everything.The import seemed to have no errors but when we ran Validate we had many warnings that basically said,The value <some value> "cannot be added to the custom field.""The value NULL="<some value>"cannot be found or is in the incorrect format."It seems if a value was not already present in a Single/Multi-list custom field - that value was not being added to the list and not used in the imported Issue.Example: If I have a single-list "Example" that has the valuesABand I wanted to add an Issue that contained single-list Example value "C" - I would get the WarningThe value C cannot be added to the custom field. The value NULL="C" cannot be found or is in the incorrect format.I've read some of the previous situations that people have had with importing CSV files but haven't seen anything quite like this.Any suggestions or things I can try to make this work?What will happen if I just ignore the warnings and allow the import to finish?Note: Before trying this import in Production I ran the import multiple times on my laptop using the exact same Project, Issues, Screens, FIelds, CSV and Configuration files and it worked every time without Errors or Warnings.Jim

DO NOT useIssues->Import from CSVALWAYS USEAdmin->System->External Import->CSV

Community
Q&A
Jira
Questions
Validation Warnings from CSV External Import

Create table in JIRA dashboard of overdue vs ontime issues in Current Sprint

Hi,

I want to create a single table in a dashboard where I can get:
Total issues in each sprint

Overdue issues in each sprint.

On time issues in each Sprint.

Please suggest possible solutions.

2 answers

1 accepted

2 votes

Answer accepted

DO NOT use

Issues->Import from CSV

ALWAYS USE

Admin->System->External Import->CSV

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Hi @[deleted]!

You sure the custom filed/schema/permission not different between test and prod?

Custom field name, list of values, visible etc. has identical customization?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks for replying Andrew.

That's exactly what I'm checking on today because something must be different somewhere.

I'll get back to you to know what I find.

Jim

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Quess what?

The problem was that the user was using the

Issues->Import from CSV

and not

Admin->System->External Import->CSV

Running Admin->System->External Import->CSV produced a perfect import.

Jim

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Create table in JIRA dashboard of overdue vs ontime issues in Current Sprint

2 answers

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events