BUG: Issue links are lost if the same issue is linked to more than one issues
GOAL
When I add a story/bug to Structure, I want all linked test cases to be added automaticallySETUP
Create and enable the following Synchronization
Issue Links
Links (Test Coverage)
Parent issue Test Coverage sub-issue
Parent issue JQL: issuetype in (story, bug)
Sub-issue JQL: issuetype = "Test Case"
Sync issues in structure and all sub-issues linked from them
Move sub-issues with no incoming links upwards
Links primacy
NOTE: “Test Coverage” is a custom link typeUSE CASE
a) Link TestCase1 and TestCase2 to StoryA through “Test Coverage” link type
b) Link the same TestCase1 and TestCase2 to StoryB through “Test Coverage” link type
c) Add StoryA to structure: TestCase1/2 added as well (EXPECTED)
d) Add StoryB to structure: TestCase1/2 added as well (EXPECTED)
e) Because of current Structure limitation, TestCase1/2 removed from StoryA in Structure (EXPECTED)
PROBLEM:
f) As a result of “d”, StoryA no longer has links to TestCase1 and TestCase_2
I believe this is a bug in Primacy setting of the synchronizer
-
-
Sonja Fruenke commented
We've run into this scenario too. Is there any indication when Structure 3.0 will be released?
-
Awesome, thanks :)
-- Igor
-
Michael Voronkov commented
no worries, I still love the tool and will help to make it better
-
Michael,
Sorry once again for the frustration the synchronizers may have caused. Except for synchronizers, Structure is indeed just an extra layer on top of JIRA. Synchronizers though... they are powerful but turned out to be too easy to use incorrectly.
That's why we never took away the "experimental" flag on the synchronizer's page; and the replacement for the synchronizers in 3.0 works differently. I hope the new version will not disappoint.
Kind regards,
Igor -
Michael Voronkov commented
I am aware with current Structure limitation of not allowing more than one instance of the issue.
Jira linkage is Jira's internal functionality that should not be affected by other plug-ins. Structure is positioned as "not-invasive" plug-in, but in this case it really is invasive, hence the bug.
Patiently waiting for Structure 3.0 ..... -
Hello Frank,
Thank you very much for taking time to record this use case and the problem! Indeed, you are right, the constraint of having only one parent forces Links synchronizer to resolve the conflict and remove the link, even with Links primacy.
I apologize for any inconvenience caused. This is a known behavior which we're going to address by introducing multi-parent feature in Structure 3.0. Please bear with us for some time!
Kind regards,
Igor -
Frank Schophuizen commented
This is because an issue in a structure can have only a single parent. So when adding a link to another parent, the issue is moved to the new location in the structure. Because it is removed from the old location, the synchronizer will remove the link to the old parent.
To resolve you should be able to have multiple parents. See http://structure.uservoice.com/forums/43181-structure-plugin-for-jira-ideas/suggestions/2329637-allow-an-issue-to-be-located-in-multiple-places-wi