JIM-1673 - csv import does not read mapping correctly

• JIM-1663 - JIM Configuration file is now correctly saved when using Project Templates
• JIM-1646 - Mantis Importer now allows to customize Issue Type mapping
• JIM-1648 - Mantis Importer will no longer raise false-positive warnings when importing issue links

JIM is now using project templates.

- Fixed importing of Sample Data into Jira

- Fixed project creation via JIM

• JIM-1596 - fixed compatibility with Jira 6.2+
• JIM-1592 - FogBugz comments are now correctly striped out of HTML tags
• JIM-1544 - FogBugz now correctly import case description when it comes from e-mail
• JIM-1535 - CSV Importer will no longer crash when uploading zip files
• JIM-1335 - FogBugz importer now correctly detects the case comments

• JIM-1502 - JIM no longer adds unused Custom Fields when importing from FogBugz
• JIM-1484, JIM-1514 - Fixed importing of dates in CSV Importers
• JIM-1483 - Fixed importing Time Tracking in Legacy Mode
• JIM-1535 - CSV Importer no longer crashes when uploading zip files
• JIM-1544 - Fixed importing of Description and comments in Fogbugz Hosted importer

• JIM-701 - JIM will now correctly download issues from FogBugz OnDemand instances with more than 100000 issues
• JIM-954 - FogBugz will no longer fail when CDATA element is found in case data.
• JIM-1434 - JIM will now correctly respect Jira text limits
• JIM-1449 - JIM will no longer wipe Component/s Fix Version/s and Affected Version/s fields during CSV update
• JIM-1453 - JIM will no longer return 500 page, when trying to download non-existing import log file
• JIM-1454 - FogBugz Importer will no longer hide inner exception that may occur during case parsing
• JIM-1460 - Fixed bug, that JIM was not importing attachments from FogBugz
• JIM-1461 - Fixed a bug that CSV Importers were incorrectly importing dates to Custom Fields
• JIM-1467 - fixed version text alignment in External Issue Import menu

• Added support for linking issues in admin and non-admin CSV Importer
• Added support for subtasks in non-admin CSV Importer

• JIM-1386 - JIM will no longer create users without e-mail address.
• JIM-1415 - JIM will no longer fail while importing to Custom Field without options
• JIM-1409 - Bulk Create will now correctly import assignees and reporters with changed usernames

• JIM-1367 - Bulk Create value mapping will now correctly detect value mapping settings in Validation step
• JIM-1400 - Fogbugz Hosted importer no longer caches all issues during import - this allows user to import large Fogbugz instances.
• JIM-1401 - JIM no longer applies timezone information to Date-only fields
• JIM-1404 - Fixed a bug on Bulk Create setup page that maximum attachment size was not displayed
• JIM-1406 - Bulk Create will now correctly import Time tracking data
• JIM-1407 - Bulk Create will now hide time tracking mappings, if they are not visible on Create Issue screen.

• JIM-1385 - Bulk Create now requires Bulk Edit permissions
• JIM-1378 - Fixed a bug that Bulk Create was not always available for non-admins.

Two completely new features added!

• JSON Importer is now available via REST
• Bulk Create! CSV Importer for non-admins with Validation step

JIM-1343 - fixed Critical bug which was causing Importer to crash with older versions of Jira Agile

JIM-1328 - better informations about Attachments errors

JIM-1327 - Fixed a bug which was causing Importer to crash when trying to add inactive user to Developers role

JIM-1326 - Fixed bug in FogBugz importer which was populating External Issue URL with incorrect link

JIM-1324 - Fixed creating of Issue Types by CSV and JSON Importers

JIM-1323 - Fixed importing of Sprint via CSV / JSON Importers

JIM-1318 - Importer log will no longer duplicate informations

JIM-1301 - Fixed FogBugz Importer to correctly import attachemts

JIM-1039 - JSON format now allows user to specify link sequence

JIM-1274 - Improve Bugzilla Importer performance

JIM-1273 - Support Bugzilla up to 4.4.4

JIM-1269 - Improved handling on Epic Links in CSV and JSON importers

JIM-1268 - Watchers importing is now available in CSV importer

• JIM-825 - fixed a bug which caused that Resolved Date was resetted after importing watchers
• JIM-1111 - small internationalization fix
• JIM-1155 - Moved "New Custom Field" to Custom Field Section in CSV Importer
• JIM-1156 - Fixed missing link on JSON Setup page
• JIM-1163 - JIM will now correctly set next issue number in project based on maximum imported Issue Key

• JIM-1262 - Added 'startDate' property to version in JSON Importer
• JIM-1257 - FogBugz users are now correctly imported
• JIM-1231 - CSV Importer now respects the user time zone settings
• JIM-1228 - CSV Importer will no longer display missleading warning about comments parsing
• JIM-1152 - Fixed the bug that time entries were deleted after updating issues
• JIM-1030 - Fixed the bug that Issue types were changed after update
• JIM-1008 - We now fully support FogBugz up to 8.8.xx
• JIM-1000 - Description value is now correctly set during FogBugz import

End of beta for JSON Importer!

Additonal Bugfixes:

• JIM-1251 - JIM will no longer redirect user to blank page, when using incorrect Base URL
• JIM-1242 - Updated messages in JSON importer
• JIM-1239 - Update JIM to work with clustered Jira
• JIM-932 - Validating usernames before create
• JIM-919 - JIM will now correctly respect Workflow validators and conditions

New in the release:

• JIM-787 - Support for all Custom Field Types in CSV and JSON Importers
• JIM-1148 - We are supporting Mantis up to 1.2.16!

Bugfix:

• JIM-1210 - CSV manual mapping fixed
• JIM-1194 - Better support for Project Lead in JSON Importer
• JIM-1178, JIM-1153 - Fixed messages on Finish Screen
• JIM-1137 - Fixed bug with importing issues with assignes as inactive users
• JIM-1135 - Fixed bug on Project Mapping Step which didn't allow user to repick projects
• JIM-1126 - Fixed importing of Mantis versions
• JIM-1120 - Removed missleading error while importing CSV files with Issue Key mapping
• JIM-1097 - JSON Exported issues has now History informations
• JIM-1080 - JSON Importer is now correctly importing inactive users
• JIM-1033 - Fixed bug that CSV Importer was crashing while trying to create a new Priority on "Map values" step

Fixed in this release

• Fixed a bug in Project Mapping step which didn't allow users to see external projects
• Fixed a bug that Trac importer allowed to import attachments with illegal filenames
• JIM will now respect Field Configuration Settings and put default values in empty required fields.
• Added additional warning for user when importing Projects via CSV file

• Fixed problem when JIM sometimes did not recognize that GreenHopper is installed and enabled.
  
• UX improvement around project selection page 
  
• Added support for Trac 1.0+ attachments
  

Small fixes and Jira 6.0 compatibility.

Fixed bug in Mantis importer which caused import failures whenever some fields where null in the database.

JIM-859 support for Mantis on Microsoft SQL Server

You can now easily write your own plugins using developer API that this Jira Importers Plugin introduces.

First official version that's compatible with incoming Jira 5.2

Bug

• [JIM-763] - JSON import results in an exception when "author" is not specified for a change group
• [JIM-765] - Weird crash importing JSON data when it thinks JODA period is invalid
• [JIM-769] - Sub tasks do not import correctly (silently ignored)
• [JIM-770] - Each import results in a new "External issue ID" custom field even though it's not needed
• [JIM-773] - Change period handling
• [JIM-775] - Controllers should not share the same importer engine
• [JIM-778] - OnDemand throws Stacktrace after selecting csv file
• [JIM-793] - Finished import logs page doesn't contain details
• [JIM-805] - JIM bundles its own library versions, which are subsequently leaked by its API

Improvement

• [JIM-786] - Custom fields cannot be specified by id in JSON, impossible to select the correct custom field
• [JIM-797] - Allow importing into custom fields that have specific issue types AND have a global context

New Feature

• [JIM-421] - It's possible to create sub-tasks to issues existing in Jira
• [JIM-766] - Allow for 'Released' versions in JSON import
• [JIM-771] - No way to set a custom field from JSON
• [JIM-772] - JSON importer should support comments
• [JIM-789] - Allow to set a Project Avatar when importing from JSON

Story

• [JIM-724] - As an admin I would like JIM to import the new PT Epics
• [JIM-794] - Read correctly timestamp format used in Trac 0.11.x

Release Notes - Jira Importers Plugin - Version 4.3.3

** Bug
    * [JIM-763] - JSON import results in an exception when "author" is not specified for a change group
    * [JIM-765] - Weird crash importing JSON data when it thinks JODA period is invalid
    * [JIM-769] - Sub tasks do not import correctly (silently ignored)
    * [JIM-773] - Change period handling
    * [JIM-775] - Controllers should not share the same importer engine
    * [JIM-788] - Null pointer when export JSON(Beta) view in issue navigator

** New Feature
    * [JIM-771] - No way to set a custom field from JSON
    * [JIM-772] - JSON importer should support comments

To export issues in JSON (beta) format you need to enable JSON (beta) modules in Jira Importers plugin.

Fixed also link to other importers available in the Marketplace.

Fixed a bug that left some custom fields not editable after the import.

This release brings Jira 5.1 compatibility.

Overall improvements

• automatically add assignees to Developers role for a project
• experimental JSON exporter and importer

Changes to CSV importer

• it's possible to specify attachment uploader, date/time and description
• you can import worklogs
• you can set issue key
• importing local attachments

Changes to FogBugz importer

• works now with FogBugz 8.7.60
• it's possible to reuse configuration for FogBugz OnDemand importer

Mantis importer works correctly with PostgreSQL database

This version brings a set of improvements/fixes:

• a few compatibility fixes with Internet Explorer
• full compatibility with the newest version of Pivotal Tracker (SaaS)
• support for very big Pivotal Importer projects (before up to 3000 stories per project were supported)
• compatibility with improved Add Project dialog in incoming Jira 5.0.3
• support for Multi Group Picker / Multi User Picker custom field in CSV importer

This version includes also a few fixes from unpublished on PAC two preceding JIM versions: 4.1.1 and 4.1.2.

Custom fields are now created with a limited scope.

CSV fields can be mapped only to supported custom field types.

Mantis importer preserves version's date and release status. Also Mantis 1.2.8 is now supported.

Bugzilla 4 with votes disabled doesn't break the import.

Jira 5.0 compatilibity!

CSV minor improvements when reading complex multiline fields. Proper ordering for subtasks imported from CSV.

HTTP/HTTPS proxy support for all importers.

Importing component leads from FogBugz.

Only enabled projects are imported from Mantis.

Extension point for adding custom importers.

Pivotal Tracker importer can use a proxy correctly.

CSV importer uses Mindprod CSV parser once again. That fixes handling complex CSV files with backslashes and quotations.

This release contains a single bug fix - Importer should no longer abort the process when trying to log data containing special characters.

New features in 3.5.1 release:

• Pivotal Tracker import wizard includes an optional username mapping stage.
• Configuration file can now be used to provide defaults for Pivotal Tracker import.

Features in our 3.5 release:

• Components are now imported with the lead for Mantis, Bugzilla and FogBugz. 
• When an import is run against existing project components the match will not be case sensitive.

Enjoy!

• Projects imported from Pivotal Tracker are now set up for use with the GreenHopper Rapid Board.
• Workflow updates to for projects imported from Pivotal Tracker.
• Importer supports Bugzilla 4.0 now.

Regressions fixed - votes in Jira 4.4 were imported but not visible on the issue screen; issues imported from CSV have no forced id.

You don't need JDBC details to setup a database. And a bunch of other small UX tweaks.

This is the biggest JIM release ever!

This release focuses mostly on User Experience improvements.

• Simplified Importer setup page (Database) - similar to the Jira 4.4 DB setup, now you don't need to hack JDBC connection strings and driver names. Just pick your DB, provide your hostname details and JIM will do it for you.
• Complete UI rework of the CSV and Pivotal importers. The new UI is more intuitive, robust and better guides users through the import process.
• All importers get a smarter UI showing the import progress. It displays the import stage and progress and also reports any problems.
• You can now import more users than your current Jira license limit allows for. At the end of the import JIM will activate only the first X users - sorted alphabetically - where X is the number of remaining active users allowed by the license.
• Tons of other bug-fixes, small improvements and corner cases are now handled correctly.

Had a bug which caused categories not to be imported from Mantis. Fixed it so issues imported from Mantis will have Components set based on category field.

This version is bundled with Jira 4.4

JIM 3.1 (an internal release) and 3.1.1 (public release) bring the following changes:

• UI has changed a little bit (to conform more to evolving Jira look & feel).
• support for direct import from FogBugz On Demand (hosted)
• administrative keyboard shortcuts to JIM (famous "gg"). Just type G, G and then "bugzilla" (or "fogbugz", or "csv", etc.) to go directly to JIM initial screen
• JIM log now includes information about who initiated the import process and who aborted it.
• A lot of internal changes.

Fixed  https://studio.atlassian.com/browse/JIM-534 which made CSV importer fail in case someone wanted to map only some values for a field.

Better handling for invalid MIME messages in FogBugz

Respect selected Workflow Scheme for projects imported from Trac

Fix all watchers still not being imported from Trac

Trac imports now all watchers (sometimes only the recently set were imported).

Importing attachments from FogBugz handles old database structure.

Priority mappings in FogBugz works now.

Mantis DISK attachments are now supported.

• UX upgrade to the main import screen
• CSV comments can include a creation date and author
• CSV date format is configured via the UI during import
• Handling of proxy settings set in the JVM
• Better reporting of SQL errors
• Auto detection of Pivotal Time tracking
• Matching external users by email to existing accounts

Enjoy!

Highights of 2.6.1:

• Trac 0.12.2 support: zip up your Trac project and then you can import it straight into Jira.
• Pivotal improvements: Story created dates now imported and past iterations are set as released.
• CSV improvements: Status mapping enforced when selected and now CSV columns can have same name and the import will be aggregated. 
• Refactored the configuration file to make it more robust(unfortunately old config files will not work).
• Plenty of other minor improvements and bug fixes too.

Enjoy!

2.5.0 version was released with a major bug that didn't let to import files that had multi-line fields. 2.5.1 fixes the problem.

Version 2.5 of Jira Importers Plugin brings the following goodies:

1. Add subtasks via CSV (JRA-6323 - 6 years old and 66 votes!)
2. Pivotal Tracker is released and out of beta with the following new features:
    * Ranking
    * Full iteration names
    * User Roles
    * Time Tracking
    * Workflow improvements
3. Improvements to our Trac importer (beta):
    * Milestones custom field
    * Custom fields
    * Wiki-markup
4. And lots of other small improvement and fixes.

Fixing regression in Bugzilla importer. 

Pivotal Tracker:

1. The importer will now create a Jira compatible workflow scheme for imported projects
2. Pivotal iterations are imported as Jira versions
3. Pivotal labels are imported
4. Pivotal Chores are imported into a new Jira issue type of Chore
5. Pivotal Tasks are imported into Jira with parent reporter and assignee
6. Resolved Pivotal issues are imported with the Jira default resolution
7. Imported Pivotal issues have a Jira custom field for story id and story url(links back to Pivotal Tracker)

Also minor fixes with the CSV and FogBugz importers.

Fixed a bug that caused comments and attachments to be sometimes imported in wrong order.

Trac 0.12.2 is officially supported - you can import issues, attachments, labels and all the usual goodies. Each Trac database backend is supported: SQLite, MySQL or PostgreSQL.

Things not yet supported in the Trac import are: wiki markup, custom workflows and custom fields. If you need to import them, contact us as we'd love to know how you use Trac.

Also in this release are minor improvements to Pivotal Tracker and CSV:

• Import Pivotal Tracker Tasks as Jira Sub-tasks.
• Import mulitple Versions from CSV into Jira Versions or Jira custom fields.

Enjoy!

This version of JIM brings the following improvements:

• Preliminary support for Pivotal Tracker
• CSV importer can create attachments when pointed to a URL
• Improved UI when dealing with projects which already exist
• Better behaviour for large scale imports (thousands of issues) 
• Many fixes for Mantis, Bugzilla and CSV importers

JIM 2.1.0 comes with the following goodies:

• You can now import both Severity and Priority information from Bugzilla and Mantis deciding which field is mapped to built-in Jira priority and which to custom field(s).
• Import log is now downloadable as a file and is no longer truncated
• Whiteboard field can be now imported from Bugzilla
• Project keys are now validated against Jira settings
• Import functionality can now be used by regular Jira administrators (not just by Jira system administrators)
• a dozen or so fixes

Jira Importers plugin now works with Jira 4.3. It also brings the following improvements:

• streamlined import configuration process and more intuitive UX
• import pages are now protected by web sudo
• CSV importer now supports various encodings
• and a lot of other fixes and improvements

Fixed following problems:

• Fixed regression in CSV importer: only the first component and the version were imported
• Importing Mantis custom fields which have empty string as a value caused NullPointerException
• Added support for Bugzilla's Status Whiteboard
• Fixed NullPointerException for accounts that were used only for watching issues in Mantis
• Bugzilla SQL queries incompatible with PostgreSQL
• Importing Mantis attachments failed with GenericEntityException

There was a problem with importing attachments due to date handling.

Mantis will correctly import dates for comments and attachments.

Issues from Mantis 1.2.x had wrong dates set after import which is now fixed.

Also fixed problem with importing long "Steps to reproduce" and "Additional Information" fields.

If you had problems importing from Bugzilla because of SQL Exception caused by invalid use of getFloat it's the change for you.

This version of the Jira Importers Plugin supports FogBugz 7.3.6 to 8.2.27. Earlier 7.x versions have not been tested but should work, however the plugin does not support FogBugz 6.x or earlier.

Version 1.7 also provides further improvements including:

    * Importing tags.
    * Improved mapping between Priorities, Issue Types and Resolutions.
    * Importing parent/sub-case relationships as Jira Issue Links.
    * Improved error handling (errors are now shown in the importer log which displayed in the web interface).

And a few other minor fixes.
Enjoy!

This version of Jira Importers plugin brings the following improvements around CSV import:

- CSV and the import configuration files are now uploaded from the web browser. You no longer need shell access to the Jira server to import from CSV.

- Streamlined CSV import process (more intutive now).

- Improved handling of definition mapping(e.g. selective import).

- Several bug-fixes.

The new year comes with new exciting news - we've added new two more systems to the importer!

You can now import issues from Mantis, versions 1.1.8 to 1.2.4.

With hassle free configuration, support for value mappings and custom fields this latest version allows you to import your Mantis issues in matter of minutes.

Also if you use other issue trackers you can use the improved CSV importer to migrate your data into Jira.

Because your Bugzilla has more than just bugs.

With this version you'll be able to import and map Bugzilla custom fields to Jira!

This release includes some small fixes:

• mapping user names ignores case
• old External System Import points to the new Bugzilla importer
• issue linking does not report errors when you import only a subset of Bugzilla bugs

• Smart handling of disabled/unused Bugzilla users to control your Jira license user limit.
• Colourful import log - import errors are now rendered in red.
• Duplicates and blockers are imported as appropriate links between Jira issues.
• Importing large attachments from Bugzilla instances that require user credentials to access them.

This is also the first release where we we ask if we can track plugin usage via Google Analytics.You will be asked to opt-in or opt-out when you first use the importer and can change your choice at any time. We track which system is chosen to import and also which pages are visited. We do not track any data that is stored in Jira or used while configuring and performing the import. The purpose of this is to constantly improve the importer with your help.

Full release notes

No more hacking! No code changes! You now can import your customized Bugzilla easier!

Bugzilla importer provides now an easy way to map:

• priorities
• statuses
• resolutions
• user names
• links

Better support for Bugzilla

Improved Bugzilla importer. Now you can import your data from Bugzilla 2.20 up to 3.6.3.

We have added these great new features:

• Importing Work History.
• Importing Big File attachments.
• Importing disabled user accounts (do not count towards Jira user limit).
• Improved import monitoring.
• Improved error handling.

And other fixes!