-
Type:
Bug
-
Resolution: Tracked Elsewhere
-
Priority:
Medium
-
None
-
Affects Version/s: 3.13
-
Component/s: Import / Export [Deprecated]
-
3.13
Fogbugz importer silently fails to create new project in JIRA, if the Fogbugz's project name is already used in JIRA with different project key.
The issues are imported to the already existing JIRA project and the Target project key specified in the first step of the import wizard is disregarded.
Steps to reproduce this behaviour:
- There is in JIRA project with the same name as the Fogbugz one but it has different project key.

- In Fogbugz there is a project with the same name and the importer is config to import it with a different project key.
# written by PropertiesConfiguration # Thu Oct 23 11:00:34 EST 2008 project.importJIRA = fogbugz project.Project2 = fogbugz link.Duplicates = Duplicate link.BugRelation = related value.sCategory.Bug = Bug value.sCategory.Schedule Item = Task value.sCategory.Inquiry = Task value.sFullName.Brian Lane = Critical value.sPriority.Must Fix = Critical value.sPriority.Fix If Time = Minor value.sCategory.Feature = New Feature value.sPriority.Don't Fix = Trivial
- Commit import finally JIRA will report in the UI "The importer has completed successfully without any errors." Also, no errors are reported in the log file check on import.log

The imported issues are placed in the existing project with its current project key.
- relates to
-
JRASERVER-15832 Fogbugz importer allows to dupicat existing project key in JIRA
-
- Closed
-