There was extended search algorithm, which resolves epic issue for epic link:
- epic link is consider to be issue key, or
- epic link is consider to be epic name of an epic, which is inside the same project as the epic story, which defines epic link, or
- epic link is consider to be epic name of an epic, which is defined in some project (it has to be unique epic name over all projects, if it want to be resolved) - it is because of back compatibility
Tested:
It was tested by integration test:
it.com.atlassian.jira.webtest.selenium.admin.imports.csv.TestCsvCustomFields.testGHEpicImport()
for next scenarios:
- epic link is to epic defined by issue key
- epic link is to epic defined by epic name and is in a same project as a epic story
- epic link is to epic defined by epic name which is in different project as a epic story
There was extended search algorithm, which resolves epic issue for epic link:
Tested:
It was tested by integration test:
it.com.atlassian.jira.webtest.selenium.admin.imports.csv.TestCsvCustomFields.testGHEpicImport()
for next scenarios: