Synchronization Error Handling of Duplicate Requirements with the same parent
We have gotten some feedback from our users that they absolutely dislike the way duplicate requirements (or requirements with the same name) are handled. Today the AGM synchronizer documentation states that requirements essentially need to be uniquely named. But this is not a reality for us. Something needs to change either in AGM where the user is notified they just created a requirement with a duplicate name, or the synchronizer need to update the name of the requirement somehow to ensure synchronization takes place. Today it simply errors out.