Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Add option to never sync changes when issue is filtered by a JQL
Won't Do
Description
Backbone provides an option to filter issues based on a custom JQL. Every time Backbone checks for changes, it also evaluates the provided JQL. Now, if changes happen in the time an issue is not synced because the JQL filter is not matching the issue, these changes are synced again as soon as the issue is matched by the JQL filter. However, in certain cases this might not be desired. For example:
a comment is added in that time
a field gets a new value (which should not be shown to the other side), but this field is changed again as soon as the JQL is matching again and then the value should be synced
We could add an option to let users activate this feature.
Notes
There are open questions to clarify the desired behaviour:
what happens to changes if a sync is stopped? how should this behave?
should this option be available on a sync basis or on a field basis?
Workaround
At least for comments there is a workaround that you use groups in order to make comments (in-)visible to the sync user. Nothing is synced if the sync user does not have enough permissions to see a comment, hence simply restrict a comment if it shouldn't be synced.
We are closing this ticket because we want to be honest to our customers - we are not planning to implement this request anytime soon. Other than that, for the comments, please check out the workaround mentioned in the description.
Backbone provides an option to filter issues based on a custom JQL. Every time Backbone checks for changes, it also evaluates the provided JQL. Now, if changes happen in the time an issue is not synced because the JQL filter is not matching the issue, these changes are synced again as soon as the issue is matched by the JQL filter. However, in certain cases this might not be desired. For example:
a comment is added in that time
a field gets a new value (which should not be shown to the other side), but this field is changed again as soon as the JQL is matching again and then the value should be synced
We could add an option to let users activate this feature.
Notes
There are open questions to clarify the desired behaviour:
what happens to changes if a sync is stopped? how should this behave?
should this option be available on a sync basis or on a field basis?
Workaround
At least for comments there is a workaround that you use groups in order to make comments (in-)visible to the sync user. Nothing is synced if the sync user does not have enough permissions to see a comment, hence simply restrict a comment if it shouldn't be synced.