Details
Story
Issue Links
| This issue is caused by: | ||||
| MYAA-25 | First field doesnt have the focus in the log work page |
|
|
|
| MYAA-409 | Build of Minyaa for JIRA 3.x was not well done with Java 1.4 |
|
|
|
| MYAA-343 | In the fastworklog portlet based on worklogs, after a refresh, issues are not sorted according to the portlet configuration |
|
|
|
| MYAA-310 | Before installation, the Settings page is available. |
|
|
|
| MYAA-432 | ExtendedPermission Validator fails with Exception with JIRA 3.12.3 |
|
|
|
| MYAA-434 | Some replacements fails with JIRA 3.12 (JVM 1.4) |
|
|
|
| This issue is related to: | ||||
| MYAA-318 | Portlets having dynamic content are not rezised when content changes |
|
|
|
| MYAA-274 | JIRA Build Number is miscontrolled for Item Updater |
|
|
|
| MYAA-343 | In the fastworklog portlet based on worklogs, after a refresh, issues are not sorted according to the portlet configuration |
|
|
|
| MYAA-335 | Users without Edit Permission have access to the Time Spent tab panel |
|
|
|
| MYAA-278 | Uninstalling minyaa doesnt restore entityengine.xml.myaa and entitygroup.xml.myaa |
|
|
|
| MYAA-409 | Build of Minyaa for JIRA 3.x was not well done with Java 1.4 |
|
|
|
| MYAA-172 | ReportElement for Priority is misformed (due to copy/paste from IssueType) and there is no associated Translator |
|
|
|
| MYAA-174 | Add Notifiable Update Jelly Tag failed due to unvalidated Project parameter |
|
|
|
| MYAA-310 | Before installation, the Settings page is available. |
|
|
|
| MYAA-432 | ExtendedPermission Validator fails with Exception with JIRA 3.12.3 |
|
|
|
| MYAA-434 | Some replacements fails with JIRA 3.12 (JVM 1.4) |
|
|
|
Activity
- All
- Comments
- Work Log
- Worklogs (extended)
- Time Spent
- History
- Activity