EPIC Reference Field On Story Form Is Showing No Records

[Gaurav Bhatia]

Hi Everyone,

There is a Reference field (EPIC) on story form and this field is referencing to 'rm_epic' table. Earlier when I click on this field then I am able to see records. However, I feel that after London Upgrade when I click on this reference field then I am not able to see any records.

I have all the required roles. When I open list view of EPIC [rm_epic] table then I can see all the records. However, when this table [rm_epic] is referenced in a EPIC reference field on story form then we are not able to see the records in the reference field Pop-up.

Those stories in which this field value is already there, we can see that value on list view as well as form view. However, as soon as I click on the reference field icon then pop-up shows no records.

Please see the below images to understand the issue and let me know if this is related to London or there is some other fix for this.

Regards,

Gaurav

[Madhu80 · Accepted solution]

Hi Gaurav,

This is a known defect PRB1308640 and will be addressed in an upcoming London patch. In the meantime, you could apply the fix by replacing the above mentioned reference qualifier with javascript:ScrumSecurityManager.getStoryDotEpic(current)

[Gaurav Bhatia]

Thank You Umapathy. The workaround has worked and now I am able to see the EPIC records.

I have few questions. Please see below-

1. Who has raised this problem ticket PRB1308640. Can I see this ticket on HI portal?

2. When London patch is applied to our instance then shall I face the same issue again?

3. Do we have any document which supports this like anything on Product document site?

Regards,

Gaurav

[Gaurav Bhatia]

Please ignore my 1 and 3rd question as one of my team mate is able to see the problem record and I found 1 knowledge article KB0716305 supporting this as well.

Please respond to below if you know something about this-

**When new London patch is applied to our instance then shall I face the same issue again?**

Regards,

Gaurav

[Madhu80]

Gaurav, No, applying the London patch that has the fix shouldn't bring the issue back. To keep the code in sync with the out of the box one, you could do one the following -

1. Apply the fix provided in the earlier reply
2. Navigate to Customer Updates and look for name=sys_dictionary_rm_story_epic
3. Bring the column "Replace on Upgrade" into view (if not already available) and set it to true

Note that if you do the steps above and upgrade to a London patch that does not have the fix for the defect, you will have to do the steps again.

or 

1. Apply the fix provided in the earlier reply
2. Let your instance go through the London patch that has the fix (or a later patch)
3. Navigate to the sys_dictionary record where you made the change
4. In the Versions related list, identify the record that points to the London patch
5. Right click and select "Revert to this version". Verify that the reference qualifier has the correct script