It's all about the answers!

Ask a question

What are the implications for adding two new values and changing one value in the Complexity enumeration?


Kim Williams (5620) | asked Nov 07 '16, 8:12 a.m.

Currently our Complexity enumeration has the values of 0,1,2,3,5,8,13, and 21 (I think this is what came with the out-of-the-box Agile process template).  We are considering changing the 21 to be 20 and adding two more values of 40 and 100. 

1.  Are there any implications in the data warehouse, or for live data on changing 21 to 20?

2. Do you foresee any issues with adding 40 and 100 to the enumeration?

Accepted answer


permanent link
Ralph Schoon (60.9k33643) | answered Nov 07 '16, 8:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
1. As far as I am aware, the algorithms treat the values as numbers and uses them to calculate burn down etc.
Dependent on how the change from 21 to 20 is done your burn up/ burn down etc will be impacted for life data. I don't know about the data warehouse, but would assume that, unless the data has to be recalculated the old data would stay.
2. No
Kim Williams selected this answer as the correct answer

Comments
Kim Williams commented Nov 07 '16, 8:35 a.m.

Thanks, Ralph.  Your answer makes sense to me.

Your answer


Register or to post your answer.