+0034 670 943 266 info@awnaba.com

This week we have released version 1.8 of Project Configurator. One of the great advances this week is compatibility with JIRA 7, which had already been requested by some customers.

Actually, version “1.8” does not exist with that name but as two different versions for JIRA 7 (1.8-J7) and JIRA 6 (1.8-J6): there are independent versions of the plugin Project Configurator for JIRA 6 and JIRA 7. Many plugin vendors that have chosen this approach have realized that some users get confused. Depending on the last version published in the Marketplace these users think that the plugin is compatible only with JIRA 7 or only with JIRA 6 and they submit an update request. So, please remember this advice: have a look at the version history of a plugin before sending an update request. If you finally send it, do not forget to add your email address to the request, so that the developers can get back to you. Needless to say, you can help us a lot (and other plugin vendors) by spreading this word among other fellow JIRA admins :)

The other innovation released this week is an improved handling of JIRA caches during import. This change started as a response to the performance degradation (quite severe in some cases) perceived by some users with large instances at the end of imports. After a lengthy research of the problem and some very useful conversations with Atlassians, it was decided that the way to handle JIRA caches had to undergo a substantial change. It also became clear that the feature for rolling back the database to its initial state in case of a failed import had to be removed. See history and all details about this change in our JIRA. There is also an important notice there, which all users of previous plugin versions should read.

The new version with this fix solves that original problem and is also faster than previous versions. We expect also that this fix will prevent the caching problems found sometimes during the import, when an object that had been created earlier in the import could not be found when it was required for a later operation.