"prevent adding user owned component" pre-condition failing with other operation
![]()
Ratheesh Madathil (137●15●26)
| asked Aug 14 '14, 5:35 a.m.
edited Aug 20 '14, 2:56 p.m. by Stephanie Taylor (241●1●5)
We have enabled:
"prevent adding user owned component" pre-condition for "default role". But this now behaves strange. If a user tries to acquire a lock on a file or try to "unlock" a file, the team advisor pops up with this error message: ------------ Problem An unhandled exception occurred during "Prevent Adding User Owned Component ". Wrong type of argument: null Reason Prevent adding user owned component ----------------- Strangely this action has nothing to do with "User Owned component"!!. When remove this pre-condition, the lock action and unlock action works fine without any errors. Is somebody else have experienced the same? |
Accepted answer
![]()
Geoffrey Clemm (30.1k●2●30●35)
| answered Aug 14 '14, 6:26 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
This should be reported as a defect, so the dev team can fix it.
Ratheesh Madathil selected this answer as the correct answer
|
One other answer
![]()
Defect link:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=328010&tab=com.ibm.team.workitem.tab.history |