RTC Attribute customization default value doesn't work in plan
I've defined a Default Values element in Attribute Customization in RTC 3.0.1 that set the category (Filed Against) to a default value. It works fine when I create a work item from the WorkItems menu, the default category is set. However, when I create a work item from a plan in a ranked list, the default category value is not taken into account.
Is it a known issue? Is there a workaround?
Thank you.
Accepted answer
Comments
Thanks, Ralph, I understand the logic. Unfortunately, this prevents us from using an attribute script to default a new child task's category to that of it's parent. This would be a time saver for my customer and would still keep the new work item within the plan view.
Since you can not access another work item or follow a link with attribute customization, that wouldn't work in any case. You can basically not use the save in the plan to save the child item and attribute customization is pretty much out of the window.
You could use a follow up action/participant. See https://rsjazz.wordpress.com/2016/10/24/using-the-work-item-server-api-to-create-work-items/ and the child would basically be created in the background and show or don't show up in a plan (dependent on the values for category and iteration). There might be scenarios to make this work. depends. You can just not make miracles work. In a participant, there could be another save after the initial one and you could potentially overwrite the defaults the plan sets.