-
Story
-
Resolution: Fixed
-
Minor
-
None
-
None
-
Security Level: Public
-
None
For each change of a list identified fields, the values are propagated to same field of each linked issue.
- Linked Issue are identified by the Outward Link (Sub Task Link included)
- Field are selected among customfield
- Recursive change may be selected
- is caused by
-
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
- Resolved
-
MYAA-311 All AInheritFromParentFunction go in NPE when applied on Non SubTask Issue
- Resolved
-
MYAA-334 Translation error in the fastworklog portlet when entering an invalid issue key
- Resolved
-
MYAA-340 In the worker custom field, clicking on the user name redirects to the issue navigator but no issue is shown
- Resolved
-
MYAA-341 In fast worklog portlet based on worklogs, issue is not added when pressing enter key.
- Resolved
-
MYAA-343 In the fastworklog portlet based on worklogs, after a refresh, issues are not sorted according to the portlet configuration
- Resolved
-
MYAA-346 In the worklogtype edition screen, when choosing a color, the page is not refreshed to show the selected color.
- Resolved
-
MYAA-358 Field Author in Log Work Page display an JS Array Value instead of a Value
- Resolved
-
MYAA-202 The Date reached condition should not accept a value of Null or Zero
- Closed
-
MYAA-364 In the edit screen, if a UserGroupPickerCFType is configured with no groups, a NullPointerException is thrown when trying to update an issue.
- Closed
-
MYAA-420 In the Reached date condition, saving without a custom field throws an java.lang.IllegalArgumentException
- Closed
-
MYAA-439 Workers field is not populated when the Worklogs are filed using Worklogger Field available in the Transition Screens
- Closed
- is related to
-
MYAA-192 Active and Inactive conditions do not respect their configuration for values lower than 1d
- Resolved
-
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
- Resolved
-
MYAA-311 All AInheritFromParentFunction go in NPE when applied on Non SubTask Issue
- Resolved
-
MYAA-318 Portlets having dynamic content are not rezised when content changes
- Resolved
-
MYAA-334 Translation error in the fastworklog portlet when entering an invalid issue key
- Resolved
-
MYAA-335 Users without Edit Permission have access to the Time Spent tab panel
- Resolved
-
MYAA-337 In fastworkflog portlet based on filter, clicking the filter name link redirects to an unexisting page.
- Resolved
-
MYAA-340 In the worker custom field, clicking on the user name redirects to the issue navigator but no issue is shown
- Resolved
-
MYAA-341 In fast worklog portlet based on worklogs, issue is not added when pressing enter key.
- Resolved
-
MYAA-343 In the fastworklog portlet based on worklogs, after a refresh, issues are not sorted according to the portlet configuration
- Resolved
-
MYAA-346 In the worklogtype edition screen, when choosing a color, the page is not refreshed to show the selected color.
- Resolved
-
MYAA-358 Field Author in Log Work Page display an JS Array Value instead of a Value
- Resolved
-
MYAA-202 The Date reached condition should not accept a value of Null or Zero
- Closed
-
MYAA-364 In the edit screen, if a UserGroupPickerCFType is configured with no groups, a NullPointerException is thrown when trying to update an issue.
- Closed
-
MYAA-413 Page ViewWorklogTypes is reacheable by non admin. users by remove /secure/ path
- Closed
-
MYAA-420 In the Reached date condition, saving without a custom field throws an java.lang.IllegalArgumentException
- Closed
-
MYAA-434 Some replacements fails with JIRA 3.12 (JVM 1.4)
- Closed
-
MYAA-439 Workers field is not populated when the Worklogs are filed using Worklogger Field available in the Transition Screens
- Closed