Why RTC 3.0 WIs Planned Dates aren't displayed in Queries?
Accepted answer
Hi,
I believe that data is dynamically calculated by the plan and therefore not available in queries.
Thanks,
Ralph
I believe that data is dynamically calculated by the plan and therefore not available in queries.
Thanks,
Ralph
I'd like to know if is possible to retrieve in queries information related to Planned Start Date and Planned End Date calculated by RTC?
I tried do find these dates but I can only retrieve them exporting the plan.
2 other answers
I just created an iteration called 1.0.2 under a timeline. I did not check the "A release is scheduled for this iteration" box when I created the iteration.
I thought that I would see this new iteration value in the Iteration Planned attribute drop down list so I can select it when adding a work item. But this value doesn't appear.
It appears as though I have to check the "A release is scheduled for this iteration" box to make the 1.0.2 iteration display in the Iterantion Planned attribute drop down.
Is that the correct behavior. If so, can anyone explain why this is the behavior.
I thought that I would see this new iteration value in the Iteration Planned attribute drop down list so I can select it when adding a work item. But this value doesn't appear.
It appears as though I have to check the "A release is scheduled for this iteration" box to make the 1.0.2 iteration display in the Iterantion Planned attribute drop down.
Is that the correct behavior. If so, can anyone explain why this is the behavior.
I just created an iteration called 1.0.2 under a timeline. I did not check the "A release is scheduled for this iteration" box when I created the iteration.
I thought that I would see this new iteration value in the Iteration Planned attribute drop down list so I can select it when adding a work item. But this value doesn't appear.
It appears as though I have to check the "A release is scheduled for this iteration" box to make the 1.0.2 iteration display in the Iterantion Planned attribute drop down.
Is that the correct behavior. If so, can anyone explain why this is the behavior.
Yes. Since you didn't plan a release it is not available for planning. This is used for instance to bind behavior to sub iterations.