Difference between revisions of "Migration to mantis"
Line 13: | Line 13: | ||
AddDate date => date submitted | AddDate date => date submitted | ||
− | FixDate date => last updated | + | FixDate date => last updated/entry in mantis_bug_history_table |
− | Fixer varchar(80) => Fixer account | + | Fixer varchar(80) => Fixer account/entry in mantis_bug_history_table |
FixVersion varchar(30) >= Fixed in Version | FixVersion varchar(30) >= Fixed in Version | ||
Line 25: | Line 25: | ||
Prog text => program upload | Prog text => program upload | ||
− | Status` enum('Unfixed','Fixed','Unreproducable','Not a bug') | + | Status` enum('Unfixed','Fixed','Unreproducable','Not a bug') Fixed => Resolved/Closed; Unfixed => New; Unreproducable => Comment/Closed; Not a bug => Comment/Closed |
BugVersion varchar(8) => Product version | BugVersion varchar(8) => Product version |
Revision as of 11:32, 16 May 2006
The FPC bug repository will be migrated to mantis. This page collects the necessary steps to do so.
The current FPC bug db has the following fields with the given mapping:
BugId int(11) => custom field old bug id
Title varchar(128) default NULL => Summary
Name varchar(80) => additional information
Email varchar(80) => additional information
AddDate date => date submitted
FixDate date => last updated/entry in mantis_bug_history_table
Fixer varchar(80) => Fixer account/entry in mantis_bug_history_table
FixVersion varchar(30) >= Fixed in Version
Category tinyint(4) => Category
Descr => description
Prog text => program upload
Status` enum('Unfixed','Fixed','Unreproducable','Not a bug') Fixed => Resolved/Closed; Unfixed => New; Unreproducable => Comment/Closed; Not a bug => Comment/Closed
BugVersion varchar(8) => Product version
bugtype tinyint(4)
`comment` text
os varchar(10)