Bulk Import of CSV shows Channel as "Unknown", causing custom fields not to display on tickets

[Tyson Neil Taber]

While using the external import system to import my csv, the tickets now (did not happen in the past) are being imported with an "unknown" channel, which is causing one of the custom fields I have created to not display on tickets created via bulk load.

Tickets I create by cloning, or from inside JIRA, have the proper channel expressed (JIRA, Portal, etc.) and those tickets (in the same project I'm bulk loading too) will display the custom field on the ticket.

I am sure the custom field is setup correctly as this has been working for some time now, and it still displays correctly on tickets created inside of JIRA, but the failure to be able to bulk load a specific "channel" (I tried and not possible), causes the tickets to create with an unknown channel, and then this particular custom field will not display on those tickets.

[Alec Jasanovsky]

Not 100% sure but while mapping fields, you may have hit the "Create Field" or something along those lines. It's right next to where you map the new field and I've made this mistake before. 

[Tyson Neil Taber]

Hmmm, the field that is now coming across as "unknown" is the JIRA inherent field of "Channel", it is not a custom field.  This field basically identifies "how" the ticket got into JIRA, either cloned from another existing, perhaps created through self service, or it used to put "JIRA" for bulk loaded tickets via csv.

This is not occurring anymore, and on the tickets created via csv, the channel now says "unknown" and only one of the several custom fields I have do not display, while the other do?

#imconfused

:D

[Tyson Neil Taber]

[Tyson Neil Taber]

The system shows that its not displaying due to no value, but the second picture clearly shows that a default value is set for this field, which has been working for quite a while now but is now not working?

[Alec Jasanovsky]

So regarding the Analysis ID, I would imagine the default value is set only when creating the ticket through normal means, whereas when importing, you’ve already supplied the options and therefore it will either go to whatever value is set in the form or a blank value as there is no value in the form. 

And for channel - Did it have a built in option of something like “imported from csv?” Or is channel never even given the option of mapping?

[Tyson Neil Taber]

Thats a great idea about mapping a value to the Analysis ID field, I had the same and tested and that did work, clunky to have to map a default value during csv import, but it did work! Thank you!

The channel used to show as JIRA when you did a csv import I'm pretty sure, and no it is never been a mappable field.

[Alec Jasanovsky]

Glad it was helpful! Ever get anywhere with the channel field?

[Tyson Neil Taber]

I did not, I was unable to bulk load anything into that field, it simply doesn't allow you to select that field when doing the bulk import function, it seems to be set by the way the ticket gets generated?

I will be doing some more bulk loading in the near future and will see if the channel imports differently or if I can find anything and report back!