Synchronization Error Handling of Duplicate Requirements with the same parent (176 Views)
Reply
Advisor
cocarp2000
Posts: 34
Registered: ‎07-02-2012
Message 1 of 3 (176 Views)

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. 

-Chris Carpenter

Please use plain text.
Valued Contributor
razido
Posts: 68
Registered: ‎03-14-2012
Message 2 of 3 (121 Views)

Re: Synchronization Error Handling of Duplicate Requirements with the same parent

Hello Chris,

 

Thanks for this input. I have some questions regarding your suggested solutions:

 

1. If we go for the first option (treating in AGM)- Will your users be ok  with not allowing it in AGM at all? Is having this limitation configurable a satisfating solution?

2. If we go for the first option (notification in AGM)- will a notification do? and in that case would you expect your users to rename the requirement and it they don’t is it ok to not sync?

3. If we add some kind of a unique suffix- would you expect the changed name to be synchronized to the other side as well to keep data consistency?

 

Thanks,

 

Ido

Please use plain text.
Advisor
cocarp2000
Posts: 34
Registered: ‎07-02-2012
Message 3 of 3 (112 Views)

Re: Synchronization Error Handling of Duplicate Requirements with the same parent

1. If we go for the first option (treating in AGM)- Will your users be ok  with not allowing it in AGM at all? Is having this limitation configurable a satisfating solution?

Users are restricted to this in ALM, I believe they would be ok having this same limitation in AGM. 

2. If we go for the first option (notification in AGM)- will a notification do? and in that case would you expect your users to rename the requirement and it they don’t is it ok to not sync?

A notification might work, but thats putting a bandaid on the situation.  There will be some users that will disregard the notification and do it anyways.

3. If we add some kind of a unique suffix- would you expect the changed name to be synchronized to the other side as well to keep data consistency?

I would expect the name change to be synchronized. 

 

 

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation