nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Accepted answers

All comments

Alec Jasanovsky_i9malr

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

Tyson Neil Taber

Screen Shot 2018-06-07 at 2.45.50 PM.png Screen Shot 2018-06-07 at 2.46.42 PM.png

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?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud