Two versions of asset and merging
One of our user faced a strange issue on asset versions and merging of assets. When we tested even we found that it is a kind of bug. Following are the details and use-case :
1) User submits an asset abc with v1.0. 2) User moved the Draft state asset abc into As-is. 3) User modified the abc asset, change its version to 1.1 and resubmitted (asset will remain Draft). 4) Its worked as designed and RAM created 2 versions of the same asset abc with one version in As-Is state and other version in Draft state. Please note that the As-is state version is 1.0 and Draft is 1.1. 5) As designed, there were no actions (modify, delete, etc.) available for As-is state asset. 6) When user changed the state of Draft asset into As-Is, it didn't merged with its As-Is state asset and As-Is state asset got stuck in its no-actions available mode. Please comment on the above use-case and let us know how we can delete that stuck As-is state asset. |
12 answers
|
The issue is that we tested this scenario using a test asset and found that because of change in version of the asset, merging is affected and RAM creates a new asset with the new version. If anything is not clear to you, please let me know and i will give you a use case for the same.
|
What is your definition of a new asset? You will have two assets until you move the draft asset into As-is state. Until that happens there are two assets.
So did you wind up with two assets in As-is state? If you did, please give me access to the testcase because it shouldn't happen. I looked at the live example you gave me and it was fine because the draft asset had not yet been moved to As-is. |
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.