Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with Jira Issue import

Ari Davidow September 24, 2018

I have been trying to pull in some data from cvs into Jira. Most things work perfectly, but I have a couple of significant problems with the "Description" field.

  1. In the fields I am importing, a dot "." appears as part of some of the field names. On import, the "." is sometimes interpreted as a command (most often, turning the succeeding text bold--even though we aren't talking about ".b" or ".B").
  2. I have not figured out how to import CRs. What exists as a CR in the CVS file gets ignored (turned to a space?) on import. This messes up the specific data.

Is there a list of reserved symbols and which to escape how?

Even better, is there a way, similar to HTML's <code> tag, so simply mark the contents of a field as "treat this literally" so that I don't have to massage the text and potentially introduce new problems?

Many thanks,
ari

 

1 answer

0 votes
Keri
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 25, 2018

Hi Ari,

 

If you encapsulate the data in quotes then it should be treated literally:

https://confluence.atlassian.com/adminjiraserver072/importing-data-from-csv-829827152.html#ImportingdatafromCSV-EncapsulatingJIRAdatastructureinyourCSVfile

 

Could you perhaps share an example of a line or two of CSV which don’t display as intended along with how it imports and what you’re expecting?

 

This may help us better understand your questions.

 

Cheers,

Keri

Ari Davidow September 26, 2018

Hi Keri, 

It looks as though that is what I did:

Issue Type,Description,Summary,Reporter,Priority,Status,label
New Feature,"RxConnect:
CHECKIN_DELIVERY.*

RxConnect:
INVENTORY_ACTIVITY.*

AIM/CIM:
CIIM_CHECKIN_DELIVERY.*
IN_EXCEPTION_LOG.*.dat (looks LIKE recently deployed)
CIIM_CONTAINER_INVOICE_XREF.*
CIIM_INVENTORY_ACTIVITY.*
INVOICE_ACTIVITY.*
CIIM_NON_CONTROL_RETURN_ACTIVITY.*
CIIM_TRANSFER_ACTIVITY.*
ORDER_ACTIVITY.*

Category Shrink: (Mainframe)
IR262_RX_SHRINK_*.TXT
",Ingest Inventory --NON BCG (RX),adavidow,Medium,To Do,Data Ingestion

 

Any idea why this is not working as expected? The data arrived, but the CRs did not, and some ".I" sequences triggered in/out of bold mode.

Ari Davidow September 26, 2018

I tried the import again, and it works as expected. Not sure what the problem was--if I added the quote marks later and forgot to retest, or if something went wrong the first time through.

One remaining question--I cannot find a "status" field to map to. Possibly anomaly on our customization? And why do I have to manually map like-labeled fields? E.g., if I have a CVS field labeled "Summary," why is it defaulting to "do not map" instead of to "Summary"?

Keri
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 26, 2018

Hi Ari, 

 

Status is not a field, but a part of a workflow - showing the current status of the tickets. See Working with workflows.

 

You should be able to save your mappings in a separate file after importing, which will speed up this process. But check your settings, have you checked Map Field Value for this particular column? To use the values from the CSV, you need just to map the column to the Corresponding JIRA field.

 

Cheers, 

Keri

Ari Davidow September 27, 2018

Excellent. Will explore. In the meantime, am I correct in concluding that "pre-Jira" status can not be imported? (Not a show-stopper, but it would have been nice.)

Keri
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 27, 2018

Hey Ari, 

 

Status can only be mapped to existing workflow statuses in JIRA. If not specified in your CSV file, imported issues will be given the default (i.e. first) Status as specified in your JIRA system.

 

So if you haven't created it in Jira, you won't be able to import them in unfortunately. 

 

Cheers, 

Keri

Ari Davidow October 2, 2018

Many thanks. I was able to do the import as it should have worked, within the limits noted above.

1. We do have a workflow set up in Jira. What I can't figure out is how to map to a specific status. Possible?

2. In the documentation (e.g., https://community.atlassian.com/t5/Jira-questions/CSV-import-with-multiple-comments/qaq-p/630263) it looks as though I can import comments--even multiple comments. But have been unable to find any way to map such fields to anything called "comment" or "comments"

What am I missing?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events