Hi Ryan Thanks for your answer. I'm aware of the product specific permission schemes. Our problem is the global dashboard displaying all tickets and products. We would need a global dashboard that filters the tickets and products based on the permission schemes on the products. That would also involve filtering the products in the create ticket dialog. Do you think this would be a useful extension of the dashboard? We would be interested in contributing to this change. How do we get this into a feature ticket?
-----Ursprüngliche Nachricht----- Von: Ryan J Ollos [mailto:rjol...@apache.org] Gesendet: Mittwoch, 30. November 2016 09:30 An: dev@bloodhound.apache.org Betreff: Re: How are products intended to be used? On Mon, Nov 28, 2016 at 7:51 AM Ferhat Günes - Vertec AG < ferhat.gue...@vertec.com> wrote: Dear Bloodhound community We are looking for a multi project management system for our clients. We thought Bloodhound would be a good solution since we are already working with Trac internally and built up some know-how. Now we don’t get any further because we don’t understand how products are intended to be used. Every client should get his own project and should not be able to see other clients projects and tasks. Unfortunately, I was not able to put that into action with Bloodhound’s permission system. We are ready to invest resources, but don’t know where to start. I think there should be some filtering of products and tickets based on product specific permissions. I found the following issue that deals with something similar https://issues.apache.org/bloodhound/ticket/572. Are these missing features or is Bloodhound meant to be used differently? Each product can have its own permission scheme. https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003#permissions For more information, take a look at the answer to a similar question: http://markmail.org/message/gqnzokeg6ye32tnn - Ryan
