| Reporter |
andrey tigay (andrey.tigay)
|
|---|---|
| Created | Mar 13, 2013 1:29:08 PM |
| Updated | May 7, 2013 2:14:56 PM |
| Resolved | May 7, 2013 2:06:45 PM |
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 hsould 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 need 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 hsould 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 need 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.