It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,785

question asked: May 19 '10, 11:55 a.m.
question was seen: 4,366 times
last updated: May 19 '10, 11:55 a.m.

Related questions

FAQ - How this Forum works

Restriction of Permissions

0
Marco Bormann (161●19●10) | asked May 19 '10, 11:55 a.m.
I want Clients to be able to report bugs, thus create BUG-workitems with their description, but I don't want them to see the further life-cycle of the bug once it has been assigned.

My plan was to create a User Role called Client who can only create bug-workitems, alter their description and add comments and but can do no further action.
Then I wanted to create some prefigured queries which show only those bugs created by Client-users and deny the permission to create new queries to those users.

Here's the problem: It actually worked the other way around; I could not get my client to save bugs he created and I could not restrict him from at least running queries, even if he cannot save them.

Do I have the correct approach or is there any other way to achieve my goal?

Thanks Marco

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered May 19 '10, 11:27 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In general, you have fine grained control on write operations, but you
do not have fine-grained control on read operations. In particular,
read access for an object is determined by the read access defined on
the project area to which that object belongs. So there is no way to
modify read access based on any property of an object other than its
project area property.

Cheers,
Geoff


On 5/19/2010 12:08 PM, MarcoB wrote:
I want Clients to be able to report bugs, thus create BUG-workitems
with their description, but I don't want them to see the further
life-cycle of the bug once it has been assigned.

My plan was to create a User Role called Client who can only create
bug-workitems, alter their description and add comments and but can
do no further action.
Then I wanted to create some prefigured queries which show only those
bugs created by Client-users and deny the permission to create new
queries to those users.

Here's the problem: It actually worked the other way around; I could
not get my client to save bugs he created and I could not restrict
him from at least running queries, even if he cannot save them.

Do I have the correct approach or is there any other way to achieve my
goal?

Thanks Marco

Your answer

Register or to post 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.