Warning from Issues > Import Issues from CSV

[Angie Affolter]

I'm trying to import using the Import Issues from CSV and am getting the warning:

The issue type [ Integration ] does not exist or it's not applicable for the selected project

We can Create issues just fine and can import many other issue types via the utility, but not sure why this particular issue type won't load.

It is Integration

[Radek Dostál · Accepted solution]

Are you using 'External System Import' wizard for admins, or the one from Issue dropdown for users?

You should be (at all times if you can) use the admin one as it has broader mapping options.

I presume you have "Issue Type" as a column in the .csv? If so, are you able to map the field value manually during the import - is the 'Integration' option selectable?

[Matt Doar]

 I refer to them as the CSV importer (original) and CSV Importer (wimpy) :)

[Angie Affolter]

It is the one under the Issue Dropdown.

When I took Radek's suggestion to map the value, it popped up TWO issue types named Integration.  I selected the second one in the list and it imported correctly.

Now, we just have to clean that mess up!

THANK YOU BOTH for your help in working through this!

Angie

[Matt Doar · Accepted solution]

Can you create Integration issues manually with the UI? The issue type has to be in the issue type scheme used by that Jira project

[Angie Affolter]

Yes!  That's the interesting part.  We are able to add them with Create button (UI), which would suggest it's available on the Issue Type Scheme (which we can see is the case). 

[Matt Doar]

Is the user running the import the same user that can create those issues in the UI? Could be permissions. The log file from the import may have more details too.

Or maybe that issue type has required fields (with *)?

[Angie Affolter]

Yes, and I am able to replicate the issue with my id and I'm have admin access. 

Log:

018-06-20 16:28:29,533 INFO - Importer started!
2018-06-20 16:28:29,533 INFO - Engine is running in Validation-only mode
2018-06-20 16:28:29,533 INFO - All issues will be imported to project: University Mississippi Medical Center (UMMC)
2018-06-20 16:28:29,533 INFO - Creating issue: [externalId='autoid-6579982523619456267', summary='FNI01a - Regions Bank Reconciliation']
2018-06-20 16:28:29,565 WARN - The issue type [ Integration ] does not exist or it's not applicable for the selected project. The affected issues will be created with issue type [ Action Item ]
2018-06-20 16:28:29,862 INFO - No problems found with issue 'FNI01a - Regions Bank Reconciliation'

I will check on required fields.

[Angie Affolter]

See above - duplicate issue types??  the importer took the first one in the list as default and it was the second one mapped to the issue type scheme. 

Thank you for helping me work through this issue!

Angie

[Radek Dostál]

Well, if it does import the issues (albeit different type), then maybe you could bulk move them to change it to 'Integration'.

I know, not ideal, but hey, it would get the job done.

Maybe it's just something random altogether that will go away after the next restart, or integrity checker will be able to catch it, etc. etc. Or maybe just making a copy of the issue type scheme and replacing it in the project would budge something.

Out of morbid curiosity you could try making 'Integrity' the default issue type in the scheme, and see if you can get a "can't find Integrity, creating 'Integrity' instead kinda warning in logs.

Well, I'm out of ideas.

[Matt Doar]

That's a good ideas about duplicate issue types. What if there was already one named "Integrity " with a trailing space

[Angie Affolter]

HMMMM, we'll have to look at that.