Hi Greg,

one possible solution would be an extension such as a follow up action on saving a work item. There is a Extensions workshop on the library that could get you started.

Not sure if that would be possible but another approach might be trying to create a value provider for due date (or a custom due date attribute) and have a dependency to the iteration to calculate the value.

One question, why would you want to do that, given that the due date is really derived and implied in the plans?

Thanks,

Ralph

Hi,

We're using RTC 2.0.X

We'd like to be able to fill in the due dates for a large number of work items at once, based on the iterations they are planned for.

Since we know the currently assigned iteration, the due date is the date at the end of that iteration.

I have run queries to find all of the items, but it seems that due date is not one of the fields you can set on all items at once.

Is there a way to do what we want to achieve here, that the due date reflects the end date of the iteration?

Thanks,
Greg