It sounds like you are talking about read-access control on your work items.
In RTC read-access control is defined primarily at the project area level, and starting in RTC-3.0, also at the team area level. So if you only want a group of people to see a certain set of work items, you would create a project or team area, and give those people read access only to that project/team area. You could then further constrain what write permissions they have, based on the role they are given in the project/team area.

Cheers,
Geoff

Hello Jazz community members :)

Atm we use RTC for out projekt developement and testing (through workflow states from solved -> to proved and with Approvals)

We get workitems from our support team members,
which are receiving telephone calls or emails from the customers and create them directly in RTC as a story.


Now our company want to "optimize" our process and get users (potentially everyone) to report bugs or requested features on their own.
In earlier projects we use OTRS (as i mentioned already in this post and asked for help: https://jazz.net/forums/viewtopic.php?t=19245&highlight=otrs)
Is there any option to integrate the output of ORTS into RTC?

How does bugtracking on the RTC project pages work?
(e.g. for https://jazz.net/projects/rational-team-concert/)
If i have a jazz.net account, i can see nearly everything in the project and create workitems?
Is it possible to integrate this in our project... without the "see everything" - part? xD


At least, i read about Rational Clear Quest... which seems not far away from what we want, but i didn't find more helpfull information about this?
And Rational Requirement Composer?

What would be the preferred solution to communicate with our wide-ranged customerbase and allow them to report bugs/requests without directly integrate them to our change and configuration management system?

best regards
- the incredible Leitman