adding/removing artifacts from modules
Hi all,
first of all, I'm novice RRC user. I'm looking for the answer if there is possible to link one artifact into the same module twice, is it a standard behavior, and what consequences it may have on removing one of it - eg. should I expect both of them will be removed?
The exact case I have is two people add the same artifact into a module and after that one decided to remove duplicate (should I call it "duplicate"?). In my case, this operation locks user account and it's not possible to add or remove anything from the module. I did not find anything that could help me (novice user) to understand is it a problem related to application itself (it's configuration maybe?) or the way I use it?
--
RRC 5.0.2
|
One answer
Hi again,
thanks for answer. I think it is solved now. The problem was because it is possible to "sort" artifacts using artifact ID (clicking on the column name). You cannot do much when you have such "sorting" applied. I also wonder, not able to check it now, is that "sorting" saved on my view, probably yes, I saved it when I tried to find duplicates ("sorting" artifacts by their ID was the best approach for me to find duplicates). Interesting that nobody thought about prevent such case which seems to be obvious for me - when you look for double occurrence - sort the list first, and no hints are shown just some features are not accessible, that all. I lost a lot of time and nerves because of that.
Regards,
John
Comments
Donald Nong
commented Feb 05 '15, 2:30 a.m.
When you sort the artifacts on a particular attribute, the module is effectively in the "view" mode, where you cannot change the module's structure. I believe this is intentional as the module may not be in its proper "book order" in this case.
|
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.
Comments
I have tried this and can add an artifact to a module twice (using 'Add an Existing Artifact...' - is that how you do it?). It seems to work fine. When removing the artefact from one place I choose 'Remove' (rather than 'Remove and Delete') and that also works fine - the copy gets removed and the original remains in place. I would guess that 'Remove and Delete' would get rid of both as the underlying base artefact would no longer exist.
I am using 5.0.0 with fix 006.
Are you sure the user and module lockout are related to the deletion of the artefact - they sound severe and I have not seen anything like that (still somewhat of a novice myself though).
What are the specific symptoms of the user lockout and what errors if any do you get when you try to edit the module?