Bulk import but for a selected Issue Type

[Eleni Timini]

I have a project that has 2 issue types.

Although I set the bulk import to use a specific issue type, it creates the issues under the other type. 

[Nic Brough -Adaptavist- · Accepted solution]

How are you mapping the issue type from the import file?  Is the target issue type at the issue level and not sub-task?  Is the "other type" the default issue type for the project?

[Eleni Timini]

I have an Issue Type column and I put the name of the issue type, although I don't think this is correctly mapped so not too sure how to do it now because is expecting a JIRA field and this is not a field, but the type of the issue

[Nic Brough -Adaptavist-]

Ok, that's correct, but you need to do some mapping in the Jira import for issue type.  It doesn't take the string as is, you still have to say "where you see Bug in my file, that means the issue type called Bug in Jira".

That is, unless I'm not looking at the same import process you are doing.

Can you run us through what you are doing to import?

[Eleni Timini]

ok, cool sure i can take you through, with screenshots or do you have a different way?

[Nic Brough -Adaptavist-]

A quick text description would be enough - for example

Login -> Admin -> System -> External system import -> CSV

is the one I usually think of when the word "import" is used.

[Eleni Timini]

Create -> Import Issues -> Choose File - Select csv file to import -> Next -> Import to Project (Company Data) -> Next -> Select the field to do mapping -> Next -> Begin Import - so from the above, there is nowhere I can say what the Issue Type is.

[Eleni Timini]

Any updates on this one?

[Nic Brough -Adaptavist-]

Sorry, wandered off to another computer (I'm "working" with four at the moment, thanks to clients)

That process is fine, but it's missing a section.  When you get to "select the field to do mapping", you should get a list of fields from your CSV and a set of questions about what field to map them into.  So, for example, in my last csv, I mapped "summary" into "Summary", "text" into "Description", "ty" into "issue type" and so on.

But, I also ticked the ☐ next to "ty -> issue type".  The next screen asked me what to map the file values to in the issue type column, where I did things like "story -> Story", "task -> Task", "item -> Issue" and "Bug, Feature, and six-leg all go to Bug".

If you don't do that issue type mapping, the importer doesn't know what issue type to use, and will just use the default for the project.

Note that you should do this mapping even when the string in your CSV is identical to the name of the issue type in Jira!  And even if you only want to import one issue type that isn't the default in the project.

[Eleni Timini]

I do get the step for mapping fields from csv and JIRA fields. But Issue Type is not a JIRA field. I am definitely missing something here but it doesn't come through the wizard.

Not sure if I can attach screenshots from here 

[Eleni Timini]

Also, when I try the import and look at the details i get this:

2021-10-20 12:43:05,700 INFO - Creating issue: [externalId='autoid-533004130448239585', summary='Boliden']
2021-10-20 12:43:05,705 INFO - Issue does not have issue type selected, the affected issues will be created with issue type [Task]
2021-10-20 12:43:05,794 INFO - No problems found with issue 'Boliden'

[Eleni Timini]

Any updates on this? 

[Nic Brough -Adaptavist-]

Sorry, but I'm offered Issue Type in the field mapping, so I don't know what you're missing.  Could you already have mapped it to another field?

[Héctor Zárate]

Hi,

I have the same problem. In the screen to do the mapping, the list to select to what to map in Jira there is no way to select the Issue Type. See:

[Eleni Timini]

This is purely because JIRA does not allow you to select Issue Type if you don't do this through the "admin" part.

In the end, I had to do all the imports for others in my organisation as I am an admin and I ended up getting lots of emails regarding issue moves etc, which I could only got round with by disabling emails to myself.

Something JIRA does not care again to fix and just say that "this is how it works"

Very frustrating indeed

[Héctor Zárate]

Hi Eleni,

You are right. I just tried to do it from the Admin panel, and then I can select it:

But exactly as you just wrote, this is frustrating, because I need non-admin users to be able to import tickets and the import list will have different issue types.

It is a pity that Atlassian does not want to consider these low-hanging fruit enhancements.

[Eleni Timini]

Exactly, welcome to my world!

Plus I spent about 2 weeks trying to figure out what the issue was because even when I am an admin, I was going through the steps you would follow, i.e. press the import bulk button, not through the admin part. JIRA support was telling me that they could do it, but I couldn't, 2 weeks later after a lot of correspondence, they sent me a video of how they do things and then it clicked!

I mean.... even if I say that is not there, this is something that you should pick up immediately, isn't it? If i say that issue type is not available to me, they should know that its because I am going through a different route than the admin part.

But why have this import button available to a normal user if there are things that you can't do? 

NONSENSE

[Héctor Zárate]

Completely agree. This functionality for a normal user with this limitation makes the functionality useless.

[Eleni Timini]

or, it should be more visible to users so they know what they are doing and not wasting their time

[Joseph Cordasco]

This is bonkers. The import from the system does not allow you to define a delimiter like doing it the other way does.