Multiple Epic-Story-Link issuelinktype which stops queries working

Chris Hodgens June 17, 2013

We appear to have an issue in our JIRA system that stops some of the Grovey scripts working. We are using JIRA 5.2.7 and Greenhopper 6.2.2.2. When trying to use the

issueFunction in linkedIssuesOf("resolution = unresolved", "has Epic") I get an error
"More than one link type with description: has Epic". When I look at the issuelink table I see multiple entries for Epic-Story-Link which I guess are causing the error:
ID LINKNAME INWARD OUTWARD pstyle
10000 Dependency blocks depends on NULL
10001 Duplicate is duplicated by duplicates NULL
10010 jira_subtask_link jira_subtask_inward jira_subtask_outward jira_subtask
10020 Linked links to links to NULL
10030 Cloners Cloned from Cloned as NULL
10031 Replacement is replaced by replaces NULL
10040 Gantt Dependency has to be done after has to be done before Gantt
10050 Epic-Story Link has Epic is Epic of jira_gh_epic_story
10051 Epic-Story Link has Epic is Epic of jira_gh_epic_story
10052 Epic-Story Link has Epic is Epic of jira_gh_epic_story
10053 Epic-Story Link has Epic is Epic of jira_gh_epic_story
10054 Epic-Story Link has Epic is Epic of jira_gh_epic_story
10055 Epic-Story Link has Epic is Epic of jira_gh_epic_story
10056 Epic-Story Link has Epic is Epic of jira_gh_epic_story
10057 Epic-Story Link has Epic is Epic of jira_gh_epic_story
10058 Epic-Story Link has Epic is Epic of jira_gh_epic_story
10059 Epic-Story Link has Epic is Epic of jira_gh_epic_story
I tried figuring out which of the duplicates is used to delete the others, but when trying to check the issuelink for items that are linked (ie where we have used the epic link in JIRA to link stories to Epics), nothing comes back - select * from jira.dbo.issuelink where linktype > 10050
So firstly, anyone know how I can figure out which rows I can delete to have just one Epic-Story-Link and secondly wht is the schema that JIRA uses to link Epics and stories so that I can find the links already in use and see which ones they use?
Thanks

5 answers

1 accepted

1 vote
Answer accepted
John Garcia
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 29, 2013

These queries should expose the Epic linked issues, as well as the correct linktype to use:

SELECT * FROM issuelink WHERE linktype IN (SELECT id FROM issuelinktype WHERE linkname = 'Epic-Story Link')
SELECT * FROM propertynumber where ID = (select id from propertyentry where PROPERTY_KEY = 'GreenHopper.Epic.Default.linktype.id');

Once you've got that info, just make sure all of the issue links shown use the linktype described in the second query.

0 votes
Saikat Paul January 23, 2014

I was able to resolve this with the help of Atlassian support. Due to one of the upgrades, multiple issue links were created. A DB change had to be made to remove the duplicate links.

Nirmani Kalakheti
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 24, 2020

@Saikat Paul , Would you be so kind as to share your resolutions here?

Like Nirmani Kalakheti likes this
0 votes
ITSupport January 23, 2014

Do you have resolution?!

0 votes
Chris Hodgens October 9, 2013

Unfortunatly the link takes me to a secure JIRA area that I have no access to.

0 votes
Saikat Paul October 9, 2013

I've got the same issue. Trying to figure it out with Jamie, the author of ScriptRunner. You can follow here:

https://jira.tubemogul.info/secure/admin/groovy/GroovyRunner.jspa

Chris Hodgens October 15, 2013

did you manage to get anywhere with this? The link above is not open to the public.

Thanks

Saikat Paul October 17, 2013

No, it turns out it is the same problem you have listed. Jamie suggested contacting JIRA support to figure out the issue. I'm working with out IT team to resolve it. Once done, I will post an update here.

Suggest an answer

Log in or Sign up to answer