It's all about the answers!

Ask a question

Custom story point values not adding up in plan view


John Goodson (2159) | asked Nov 03 '09, 12:41 p.m.
Our team is new to RTC. One of the first changes we made to customize was to assign additional story point enumerations as we have been using different numbers than the traditional Mike Cohn set.

The problem is that when we assign a story to a different value from the original set, the plan document counts it as 0 points. If we choose one of the original values like 8 or 13, then it counts it correctly.

Did I miss a step in configuring something?

Thanks

Accepted answer


permanent link
Kevin Ramer (4.5k6172190) | answered Oct 10 '13, 12:18 p.m.
This happens because the "complexity" enumeration inserts numeric strings into the attribute.  To see what I mean, open your project area configuration and switch to the Process Configuration Source, search for /enumeration to get to the right area, then look for the 'complexity' enumeration.  It may look a bit like this OOTB scrum:

            <configuration-data final="false" id="com.ibm.team.workitem.configuration.enumerations" xmlns="http://com.ibm.team.workitem/enumerations">
                <enumeration attributeTypeId="complexity" name="complexity">
                    <literal default="true" id="0" name="0 pts"/>
                    <literal id="1" name="1 pt"/>
                    <literal id="2" name="2 pts"/>
                    <literal id="3" name="3 pts"/>
                    <literal id="5" name="5 pts"/>
                    <literal id="8" name="8 pts"/>
                    <literal id="13" name="13 pts"/>
                    <literal id="20" name="20 pts"/>
                    <literal id="40" name="40 pts"/>
                    <literal id="100" name="100 pts"/>
                </enumeration>

However, if you have added additional entries, say 71 pts it may look like this:

<literal id="complexity.literal.l4" name="71 pts"/>

This can be corrected but will be a mult-pass process so grab on an pay attention ;-)

  1. For any entries that have id="complexity.literal.lX" change the name= to something eye-catching.  e.g. <literal id="complexity.literal.l4" name="NOT 71pts"/>
  2. Create a new literal whose id is an integer value <literal id="71" name="71 pts"/>.  You can copy/paste additional line in the process source.
  3. Save the project area.
  4. Change work items whose story points show your eye catcher to the new entry.
  5. Delete the miscreant entries from the enumeration
  6. Remember this for the next time you need a new value.  It's ok to use the UI to enter it, but change the id= to the numeric value
Hope this displays right and helps.
John Goodson selected this answer as the correct answer

One other answer



permanent link
John Goodson (2159) | answered Nov 03 '09, 4:20 p.m.
Solved my own problem had to edit process config source

Comments
Gayathri Vikraman commented Oct 10 '13, 12:06 p.m.

Hi John

May I know what change did you make in the process config source? I am also facing a similar issue now.

Thanks
Gayathri


John Goodson commented Oct 10 '13, 1:07 p.m.

Gayathri,


See the answer from Kevin below. That was exactly what I did 

Your answer


Register or to post your answer.