Originally asked by ben friedman on 29 October 2020 (original question)
Hi,
in the connection setup, from ZD to Jira, the rule filter is based on a tag:jira (which is created from a check box). however, then an issue is updated from JSD to ZD, the jira tag disappears (as well as other tags).
How can i protect the ZD tagsfrom being over-written by JSD?
i need the jira tag to be able to maintain the sync going.
Thanks
Comments:
ben friedman commented on 29 October 2020
from what im seeing - after the first sync from ZD to JSD, the Jira tag is in the JSD issue. after that, when i examine both replicas, they both contain the Jira tag. after i update from JSD, the Jira label disappers from the replicas.
any thoughts?
ben friedman commented on 29 October 2020
there isnt a tag locker on the ZD side. and all the other tags/lables go through. just the Jira label isnt coming through.
Juan Grases commented on 29 October 2020
Could you confirm that the Jira is sending the labels (tags)
//Jira Outgoing
replica.labels = issue.labels
ben friedman commented on 30 October 2020
yes, that is on.
in the local replica, when sending back from JSD to ZD, the label exists.
when its being sent to ZD, it doesnt register.
The tag is being formed from a checkbox field. on the ZD, that field registers as false (i.e not checked).
i think the tag might be syncing, but its then removed since the check box field is set to false.
what should i add in the incoming sync on ZD to make sure the checkbox is always checked?