Use existing field in Story table to Defect table

Ramel · ‎03-22-2017

Hi All,

I am trying to use an existing field [Business Analyst] in the 'Story' [rm_story] table to the Defect [rm_defect] table. But within the 'rm_defect' table form layout 'business analyst' field is not available in the form layout. I have check the 'rm_story' table and it extends table is 'rm_feature'. When I check 'rm_feature.list' in the filter navigator it shows the list of Defects, Epics, Stories which I think means that I can use the fields in the 'rm_story' table to the 'rm_defect' table. However, in the form layout, 'Business Analyst' field is nowhere to be found. I have tried different fields, expanding it and by dotwalking I still cannot see 'business analyst' field. I also tried setting extensible from FALSE to TRUE but it does not make any difference.

Is it possible to extend the existing 'business analyst' field in the 'rm_story' table to the 'rm_defect' table? Any thoughts will be much appreciated.

Thanks in advance

Ramel

Robbie · ‎03-22-2017

Hi Ramel,

Can you check the dictionary attribute(s) of the 'Business Analyst' field please? Simply right click on the field.

If as suspected (as shown below) the field is created by you/someone within your company (signified by starting with a 'u_'[field_name], it is only available on the Story table.

As the Story table is at the same level as the Defect table, you cannot 'see it' or leverage the field.

If the field had been implemented on the Feature table, as you've described and understood, it would be available.

(It could also be available if there is also a link between Defect and Story other than via the Feature table - ie if Stories are shown, or referenced from the Defect table and then it would be available via 'dot-walking' however this is not implemented or considered out of the box due to the current model)

You'll either have to create your own 'Business Analyst' field on the Defect table, implement it at the parent Feature table level (and then deal with the existing Business Analyst field on the Story table and copy this data to the new field), or set up a link to the Story table (however this also requires some consideration such as 1:1, 1:M etc.)

Please mark this response as correct and helpful via your post link (Use existing field in Story table to Defect table ) to help others with the same question.

Thanks,

Robbie

View solution in original post

Robbie · ‎03-22-2017

Hi Remel,

Interesting - before I wrote my response I checked the Story table including the dictionary and language file to ensure it didn't already exist. I used one of my Dev instances which admittedly is running Helsinki. (I should have checked via an Istanbul instance. What verion are you running?)

I wonder if this is a new field found on Geneva and Istanbul etc. Let me check and confirm. If its been implemented on the Story level and not on the Feature level, the same principle applies (as per my original response).

Thanks,

Robbie

Robbie · ‎03-22-2017

Hi Remel,

Can you navigate to the field from the Dictionary perspective so we can see when it was created, who was created by, and importantly exactly what table it was created on. This will help shed light on what we need ; )

Thanks,

Robbie