Upgrade Tasks for Minyaa 3.5
For previous release see Upgrade to Minyaa 3.4.x
This release provides different Upgrade Tasks.
Upgrade Tasks applied using REST instead of JELLY
Since JIRA 6.4.x, the JELLY framework is not more supported and it causes that Uprade tasks, requiring to be re-executed, have to be applied
using the new REST API.
Only the Upgrade Task defined since Minyaa 3.4.x can be launched by REST API.
Custom Permission Upgrade Task 006
This Upgrade Task is available since Minyaa for JIRA 6.3.x
Core Upgrade Task 007
This Upgrade Task is available since Minyaa for JIRA 6.3.x
Upgrade Tasks for Minyaa 3.5.1
This release does not provide special Upgrade Task to execute using REST.
Same procedure as Minyaa 3.5.1. You have only to follow below additionals points ...
License Management Libraries changed ...
This version comes with some changes in the License Management ...
- The License Checker sequence has been modified in order to avoid Deadlock with MSSQL environments.
- The License Key Controller has been modified in order to support installation with expired licenses keys, when the Key is valid for a old Minyaa version.
BROWSE SUBTASK & WORKLOG Custom Permissions
Since Minyaa 3.4 (since JIRA 6.3.x), these permissions required to be granted to all concerned users.
Now, it is possible to disable them (not controlled) using some dedicated properties. See
Minyaa Core Settings page.
Upgrade Tasks for Minyaa 3.5.2
This release does not provide special Upgrade Task to execute using REST.
Check for previous Upgrade Procedure, depending on your current version ...