RTC permissions questions
Hi - we are working on a small web project, the code is being managed in RTC. We'd like to find a way that anyone in the department (>1000 people in a Blue Group), or possibly, anyone in IBM, can raise defects against the project. These people do not need to be able to see source code or work on defects. After some looking around I'm still not sure what the best way to achieve this would be? Can anyone point me in the right direction?
Thanks, Zoe
Thanks, Zoe
4 answers
Hi Zoe,
In order to user be able to perform any action, he needs to be added to RTC. There is no anonymous access yet. In other words you must rtc users RTC group must be mapped to ldap group where are all users who you want they have an access.
Another issue is licenses. I believe that you can configure floating licensing server then you will not have separate license for each user.
Let us know if it helps for you.
In order to user be able to perform any action, he needs to be added to RTC. There is no anonymous access yet. In other words you must rtc users RTC group must be mapped to ldap group where are all users who you want they have an access.
Another issue is licenses. I believe that you can configure floating licensing server then you will not have separate license for each user.
Let us know if it helps for you.
Maybe you could have a website generating an email and read those mails to create work items.
See this link for an email reader: http://www.cm-logic.com/jazzconnect-email.html
Or here for an email importer: https://jazz.net/wiki/bin/view/Main/WorkItemEmailImport
And for a future solution: Create e change request against Team Concert to have a anonymous user with the ability to create work items.
See this link for an email reader: http://www.cm-logic.com/jazzconnect-email.html
Or here for an email importer: https://jazz.net/wiki/bin/view/Main/WorkItemEmailImport
And for a future solution: Create e change request against Team Concert to have a anonymous user with the ability to create work items.
Comments
This answer makes most sense to me at the moment. I can see that other groups appear to have implemented something that looks like PHP code creating work items.
There is some useful content in the other answers but my understanding (possibly incorrect) is that I would still have to have to maintain RTC User IDs for everyone that might want to submit a bug. If so that would not work for the kind of numbers I had in mind.
the following article provides the solution which i think you are looking for
https://jazz.net/library/article/215
https://jazz.net/library/article/215
Comments
Not sure where there is an "everybody shall be able to submit"-part.
Maybe I haven't seen it?
https://jazz.net/library/article/215#protect_some
You can protect the visibility of the components instead of trying to set the visibility of work items. The project area should be open but the components should be owned and only visible to a team area.