Customers
User information
 Loading ...
Show article in Knowledge Base

 The issue Import file formatting Export knowledge base Export     SubscribeSubscribe      Show article info

You can get a sample import file by choosing the "import from CSV/Excel" function, and then clicking on "Download sample file".

This article outlines the format for issue fields in the file.

 

Note: The import function currently uses its own names for the issue fields, and unfortunately does not consider the names of the fields in the issue field configuration. So it is not possible now to export a file as xls, then adjust it and re-import it. (The exported file will use the field names as shown in the issue field configuration (say, "Status"), while the import file needs the specific format described below (for example "statusAsStr"). ).

 

If you import from a .csv file, it needs to:

  • use UTF-8
  • use semicolon separated values
  • use the correct "import names" of the imported issue field.

 

 

Importing from Excel files ( both .xls and .xlsx should be supported) were added in v9.7.

 

MANDATORY fields are issueTypeName and reportedByName

 

 

Default English name

of issue field

Name of issue field in the import file Mandatory? Type of data
Issue key issueKey

No, but will be created if not set.

If issue key of existing issue is given, the import will update that issue instead of creating a new issue.

Correctly formatted issue key
Parent issue key parentIssueKey   Correctly formatted issue key
Title title   Text
Status statusAsStr No, but will be set to the default status  if not set Name of an issue status
Resolution resolutionName   Name of an issue resolution
Issue type issueTypeName YES Name of an issue type
Severity severityAsStr   Name of an issue severity
Priority priorityAsStr   Name of an issue priority
Urgency urgencyAsStr   Name of an issue urgency
Escalation level escalationLevelAsStr   Name of an issue escalation level
Ticket id ticketId No, but if issue key is not given, and the ticket id matches an existing issue, the import will update that one instead of creating a new issue. Integer
Parent ticket id parentTicketId   Integer
Developer/Responsible responsibleName   Username of a user
Reporter reportedByName YES Username of a user
Published publishExternal   Yes/No
Owner ownerName   Name of a user
Owner username ownerUserName   Username of a user
Owner Group ownerGroup   Name of a user group 
Iteration versionName   Name of a version/iteration
Affected version affectedVersion   Name of a version
Est. Time estimatedTime   Decimal number
Remaining Time remainingTime   Decimal number
Actual Time actualTime   Decimal number
Start date startDate   Date + time
Due date dueDate   Date + time
Description description   Text
Solution solution   Text
Created createDate   Date + time. If not set, then this will be the time of import
Completed completionDate   Date + time. 
Billing amount billingAmount   Integer
Cost amount costAmount   Integer
Billable billable   Yes/No
Company customerName   Name of a Company
Product productName   Name of a Product/Config item
Product component productComponentName   Name of a Product/Config item
Release releaseName   Name of a release
SLA slaPlan   Name of a SLA
Source sourceName   The source of the issue
Source Direction sourceDirectionAsString    
Contract contract    
Responsible tester responsibleTesterName   Name of a user
       
       

User comments
 Loading ...