Update handling of attachments in development system integrations

What is the challenge?

Currently there are situations where attachments can be deleted via integration. Generally, attachments should never be deleted in the dev system if they were deleted in Aha! Roadmaps (and vice versa.)

What is the impact?

Someone could unknowingly delete a very important attachment in the dev system or Aha! Roadmaps.

Describe your idea

• Deleting an attachment in the development system should not delete the attachment in Aha! Roadmaps

• Deleting an attachment in Aha! Roadmaps should not delete the attachment in the development system

• You should, however, be able to replace an attachment (since often times there may be a more current version)