-1

I've introduced a new workflow that I'm using for my project, and everything looks so good so far. There was one unintended effect,though.

When I applied everything and the new statuses were applied to current issues, the burndown chart showed everything as if they had been removed from "Resolved". It trended back upward, as if the things that were done become not done.

Now, if I act on the issues and use one of the transitions, it burns down properly (the statuses have been mapped to the "Complete" state in the transitions). This makes me wonder: does the association that happens in a new workflow disregard the burndown chart? Which properties should I address to ensure that everything previously marked as Complete remains so and is reflected in the burndown chart?

4

1 回答 1

0

据我所知:是的,它被忽略了。我尝试将工作流应用到另一个项目并得到相同的结果。所有以前解决的问题都被标记为未解决,即使转换甚至更改了解决方案字段以使其完成。

于 2014-05-12T22:50:04.813 回答