Note
We've packed up and moved from Confluence to Discourse to bring you a better, more interactive space. Out of courtesy we didn't migrate your user account so - you will have to signup again
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
Hi,
I’m experiencing a Jira status sync thrash when synchronizing a newly created issues whose statuses have changed before the first sync completes.
In my case, the two statuses in question (Draft and Ready for Grooming) are present on both sides of the sync, so no mapping is required (although I do use a mapping for other statuses).
Steps to reproduce:
Actual results: issue syncs and creates CS-2803 in Ready for Grooming status, but then DEV-14602 is reset back to Draft status
Expected result: both DEV-14602 and CS-2803 are sync’d in Ready for Grooming status
Note:
I reproduced the behavior again this morning, although the result was a little different. In this case, on the incoming side the status was reset to Draft and then Ready for Grooming, while the outgoing side was reset back to draft.
Expected result: both sides synchronized to Ready for Grooming status, which is the last status set by a user.