Conversion from Points Open Text to Points Fibonacci

XMLWordPrintable

      Issue Summary

      When converting from Points Open Text to Points Fibonacci, in the forecast page points do not change.

      Steps to Reproduce

      If I have Epic A with 149 points and Epic B with 100 points in Details and Forecast tabs (prior to changing it to Fibonacci) and then switch it to using Fibonacci:

      1. Epic A will show 149 points in the points field in the Backlog and Grid. However, when you open it up on the details tab, the drop down will have nothing in it. Should it convert it? Confusing to have it say 1 value on a page but when you look at it, nothing is selected. No separate field in column view for Fibonacci like there is for T-shirt, etc.

      2. Epic B will show 100 in the Points field in the Backlog and Grid. However, when you open it up on the details tab, the drop down will have 100 selected. 100 points in open text is not the same as 100 Fibonacci in my estimation table. 100 Fibonacci = 2250 points.

      3. From the Epic Backlog, if you select Kanban and column view. Then select Estimate. If Epic B is the only item in that PI, it shows the converted points to be 2200. My table says 2250. When we first did the estimation conversion, we used the customer's numbers and said we would continue to use those until the customer updated and clicked on save to begin using the new calcs. I have never clicked on save so I have the existing numbers. You should still be using what is listed in conversion table.

      4. If I add multiple PI's to Epic A and add Fibonacci for both 100 for PI 1 and 13 for PI2, then it provides a total of 113 points. Should we be showing a total or should this be treated like T-shirt. If we should show the total, should it 113 or should it be the total number of points based on the estimation conversion table?

      5. If Epic A has 100 points for the PI, then if you go to the Forecast tab, it is showing 100 pts. When you put a number at the program level, this carries to the Forecast page. It is now comparing the 100 using Fibonacci to the Program Velocity. This is different than what we show in #3 above. We aren't comparing the same thing. Should we show the converted points on the Forecast tab so they can continue to use Velocity?

      6. If Epic B has 149 points for the PI, then if you go to the Forecast tab, it is still showing 149 pts from when we entered it using Open Text. There is no conversion taking place which means the numbers would be incorrect on the forecast tab as well as on the forecast page.

      Expected Results

      If in fibonacci or power of 2, it should convert to the open text field points

      Actual Results

      If in fibonacci or power of 2, it is not converted to open text field points

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Kyle Byrd (Inactive)
              Reporter:
              Mario Sojo (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: