Customizing story point

Hi,

Please give me a suggestion on this.

I modified story point by following steps.

Going to
Process Configuration -> Project Configuration -> Configuration Data -> Work Items -> Enumerations

By default, the "Complexity" is 0 pts, 1pt, 2pts, 3pts, ..... , 100pts.
I removed those values and added Unassigned, Extra Small (1), Small (3), Medium (5), ...... , Gigantic (200).

Then, created some stories and set the story point(Medium (5) or Gigantic (200) or etc) on them.

Then I ran "Run all data warehouse collection jobs for all applications" and "Run all data warehouse collection jobs".
Then I checked the widget on dashborad e.g. "Story Points Remaining".
But, it seems that those added story points "Extra Small (1), Small (3), Medium (5), ...... , Gigantic (200)" are not reflected on the widget.


My expectation is that those values Extra Small (1), Small (3), Medium (5), ...... , Gigantic (200) should be used as the parameter of the widget.


Is there anything else needs to be done?

Hi,

Please give me a suggestion on this.

I modified story point by following steps.

Going to
Process Configuration -> Project Configuration -> Configuration Data -> Work Items -> Enumerations

By default, the "Complexity" is 0 pts, 1pt, 2pts, 3pts, ..... , 100pts.
I removed those values and added Unassigned, Extra Small (1), Small (3), Medium (5), ...... , Gigantic (200).

Then, created some stories and set the story point(Medium (5) or Gigantic (200) or etc) on them.

Then I ran "Run all data warehouse collection jobs for all applications" and "Run all data warehouse collection jobs".
Then I checked the widget on dashborad e.g. "Story Points Remaining".
But, it seems that those added story points "Extra Small (1), Small (3), Medium (5), ...... , Gigantic (200)" are not reflected on the widget.


My expectation is that those values Extra Small (1), Small (3), Medium (5), ...... , Gigantic (200) should be used as the parameter of the widget.


Is there anything else needs to be done?

When running against a data warehouse the reports look at the "Numeric Value" field in the string extensions table. This is parsed from the ID of the enumeration values in the XML configuration.

In order to show custom story point values you will need to edit the ID's in the XML to change them from the default auto-generated ID (something like "complexity.literal.l1") to the number representing the story points.

If you have any existing data there is a slight complication in doing this, in that if you change the id of the enumeration value any existing work items that reference that value will just show the old id rather than the new value.

The best approach I have found is to create new enumeration values for the story points you want, then go in and change the ID's of these new values in the XML. After you've done this do a bulk edit of all stories to point to the new values you've created and then delete the old values.

Hi,

Please give me a suggestion on this.

I modified story point by following steps.

Going to
Process Configuration -> Project Configuration -> Configuration Data -> Work Items -> Enumerations

By default, the "Complexity" is 0 pts, 1pt, 2pts, 3pts, ..... , 100pts.
I removed those values and added Unassigned, Extra Small (1), Small (3), Medium (5), ...... , Gigantic (200).

Then, created some stories and set the story point(Medium (5) or Gigantic (200) or etc) on them.

Then I ran "Run all data warehouse collection jobs for all applications" and "Run all data warehouse collection jobs".
Then I checked the widget on dashborad e.g. "Story Points Remaining".
But, it seems that those added story points "Extra Small (1), Small (3), Medium (5), ...... , Gigantic (200)" are not reflected on the widget.


My expectation is that those values Extra Small (1), Small (3), Medium (5), ...... , Gigantic (200) should be used as the parameter of the widget.


Is there anything else needs to be done?