I am not sure what you gain from that and I am pretty sure it will not be as easy as soon as you have more than one iteration cycle.

Anyway. Attribute customization is across all work items that have the attribute. For attribute customization the only chance would be trying to use a JavaScript based default value as JavaScript allows you to potentially see and react to the work item type. That could look at the type and return the iteration UUID. A calculated value always calculates, so that is not very useful. In JavaScript you have no chance to look up iterations, see the limitations Attribute customization or in Process Enactment Workshop for the Rational solution for Collaborative Lifecycle Management so you are pretty limited in what you can do.

You can use Java for Attribute customization and the API provides you with a little more choices. The limitations are then this API and how attribute customization providers work. See an example here: Attribute Customization – Java Based Value Providers, Conditions and Validators  

My choice would be a work item save (server) follow up action / participant if I wanted to do anything like that, because that gives you the complete API and the most control about what happens. Here an example as entry point A Create Approval Work Item Save Participant. The blog also has examples how to access timelines and iterations.

Ian,

Rather than looking into a way to do this within a Work Item;

Why not set up a plan view and then you will be able to create the Work items agains the correct Planned for.

Just a thought.

Regards

Matt

 Hi Ian,