Error when creating requirement in sandbox
I am trying to create a requirement (using default requirement type) in the sandbox environment and getting the following error:
Error 500: Internal Server Error Error updating artifact. Could not add identifier; no identifier attribute definition found for project context: https://jazz.net/sandbox01-jts/process/project-areas/_5txyAfAzEeCtO5XmfeTL-Q (More info found at entry in RRS server log) Can anybody suggest what might be wrong? |
4 answers
I am trying to create a requirement (using default requirement type) in the sandbox environment and getting the following error: A 500 error is usually an authentication error, usually a missing license (Rational Analyst), or role in the project area (Author), JazzUser or the server is not available. |
I am trying to create a requirement (using default requirement type) in the sandbox environment and getting the following error: A 500 error is usually an authentication error, usually a missing license (Rational Analyst), or role in the project area (Author), JazzUser or the server is not available. I granted all of the roles that were available in the environment. Given it's the sandbox environment is it reasonable to assume all required licenses are present? Is there any way to narrow things down? Thanks! |
At work, we have created 3 accounts in the sandbox at https://jazz.net/development/sandbox/
-account #1 was created a while ago and has all required licenses. -account #2 & #3 were created on Fri and only have RTC licenses. With accounts 2 & 3, we cannot create requirements/collections or test related artifacts. What should we do? |
At work, we have created 3 accounts in the sandbox at https://jazz.net/development/sandbox/ Which RTC Licences are you using? Some only provide read access as described in Table 1 of the help: http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.jazz.repository.web.admin.doc%2Ftopics%2Fc_license_mgmt_over.html |
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.