Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

How to duplicate an asset but not its relationships

Greetings All,

When a user duplicates an asset, it is their responsibility to clean up any unneeded relationships or other content that they do not want on the new asset.  Problem is that sometimes users forget to do this, and it can create a mess of tangled relationships between assets that aren't truly related.

Is there a way to delete relationships on the new asset when the duplicate/version feature is used?  I suppose a custom policy could do it, but how do you trigger a policy for the duplicate action?

Thanks for any help!

0 votes

Comments

The more I think about it, a custom policy seems to be an ugly way to solve this problem.  Assuming I could write a custom policy to delete old relationships, where would I call it from?  How would it tell the difference between a "duplicate" action and something else, such as a retire/restore action?


Looking for any solution rght now, but hopefully there's something simple and straightforward available.

Thoughts? 


Be the first one to answer this question!

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,031

Question asked: Jun 24 '14, 10:30 a.m.

Question was seen: 4,501 times

Last updated: Jun 24 '14, 10:41 a.m.

Confirmation Cancel Confirm