/
gd.initFromParent
gd.initFromParent
When gd.initFromParent is true, and a sub-task of the issue is created, all rows which are linked to the parent issue, will be duplicated to the created sub-task
Class | grid |
---|---|
Property | gd.initFromParent |
Formal specification | gd.initFromParent = false | true |
Required | no |
Default | false |
Version | 1.23 |
Comment | The grid data is copied from the parent issue to a sub-task if a sub-task issue type also has the grid configured. First the data is copied to a temporary database allowing user to edit it before submission of the sub-task creation. All the changes made on the "Create sub-task" screen are saved then to a persistent database. |
Example | gd.initFromParent=true
|
Reference |
Related content
gd.initFromClone
gd.initFromClone
More like this
Behind the scenes of gd.initFromClone
Behind the scenes of gd.initFromClone
More like this
gd.query.reloadTrigger
gd.query.reloadTrigger
More like this
Bob Swift's "Create on Transition" integration
Bob Swift's "Create on Transition" integration
More like this
Grid reload
Grid reload
More like this
How to ensure that the grid has been modified when creating an issue
How to ensure that the grid has been modified when creating an issue
More like this