REST-API: Original Project Area name not working in REST API URL
Hello,
|
2 answers
Hi Georg!
You have successfully logged into Jazz Team Server but not able to access the Project 'TDG1_QA_CLONE3'. Thanks, Jörg [we use RQM 6.0.3] Comments
Georg Kellner
commented Apr 06 '17, 5:58 a.m.
We've discovered this behavior after renaming some project areas.
|
A similar discussion took place two years ago.
If you replace the term "alias" with "ID", you will understand why. If you do what Ara suggested, to get a list of the project areas, you will see that the "alias" is referred to as "identifier", whereas the project name as "title". I believe in your case "TDG1_QA_CLONE3" is actually the "original" (as when first created) project name. The fact that you can use "TDG1 Demo" in some requests should not matter. Comments
Jörg Werner
commented Apr 10 '17, 2:53 a.m.
Yes Don, TDG1_QA_CLONE3 is the original name and was later renamed.
You have successfully logged into Jazz Team Server but not able to access the Project 'TDG1_QA_CLONE3'.
Donald Nong
commented Apr 10 '17, 3:23 a.m.
When you say you "want to open the project area", what URL are you going to use? Is it still related to REST API? The web UI may use a different logic and has different requirements.
|
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
Jorg,
Thanks Ara!
Two questions:
1) Can I change the alias?
2) Why I have to use the alias in the above query and can not use the standard project name?
Cheers, Jörg
Hi Jörg,
you can change the project name as often as you want to.
So using the alias is more stable instead of using the project name.
Greetings Georg.