It's all about the answers!

Ask a question

Does Iteration need to be explicitly set as an attribute on a defect as created?

Barb Oxenford (231113) | asked Apr 09 '13, 9:38 a.m.
edited Apr 09 '13, 9:58 a.m. by Ralph Schoon (63.2k33646)
Or is there a way to tell which iteration a defects were created during by the Current Iteration setting at the time it was opened?

One answer

permanent link
Ralph Schoon (63.2k33646) | answered Apr 09 '13, 9:54 a.m.
edited Apr 09 '13, 9:55 a.m.

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 and 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 for one approach. Another is a follow up action. See for setup instructions and for how to handle iterations. And for a server example for a followup action you could use to run after the save.

This is not a trivial task.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.