The Bug Genie
star_faded.png
Please log in to subscribe to updates for this article
CSVImport
Last updated at Thu Jun 12 12:15, by zegenie

Importing data from CSV files  ⇑ top

You can import data to The Bug Genie from a CSV file, pasted into the Import screen. Currently you can only import projects, issues and clients. This document explains how to use the Import feature.

Data must be provided in comma-separated format, with the first row containing column names (which have restrictions - see below). Column values should be enclosed in speech marks if appropriate - The Bug Genie will handle these correctly. In addition, The Bug Genie also performs a number of validation steps to ensure the data is valid, also explained below.

When the tables mention the 'column name', this is what should be in the first row to indicate the column. Some columns are required, some are optional, however if you specify a column in the header row it must be included in every subsequent row. Likewise, you can not specify data in subsequent rows which does not have a matching column marked in the header row.

Importing projects  ⇑ top

Column nameRequiredContainsOther details
nameYesProject namenone
prefixNoPrefix for project issue numbersBy specifying a prefix, the project will automatically use the prefix
workflow_idYesID number of workflow schemeUse 1 if you have no custom workflow specified
scrumNoShould scrum (Agile) development be used1 for yes, 0 for no
ownerNo (yes if owner_type specified)User or Team ID for project ownernone
owner_typeNo (yes if owner specified)Type identifier for owner1 for user, 2 for team
leadNo (yes if lead_type specified)User or Team ID for project leadernone
lead_typeNo (yes if lead specified)Type identifier for leader1 for user, 2 for team
qaNo (yes if qa_type specified)User or Team ID for project's QA responsiblenone
qa_typeNo (yes if qa specified)Type identifier for QA responsible1 for user, 2 for team
descrNoDescriptionnone
doc_urlNoURL for documentation websitenone
freelanceNoCan users edit issue properties without working on the issue1 for yes, 0 for no
en_buildsNoAre builds enabled1 for yes, 0 for no
en_compsNoAre components enabled1 for yes, 0 for no
en_editionsNoAre editions enabled1 for yes, 0 for no
clientNoID number of clientnone
show_summaryNoShould a summary be shown on the frontpage1 for yes, 0 for no
summary_typeNoWhat to show on the frontpageEither issuetypes or milestones
issuetype_schemeNoID number of issuetype schemenone
allow_reportingNoSet whether new issues can be reported against this project1 for yes, 0 for no
autoassignNoSet whether to automatically assign issues based on the leader for projects, editions and components1 for yes, 0 for no


Importing clients  ⇑ top

Column name RequiredContainsOther details
nameYesClient namenone
emailNoEmail addressnone
telephoneNoTelephone numbernone
faxNoFax numbernone
websiteNoWebsite addressnone


Importing issues  ⇑ top

Column nameRequiredContainsOther details
titleYesIssue titlenone
projectYesProject IDnone
descrNoIssue descriptionnone
reproNoReproduction stepsnone
stateNoType identifier for owner1 for closed, 0 for open
statusNoID for status valuenone
posted_byNoUser ID (NOT team) for issue posterIf not specified, importing user will be set
ownerNo (yes if owner_type specified)User or Team ID for issue ownernone
owner_typeNo (yes if owner specified)Type identifier for owner1 for user, 2 for team
assignedNo (yes if assigned_type specified)User or Team ID for issue assigneenone
assigned_typeNo (yes if assigned specified)Type identifier for assignee1 for user, 2 for team
resolutionNoID of resolution valuenone
issue_typeYesID of issue typenone
priorityNoID of priority valuenone
categoryNoID of category valuenone
severityNoID of severity valuenone
reproducabilityNoID of reproducability valuenone
votesNoNumber of votesnone
percentageNoHow much of the issue is complete0 to 100 inclusive
blockingNoDoes the issue block the next release1 for yes, 0 for no
milestoneNoID number of milestonenone





Categories: Help

Article attachments

There are no file attached to this article

Article comments (1)