Hi,

as far as I can tell, you would have to write an extension (a participant) to do this. The other option would be a Java Client that runs every now and then and automates.

I would probably not tie the automatic state change to just one attribute, in fact, I would probably propose a completely other solution. I would make "not yet estimated" the unassigned literal and make the attribute mandatory for the "Ready For Sprint" state.

In addition, the decision to change the state should be a conscious decision that is done by some role during an activity. I am not sure it is a good idea to reflect activities like "Planning Poker" or "Ready for Sprint" as a state of the work item.

The way this is meant to be done in RTC is to plan a work item for an iteration (e.g. the sprint backlog or another iteration used to collect the items considered to go into the next sprint). All the items in this iteration can be presented by a query or a plan and then you can perform your planning poker on them. Once the estimation is done, you can plan the work items for the sprint they are proposed to be executed in.