xmera Omnia

🐛 Thanks for taking the time to fill out this bug report! 😊

What did you expect?¶

When I sync issues from a source object I expect to get only those issue relations which are part of the source and do not document where the source issue was already synced to.

What has happened instead?¶

Every related issue of the source issue will be synced into another object. Even the sync history of the source is synced leading
to the effect that this historical information will rise from syc to sync.

What could be a possible solution?¶

Exclude the sync history of the source from syncing. Allow only to document the sync between the current source and target if the
user has allowed to do so.

How can we reproduce the problem?¶

1. Create some issues in a project.
2. Configure the plugin settings to use that project as sync catalogue.
3. Configure some receiving projects to sync from the catalogue.
4. Execute the sync in each of the receiving projects.
5. Observer the sync history in all involved projects.

In what environment are you running the plugin?¶

Please copy and paste your environment information as displayed in Administration » Information or run bin/about in the root dir of your Redmine instance.

What browsers are you seeing the problem on?¶

• Firefox
• Chrome
• Safari

Relevant log output¶

# Copy your log output (log/production.log) here