On Mon, Sep 9, 2013 at 6:42 PM, Kevin Falcone <[email protected]> wrote: > On Fri, Sep 06, 2013 at 11:24:45AM +0200, Christophe Vandeplas wrote: >> Thank you Kevin and Landon for the reply ! >> >> After fiddling a little bit more ... woohoo, now I get it... > >> I tried to follow this guide: >> http://bestpractical.com/docs/rtir/3.0/Constituencies.html#Managing-Constituency-Values >> However some things were not really clear to me. >> >> Kevin, >> Would you be able to update the Constituencies.html documentation a >> little bit to make it clear that the newly created Queues are there >> only for technical reasons, and are NOT meant to be used directly >> reasons? > > Are you up to sending a patch to the docs making it clearer? > There are directions on getting a copy of the rtir source here > http://bestpractical.com/rtir/git.html > and these days github will even let you generate pull requests almost > directly from the UI.
done: https://github.com/bestpractical/rtir/pull/1 >> Downsides: >> - everyone sees the statistics of the queues statuses in the "Quick >> search home screen" (number of new, open tickets) > > This is a known problem with how Constituencies are implemented, and > not easy to resolve. > >> - administrator user sees the newly created queues, however these >> queues are NOT functionally needed by the operator. (normal user >> doesn't see these queues) > > As long as it's only Administrators, this is ok. Default permissions > should not be for DutyTeam or DutyTeam Foo members to see those > queues. > > -kevin > > _______________________________________________ > Rtir mailing list > [email protected] > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rtir > _______________________________________________ Rtir mailing list [email protected] http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rtir
