Hi again, after some months of silence. This did not mean lack of activity, on the contrary, after the release of version 2.0 the support activity has been very intense. In addition, development has produced, apart from a number of bug fixes, interesting improvements. I would like to review some of them here:
- The data import log has been improved from its original content in version 2.0. This helps the user gather more complete information about the data import process, including any warning or error.
- It is possible to see the list of optional or mandatory users that could not be created during the data import phase. These users are shown grouped by projects, with the information that was available about them. With this information, the user can assess better the impact of these missing users and take corrective action if appropriate.
- Locked custom fields are not exported. These are fields created by plugins or applications (for example, JIRA Software or JIRA Service Desk) and their configuration cannot be modified (not even by the JIRA admin…). It does not make any sense to export and import configuration for these custom fields, as this configuration can only be set up by the plugin that owns these custom fields. So, as long as the owner plugin is properly installed in a JIRA instance, those fields are correctly configured and there is not anything we should do about them.
- And, of course, compatibility with JIRA 7.2…
Please, stay tuned to our blog. Important news coming very soon…