I am not getting the epic/story linked relationship to work with the story map plugin v2.2.0 using jira 5.2.1 and Greenhopper 6.2.2.2.

[Nancy Belser]

When I create an epic and story through greenhopper proper, the link relationship does work and then is reflected on the story map board. When I do the same thing via the story map plugin, the link relationship is not created; if I refresh the board, the story appears under the unlinked issues box.

I confirmed by checking the database issuelink table that the story map plugin does not seem to create the actual record in the issuelink table, but greenhopper does.

Am I doing something wrong?

[Florian Bauer]

there are two link techiques - the older versions of Greenhopper used a custom field named 'epic_link' at an issue. Please try to delete this field it is legacy.

[Nancy Belser]

Hi Florian,

From what I am reading, Epic Link is a calculated field to aid in JQL searches and is a newer greenhopper feature:

https://answers.atlassian.com/questions/141516/can-you-bulk-edit-the-epic-link-field

https://confluence.atlassian.com/display/GHKB/Epic+Name+vs+Epic+Link

The real epic/story relationship is set via a row in the issuelink table. Deleting the epic link customfield will not solve this problem as it is only a derivative of the issuelink table relationship. What I see as the problem is as I originally stated: the story map plugin is not creating a row in the issuelink table when I create a story off of an epic in the plugin.