Details
Story
Description
Since Issue View Screen does take in account only CustomField, the control is done using Edit Screen, even for View Screen !
Issue Links
| This issue is caused by: | ||||
| MYAA-299 | ExtendedPermission Condition and Validator does not evaluate any more Non Standard Permission |
|
|
|
| MYAA-3 | Edition and Visualisation of Worklog Function based on CustomPermissions are not available |
|
|
|
| MYAA-339 | Parameter "Delay in Days allowing Worklog Update" is not controlled in default LogWork page |
|
|
|
| MYAA-409 | Build of Minyaa for JIRA 3.x was not well done with Java 1.4 |
|
|
|
| MYAA-346 | In the worklogtype edition screen, when choosing a color, the page is not refreshed to show the selected color. |
|
|
|
| MYAA-316 | When edit Global Transition is implemented, raised Event is no more Update but Generic. |
|
|
|
| MYAA-340 | In the worker custom field, clicking on the user name redirects to the issue navigator but no issue is shown |
|
|
|
| MYAA-343 | In the fastworklog portlet based on worklogs, after a refresh, issues are not sorted according to the portlet configuration |
|
|
|
| MYAA-334 | Translation error in the fastworklog portlet when entering an invalid issue key |
|
|
|
| MYAA-311 | All AInheritFromParentFunction go in NPE when applied on Non SubTask Issue |
|
|
|
| MYAA-296 | Edit Screen for default com.atlassian.jira.workflow.condition.PermissionCondition allows to select Auto Transition permission but View Screen fails in display. Edit no more available |
|
|
|
| MYAA-439 | Workers field is not populated when the Worklogs are filed using Worklogger Field available in the Transition Screens |
|
|
|
| MYAA-364 | In the edit screen, if a UserGroupPickerCFType is configured with no groups, a NullPointerException is thrown when trying to update an issue. |
|
|
|
| MYAA-432 | ExtendedPermission Validator fails with Exception with JIRA 3.12.3 |
|
|
|
| MYAA-433 | When a Global Action is created, it does not reference Workflow descriptor until the next Startup |
|
|
|
| This issue is related to: | ||||
| MYAA-299 | ExtendedPermission Condition and Validator does not evaluate any more Non Standard Permission |
|
|
|
| MYAA-3 | Edition and Visualisation of Worklog Function based on CustomPermissions are not available |
|
|
|
| MYAA-79 | in the report configuration screen, the ID combobox should be labaled as a key instead of an id. |
|
|
|
| MYAA-343 | In the fastworklog portlet based on worklogs, after a refresh, issues are not sorted according to the portlet configuration |
|
|
|
| MYAA-296 | Edit Screen for default com.atlassian.jira.workflow.condition.PermissionCondition allows to select Auto Transition permission but View Screen fails in display. Edit no more available |
|
|
|
| MYAA-335 | Users without Edit Permission have access to the Time Spent tab panel |
|
|
|
| MYAA-346 | In the worklogtype edition screen, when choosing a color, the page is not refreshed to show the selected color. |
|
|
|
| MYAA-340 | In the worker custom field, clicking on the user name redirects to the issue navigator but no issue is shown |
|
|
|
| MYAA-339 | Parameter "Delay in Days allowing Worklog Update" is not controlled in default LogWork page |
|
|
|
| MYAA-409 | Build of Minyaa for JIRA 3.x was not well done with Java 1.4 |
|
|
|
| MYAA-311 | All AInheritFromParentFunction go in NPE when applied on Non SubTask Issue |
|
|
|
| MYAA-316 | When edit Global Transition is implemented, raised Event is no more Update but Generic. |
|
|
|
| MYAA-341 | In fast worklog portlet based on worklogs, issue is not added when pressing enter key. |
|
|
|
| MYAA-334 | Translation error in the fastworklog portlet when entering an invalid issue key |
|
|
|
| MYAA-439 | Workers field is not populated when the Worklogs are filed using Worklogger Field available in the Transition Screens |
|
|
|
| MYAA-432 | ExtendedPermission Validator fails with Exception with JIRA 3.12.3 |
|
|
|
| MYAA-433 | When a Global Action is created, it does not reference Workflow descriptor until the next Startup |
|
|
|
| MYAA-434 | Some replacements fails with JIRA 3.12 (JVM 1.4) |
|
|
|
Activity
- All
- Comments
- Work Log
- Worklogs (extended)
- Time Spent
- History
- Activity