Hi
I have been using RTx:Tags and am finding it quite useful but I have been
trying to figure out how I can have different the terms in the tagcloud that
is shown be dependent on the queue that the person has permission to view.
At the moment I have the tags custom field assigned to a single queue
"General" but a user that does not have access to that queue sees the
tagcloud in the simple search. They don’t see any tickets under the tags but
I was wondering if they should be seeing the tagcloud at all?
I have tried creating another customfield tags and assigning this to the
other queue in an effort to give them their own custom tagcloud but that has
not worked. For all users outside of those with permission for the General
queue the tagcloud if full of terms that have no relevance to them.
Does anyone know how you might go about having tagclouds that are specific
to a queue?
Thank you
John
Does anyone know how you might go about having tagclouds that are specific
to a queue?
I never had the need. It’s not impossible, but would take considerable work.
Part of the problem is that for expediency the extension does its work
with raw SQL,
rather than the RT API. Therefore, it is not aware of users’ CF ACLs.
Although hacking
in that bit wouldn’t be too hard. Feel free to submit a bug report at
rt.cpan.org, but
I can’t make any guarantees when I might be able to do so.
However, I would make the case that while there may be some information leakage
through seeing tags on tickets one cannot access, access to a full
list of tags in
current use helps standardize tag names and reduce proliferation. Not
getting results
when clicking on tags ranks as a minor annoyance on par with search result count
not matching the number of returned results 
Hi Jerrad
The problem I have is that I users of the different queues are very
different, for example I have an IT specific queue and then I have a queue
for people working on things like event organisation and grant funding
proposals so the tags that I have in use for the IT queue are not relevant
in any way to the users of the Community queue so the tagcloud would quickly
become cluttered with irrelevant terms.
I might just look at removing it from simple search and just having it as an
option to be added to a dashboard so users in the IT queue can just add a
tagcloud to their dashboard but it won’t be cluttering up the simple search
for the other users. Is that something that should be easy to do?
Thank youOn Fri, Aug 6, 2010 at 2:21 AM, Jerrad Pierce < jpierce@cambridgeenergyalliance.org> wrote:
Does anyone know how you might go about having tagclouds that are
specific
to a queue?
I never had the need. It’s not impossible, but would take considerable
work.
Part of the problem is that for expediency the extension does its work
with raw SQL,
rather than the RT API. Therefore, it is not aware of users’ CF ACLs.
Although hacking
in that bit wouldn’t be too hard. Feel free to submit a bug report at
rt.cpan.org, but
I can’t make any guarantees when I might be able to do so.
However, I would make the case that while there may be some information
leakage
through seeing tags on tickets one cannot access, access to a full
list of tags in
current use helps standardize tag names and reduce proliferation. Not
getting results
when clicking on tags ranks as a minor annoyance on par with search result
count
not matching the number of returned results