Is it possible to prevent users from creating personal queries?
Hi, Is it possible to prevent users from creating personal queries? My customer needs to keep certain users, who can create some workitems, from creating presonal queries. I verified that if a "save query" is not granted, the user can create and update personal queries. When this user try to update shared queries, that operation is not allowed.
Is there any way to prevent users from creating personal queries? My customer ueses RTC 4.0.3.
Natsumi
Thank you in advance |
2 answers
I don't think this is possible. RTC is a tool aimed at collaboration, so we do not restrict collaboration by turning off features. Data security is obtained at data level, i.e., you can restrict some users from viewing certain workitems, so that they do not pop up in query results.
Can you please elaborate why do you not want users to run personal queries? Comments
Martin Wassermann
commented Oct 01 '13, 4:30 a.m.
@paniola For legal reasons. For some companies it is important that the company can't use the tool to measure the efficiency of the workers. Especially in companies who have a worker's council this could be a valid precondition for using RTC.
Andrew Trobec
commented Oct 01 '13, 5:07 a.m.
what about limiting visibility of work items by using team areas?
there is more than one way to extract information, even if this means opening each work item individually and copying data into excel...
Limiting visibility doesn't really help (see my comment beneath)
Natsumi Yokoyama
commented Oct 01 '13, 9:27 p.m.
In my case, what customer wants to do is to implement a ticket management system in their application maintenance department. The scenario what customer wants to do is following. There are two types of project areas in RTC. One is a project area for ticket management, others are for application development. The project area for ticket management is shared with LOB and application development teams. In this project area, at first, LOB's member creates a ticket. After a leader of dev team updates some estimated workload information on this workitem, dev team does not want to share only this information with LOB. (This requirement is another issue to implement.) Offcourse, actual and detailed workload information is managed as tasks or defects in other project area for application developmet . But some information about estimated workload is needed to be managed per ticket. Bucause of reporting requirements and so on. I understood above scenario is difficult to implement using RTC. I want to show them workaround. Natsumi
|
Hi Martin and Natsumi,
You can try using workitem visibility restriction function: https://jazz.net/library/article/554/ Let us know if it helps you. Comments
Martin Wassermann
commented Oct 01 '13, 4:51 a.m.
But that's something different. The work item visibility restriction doesn't prevent e.g. a Project Manager to create and run queries to measure the efficiency of his team.
Natsumi Yokoyama
commented Oct 01 '13, 9:44 p.m.
Hi, Krzysztof and Martin
Thank you for your comments. My understanding is that "visibility restriction" controlles visibility per workitem. Is there any workarround to controlle visibility per attribute and role(or team)?
Natsumi
|
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
I'm interested in that topic too. Addition it is interesting for me if it's possible to prevent that a user to run a shared query that he has modified without saving.