Reporter |
![]() |
---|---|
Created | Mar 13, 2013 1:31:41 PM |
Updated | Mar 13, 2013 1:59:10 PM |
Priority | Normal |
Type | Task |
State | Open |
Assignee | Dmitry Krasilschikov (dima) |
Subsystem | Workflow |
Fix versions | No Fix versions |
Fixed in builds | No Fixed in build |
Affected versions | No Affected versions |
Browser | Any Browser |
OS | Any OS |
Verified in build | Not verified |
Verified by | Nobody |
Reviewed by | No reviewed by |
Severity | Routine |
Please look at the http://youtrack.jetbrains.com/issue/JT-18189#comment=27-458201
That's correct behaviour as It shows the fix of http://youtrack.jetbrains.com/issue/JT-18189 , but we should create a workaround when we need to sync different bundles from different projects.
Conditions: Project1 has the Resolved state, Project2 has not this state. When the Resolved state sets in Project1's issue, it should be synced with Project2's issue.
I assume we can do the following: if there is no Resolve state in Project2, we can set the nearest state of resolved type (Fixed, Verified, Duplicate and others).
Please check this.
That's correct behaviour as It shows the fix of http://youtrack.jetbrains.com/issue/JT-18189 , but we should create a workaround when we need to sync different bundles from different projects.
Conditions: Project1 has the Resolved state, Project2 has not this state. When the Resolved state sets in Project1's issue, it should be synced with Project2's issue.
I assume we can do the following: if there is no Resolve state in Project2, we can set the nearest state of resolved type (Fixed, Verified, Duplicate and others).
Please check this.