New linked work item inherits iteration from parent only when autocreate is not ticked on

[chrisn25]

Hi, I've just started using this plugin and it does exactly what I want, so thanks.

I'm using it to try and make a template to add a set of tasks to a product backlog item. My one small quibble is that if I tick the checkbox to set the action to autocreate the tasks, then they don't inherit the product backlog item's current iteration. If I leave this ticked off, I have to save/close in the task dialog for each task that it creates, but it does seem to get the iteration.

I'd like to be able to have it autocreate and inherit the iteration from the parent. Thanks.

[Wickkky]

Hi,
I have the same problem with the Iteration path, and the Area path also. I created the templates and the rules also. I wanted to add tasksto a User Story as new child WI , and when I thick the automatic creation checkbox, the area and iteration path are not inhetrited. They are set to the Default area and iteration value.
It would be great if the automated child creation could inherit the parent work item's area and iteration settings.
Many thanks!

[YggY]

I've got a workaround for you: In the template of the new item, set this field "Area Path" to "@fieldvalue=System.AreaPath" and do the same for Iteration Paths.

[SillyKeith]

I've got a workaround for you: In the template of the new item, set this field "Area Path" to "@fieldvalue=System.AreaPath" and do the same for Iteration Paths.

This also works: @fieldvalue=Iteration Path
It works for lots of field values with the space, like @fieldvalue=Impacted Role etc.
It doesn't work with Identity fields, like "Resolved By"