Use existing field in Story table to Defect table

[Ramel]

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 · Accepted solution]

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

[Ramel]

Thanks Robbie,

It may probably have been customized in our instance. I will figured it out here as this field was created a while back. You are probably right. Will just ask internally.

Regards,

Ramel

[Shaun Hillier]

Hi Ramel

The reason you can't see the field is because it is a rm_stroy field and not a rm_feature field, you can see this my right clicking on the field and selecting "Show - Business Analyst":

Now all is not lost, there is a Glide package to promote a field to a parent table, so you could run this in a fix script to move the field to the rm_feature table:

GlideDBUtil.promoteColumn('rm_story', 'rm_feature', 'business_analyst', true);

Be warned though, this is not captured in an update set so you must add it as a manual step in your deployment process when you move to Test/Prod.

Hope that helps

Shaun

[Ramel]

Hi Robbie,

Thanks for your response.

I have checked on the 'business analyst' field in the rm_story table but it does not look to be created by someone in my team.

It also cannot be deleted in the rm_story columns, which only means it is there by default.

I am actually thinking of creating a new Business Analyst field in the rm_defect table but I just wanted to explore my options on using the existing field if possible rather than creating new one.

Regards,

Ramel