Rational Insight: Story points column is empty in RIODS.request table
3 answers
Timur - good question. My users find it confusing because Story Points is in the data model but not populated by the ETL, so I'm also curious if this will be provided by a future release.
From what I can tell, Story Points is actually treated as a custom attribute so it would need some special consideration in the ETL.
From what I can tell, Story Points is actually treated as a custom attribute so it would need some special consideration in the ETL.
Solved:
I've found that info I looked for is stored in RICALM."REQUEST_STRING_EXT" table.
You could use this query to select user stories and story points
SELECT request_id,num_val FROM RICALM."REQUEST_STRING_EXT"
where name = 'com.ibm.team.apt.attribute.complexity'
I just wonder why this information is not synchronized to RIODS.REQUEST table. This table has STORY_POINTS column that is emty.
The story points field is stored in two locations in the data warehouse: in the Request String Extentions table, and in the Story Points column of the Request table itself.
For the latter to be populated you need to be running 3.0.1.2+, because prior to this the ETLs did not extract the story points as part of the request fact build (see this work item).