Details
-
Type:
Story
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.5
-
Component/s: None
-
Security Level: Public
-
Labels:None
-
Rank:Issue can not be ranked.
-
Workers:
Description
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
Issue Links
| This issue is caused by: | ||||
| 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-311 | All AInheritFromParentFunction go in NPE when applied on Non SubTask Issue |
|
|
|
| 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-341 | In fast worklog portlet based on worklogs, issue is not added when pressing enter key. |
|
|
|
| MYAA-358 | Field Author in Log Work Page display an JS Array Value instead of a Value |
|
|
|
| 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-420 | In the Reached date condition, saving without a custom field throws an java.lang.IllegalArgumentException |
|
|
|
| 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-202 | The Date reached condition should not accept a value of Null or Zero |
|
|
|
| This issue is related to: | ||||
| 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-340 | In the worker custom field, clicking on the user name redirects to the issue navigator but no issue is shown |
|
|
|
| MYAA-346 | In the worklogtype edition screen, when choosing a color, the page is not refreshed to show the selected color. |
|
|
|
| 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-192 | Active and Inactive conditions do not respect their configuration for values lower than 1d |
|
|
|
| MYAA-334 | Translation error in the fastworklog portlet when entering an invalid issue key |
|
|
|
| MYAA-337 | In fastworkflog portlet based on filter, clicking the filter name link redirects to an unexisting page. |
|
|
|
| MYAA-318 | Portlets having dynamic content are not rezised when content changes |
|
|
|
| MYAA-358 | Field Author in Log Work Page display an JS Array Value instead of a Value |
|
|
|
| MYAA-413 | Page ViewWorklogTypes is reacheable by non admin. users by remove /secure/ path |
|
|
|
| MYAA-434 | Some replacements fails with JIRA 3.12 (JVM 1.4) |
|
|
|
| MYAA-439 | Workers field is not populated when the Worklogs are filed using Worklogger Field available in the Transition Screens |
|
|
|
| MYAA-420 | In the Reached date condition, saving without a custom field throws an java.lang.IllegalArgumentException |
|
|
|
| MYAA-202 | The Date reached condition should not accept a value of Null or Zero |
|
|
|
| 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