- Implemented issue journal details export feature
- Implemented issue category list by project feature
- Implemented version list by project feature
- Added support to version resource type mappings
- Re-engineered definitions of internal domain entities and their mappings via classes and named tuples
- Moved definitions of internal domain entities and their mappings to 'resources' sub-package
- Refactored issues export feature to 'IssueExporter' class
- Improved and optimized description of resource mappings settings
- Slightly improved configuration settings comments
- Updated Sphinx to 1.7.1
- Several code optimizations
- Added Python 2 Unicode compatibility for string type
- Used project identifier instead of its internal ID to fetch per-project static resource value mappings
- Used lists instead of sets to achieve Json format serializer compatibility
- Used safer method to check for journal notes existence before fetching them
- Update coverage from 4.5 to 4.5.1
Disable possibility to skip dynamic value mapping feature
Remove printing of issues referenced users at the end of export phase.
As both static and dynamic value mappings are enabled for user resources, the final user doesn't need to be warned for something he consciously did in either case.
- Honor value mappings for user resources
- Implemented issue watchers save method
- Implemented issue attachments save method
- Partially implemented issue journals save method. Redmine journal notes are saved to Jira comments.
- Apply conversion to Confluence Wiki notation only if Textile or Markdown text formatting is enabled in settings
- Implemented issue custom fields save method
- Used tuples as dictionary keys for both resource type fields mappings and dynamic resource value mappings
- Added comment to explain what happens when no static user-defined mapping has been found and dynamic resource value mapping feature is disabled
- Removed leftovers of old project name "Redmine XLS Export to Jira"
- Removed CUSTOM_ prefix from the resource value mappings setting names
- Fixed setting of dynamic resource value mapping when the resource type is defined on a per-project basis
- Removed misleading comment. When a Redmine resource type is mapped to more than one Jira resource type the final user is free to set value mappings across all possible resource type combinations.
- Added default empty dictionary if the resource type mapping setting is not found
- Minor docstring fixes
- Add pyenv support for Tox
- Fix packages include directive in
setup.py
Fake release to fix a problem in PyPI upload.
- Implemented issue project save method
- Implemented issue standard fields save methods
Renamed
_get_resource_value_mappingmethod to_get_resource_mapping.The method now returns both mapped Jira type and value, rather than only value.
Updated method docstring accordingly.
Added Redmine general configuration section header
- Removed Python 3.3 compatibility
- Updated encrypted PyPI password for Travis CI
- Replaced references to old
CUSTOM_USERS_MAPPINGSsetting with newCUSTOM_REDMINE_USER_JIRA_USER_MAPPINGS - Retrieved issue user resource instance from cached users list rather than from issue lazy loaded instance
- Disabled dynamic value mapping feature for Redmine "User" resource type
- Added dynamic resource value mapping management at runtime
- Added dynamic resource value mapping for assignee field when it refers to a standard user
- Added command to list issue priorities
- Made Redmine and Jira respective resource types explicit in the names of settings related to resource value mappings
- Slightly improved settings related comments
- Added labels for values printed in console output
- Improved code readability
- Slightly improved docstrings
- Updated
sphinxto 1.6.7 - Updated
coverageto 4.5
- Added dynamic project mappings management
- Refactored specific methods to save issue resources
- Minor optimizations
- Referenced users and groups are collected on-the-fly while exporting issues. This increases performance.
- Minor enhancements in the console output for the completion of the export
- Fix recursive function used in
list projectscommand to build the full project hierarchical name - Fixed a bug affecting all the
listcommands that caused some resource relations being included in the tables - Fixed another minor bug affecting all the
listcommands
- Added early lookup of users and groups references within the issues being exported
- Added command to list Redmine groups
- Added option to list all Redmine users at once, including locked ones
- Enhanced notes in configuration file
- Added requirements.txt for installation package requirements (useful for pyup.io)
- Added PyCharm IDE configuration and Python Virtual Environments to .gitignore
- Added configuration file with defaults and support for local configuration file
- Minor documentation fixes
Dropped out "Redmine XLS Plugin" in favor of Redmine REST API.
Since the files exported by the plugin lack some information needed to produce files compatible with the Jira Importer Plugin (JIM), several calls to the Redmine REST API were needed to compensate the data. Hence to avoid the effort to merge the data coming from two difference sources I decided to rely solely on Redmine REST API to fetch all the needed data.
This is a major project scope change that implied, in turn, the following modifications:
- Renamed GitHub repository from "redmine-xls-export2jira" to "redmine2jira"
- Renamed Python package from "redmine_xls_export2jira" to "redmine2jira"
- Rename project description to "Redmine to JIRA Importers plugin"
Any other reference to the "Redmine XLS Export" plugin has also been removed from the documentation.
Removed Python 2.7 compatibility. Added Python 3.6 compatibility.
Temporarily disable CLI tests
- Minor fixes in docs
- Initial pyup.io update
- Added pyup.io Python 3 badge
- Linked pyup.io
- Removed CHANGELOG.rst
- First release on PyPI.