Does Iteration need to be explicitly set as an attribute on a defect as created?
One answer
Barb,
the planned for attribute is supposed to show the iteration a defect is supposed to be fixed. This is usually a conscious discussion and should not be set automatically.
You can define a default value in RTC using Attribute Customzation see https://jazz.net/wiki/bin/view/Main/AttributeCustomization and https://jazz.net/library/article/1093 Lab 4 for details. However that does not allow to set the current iteration - which is also not trivial, because as long as a work item is not filed against a category , you can't know the timeline hence the current iteration. Also, if someone changes the filed against category, what is supposed to happen?
Anyway, you can also not use JavaScript, you can try using a Java Extension. See https://jazz.net/wiki/bin/view/Main/AttributeCustomization#Providing_new_customizations_imp for one approach. Another is a follow up action. See http://rsjazz.wordpress.com/2013/02/28/setting-up-rational-team-concert-for-api-development/ for setup instructions and http://rsjazz.wordpress.com/2012/10/05/handling-iterations-automation-for-the-planned-for-attribute/ for how to handle iterations. And http://rsjazz.wordpress.com/2012/11/27/resolve-parent-if-all-children-are-resolved-participant/ for a server example for a followup action you could use to run after the save.
This is not a trivial task.
the planned for attribute is supposed to show the iteration a defect is supposed to be fixed. This is usually a conscious discussion and should not be set automatically.
You can define a default value in RTC using Attribute Customzation see https://jazz.net/wiki/bin/view/Main/AttributeCustomization and https://jazz.net/library/article/1093 Lab 4 for details. However that does not allow to set the current iteration - which is also not trivial, because as long as a work item is not filed against a category , you can't know the timeline hence the current iteration. Also, if someone changes the filed against category, what is supposed to happen?
Anyway, you can also not use JavaScript, you can try using a Java Extension. See https://jazz.net/wiki/bin/view/Main/AttributeCustomization#Providing_new_customizations_imp for one approach. Another is a follow up action. See http://rsjazz.wordpress.com/2013/02/28/setting-up-rational-team-concert-for-api-development/ for setup instructions and http://rsjazz.wordpress.com/2012/10/05/handling-iterations-automation-for-the-planned-for-attribute/ for how to handle iterations. And http://rsjazz.wordpress.com/2012/11/27/resolve-parent-if-all-children-are-resolved-participant/ for a server example for a followup action you could use to run after the save.
This is not a trivial task.