Custom complexity attribute not not seen as '{Complexity Attribute}' by BIRT
Hi,
we've created a custom attribute Epic Points with the id com.company.attribute.complexity.epic_points which shall be used within an Epic as a kind of early planning points.
It is defined as a complexity attribute and therefore it deals with points.
Our idea was to use the BIRT report variable '{Complexity Attribute}' within a custom report to fetch those rows of the LIVE_WORKITEM_CNT table which contain points. Unfortunately that doesn't work. Therefore I'd like to know how a custom attribute needs to be designed to fit that requirement.
Cheers
Matthias
we've created a custom attribute Epic Points with the id com.company.attribute.complexity.epic_points which shall be used within an Epic as a kind of early planning points.
It is defined as a complexity attribute and therefore it deals with points.
Our idea was to use the BIRT report variable '{Complexity Attribute}' within a custom report to fetch those rows of the LIVE_WORKITEM_CNT table which contain points. Unfortunately that doesn't work. Therefore I'd like to know how a custom attribute needs to be designed to fit that requirement.
Cheers
Matthias
One answer
Hi Matthias,
Accessing complexity attributes should be possible using the variable you're referring to. However there is some knowledge needed at report design time: the type of the attribute. Complexity attributes could be (for example) strings or ints, and you need to pass "{Complexity Attribute}" into the STRING_KEY or INT_KEY as appropriate and then select whichever of STRING_VAL or INT_VAL you need.
Out of curiosity, if you pass in the attribute id directly (instead of {Complexity Attribute}) does it work?
james
Comments