Details
-
Type:
Story
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: None
-
Security Level: Public
-
Labels:None
-
Story Points:3
-
Workers:
Description
If the Server Id. in the license key is valid for the Old Backup Data, it is not valid for the first installation required to update Ofbiz settings needed to import Old Data
Issue Links
| This issue is caused by: | ||||
| MYAA-299 | ExtendedPermission Condition and Validator does not evaluate any more Non Standard Permission |
|
|
|
| MYAA-116 | License Key can not be stored in Java Preference on Unix System |
|
|
|
| MYAA-79 | in the report configuration screen, the ID combobox should be labaled as a key instead of an id. |
|
|
|
| MYAA-340 | In the worker custom field, clicking on the user name redirects to the issue navigator but no issue is shown |
|
|
|
| MYAA-316 | When edit Global Transition is implemented, raised Event is no more Update but Generic. |
|
|
|
| MYAA-311 | All AInheritFromParentFunction go in NPE when applied on Non SubTask Issue |
|
|
|
| MYAA-341 | In fast worklog portlet based on worklogs, issue is not added when pressing enter key. |
|
|
|
| MYAA-309 | When registering an invalid license, a stacktrace is logged |
|
|
|
| MYAA-310 | Before installation, the Settings page is available. |
|
|
|
| MYAA-409 | Build of Minyaa for JIRA 3.x was not well done with Java 1.4 |
|
|
|
| MYAA-334 | Translation error in the fastworklog portlet when entering an invalid issue key |
|
|
|
| MYAA-432 | ExtendedPermission Validator fails with Exception with JIRA 3.12.3 |
|
|
|
| MYAA-400 | StringIndexOutOfBoundsException when Background Start and End Colors are not initialized in Settings. |
|
|
|
| MYAA-434 | Some replacements fails with JIRA 3.12 (JVM 1.4) |
|
|
|
| MYAA-364 | In the edit screen, if a UserGroupPickerCFType is configured with no groups, a NullPointerException is thrown when trying to update an issue. |
|
|
|
| This issue is related to: | ||||
| MYAA-299 | ExtendedPermission Condition and Validator does not evaluate any more Non Standard Permission |
|
|
|
| MYAA-72 | WorklogType.Required i18n key is not translated in the LogWork page |
|
|
|
| MYAA-79 | in the report configuration screen, the ID combobox should be labaled as a key instead of an id. |
|
|
|
| MYAA-173 | RegExp Validation failed when Old Value was valid and new Value is null and not valid |
|
|
|
| MYAA-335 | Users without Edit Permission have access to the Time Spent tab panel |
|
|
|
| MYAA-340 | In the worker custom field, clicking on the user name redirects to the issue navigator but no issue is shown |
|
|
|
| MYAA-409 | Build of Minyaa for JIRA 3.x was not well done with Java 1.4 |
|
|
|
| MYAA-174 | Add Notifiable Update Jelly Tag failed due to unvalidated Project parameter |
|
|
|
| MYAA-334 | Translation error in the fastworklog portlet when entering an invalid issue key |
|
|
|
| MYAA-341 | In fast worklog portlet based on worklogs, issue is not added when pressing enter key. |
|
|
|
| MYAA-311 | All AInheritFromParentFunction go in NPE when applied on Non SubTask Issue |
|
|
|
| MYAA-310 | Before installation, the Settings page is available. |
|
|
|
| MYAA-413 | Page ViewWorklogTypes is reacheable by non admin. users by remove /secure/ path |
|
|
|
| MYAA-432 | ExtendedPermission Validator fails with Exception with JIRA 3.12.3 |
|
|
|
| MYAA-434 | Some replacements fails with JIRA 3.12 (JVM 1.4) |
|
|
|
| MYAA-364 | In the edit screen, if a UserGroupPickerCFType is configured with no groups, a NullPointerException is thrown when trying to update an issue. |
|
|
|
Activity
- All
- Comments
- Work Log
- Worklogs (extended)
- Time Spent
- History
- Activity
With non-trial Licenses, the JIRA Server Id. have to be validated against Server Id. stored in License Key.
In order to allow the installation of a new instance of JIRA using a XML Backup, the user need to perform a first installation before importing the XML Backup. Like any new installation, the Server Id. is regenerated and then, the will be never valid against the Server Id. provided the License Key issued from the backuped Database.
No control of the Server Id. while there is only 1 active user !