Return-Path: X-Original-To: apmail-bloodhound-user-archive@www.apache.org Delivered-To: apmail-bloodhound-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8241010F4E for ; Tue, 17 Sep 2013 19:10:07 +0000 (UTC) Received: (qmail 3236 invoked by uid 500); 17 Sep 2013 19:10:07 -0000 Delivered-To: apmail-bloodhound-user-archive@bloodhound.apache.org Received: (qmail 3226 invoked by uid 500); 17 Sep 2013 19:10:07 -0000 Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@bloodhound.apache.org Delivered-To: mailing list user@bloodhound.apache.org Received: (qmail 3218 invoked by uid 99); 17 Sep 2013 19:10:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Sep 2013 19:10:07 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of j@jdunk.com designates 208.97.132.74 as permitted sender) Received: from [208.97.132.74] (HELO homiemail-a13.g.dreamhost.com) (208.97.132.74) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Sep 2013 19:09:59 +0000 Received: from homiemail-a13.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a13.g.dreamhost.com (Postfix) with ESMTP id D9D3D33406F for ; Tue, 17 Sep 2013 12:09:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=jdunk.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to: content-type; s=jdunk.com; bh=iNqNzoVpD36PmsCH77BFlmZVP5E=; b=ir MqTFpMMbtd0aVcfNe4pX6rXc0lsMI0N2NoYUYP0IV3ZX01lX1loAgGdqIfMazN4l 16OUdF1BHDI1uN+QjuHD47A1YiYLiT5RFTnjmQi4vEZwIbt5k3tfxGDTt9p8Fh7l Dai7B/DD++7qu0Cc278WppxouvcyL/LZAxBjDy5Aw= Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: j@jdunk.com) by homiemail-a13.g.dreamhost.com (Postfix) with ESMTPSA id BC4D7334072 for ; Tue, 17 Sep 2013 12:09:36 -0700 (PDT) Received: by mail-wi0-f171.google.com with SMTP id hm2so5377256wib.4 for ; Tue, 17 Sep 2013 12:09:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=nSRctqtXlfn8/HUXT33vbkq8aNcNQcab5PRHVTA4rOU=; b=VUfp4bh8gMEabJUEqC+DbmCB6Q+L6g069J0CixcLZbe9wUK7nW2IdeXXeBm/ovz+Wj roN2qLQajtesqg9BEnwIMUpNrURK0HUUXleoUzG2+hJ+Nfq767y+XwHW41CYRmoC2pZ7 xBX4VfFM0zA+xW4i7x4821QT5v+EON/svzhjSDTuLqkGrMyyDTULd4kICyqTd1wy+qfq ujTLZiKCoJMtWDHVqjfhZh3u5DrIezqzygwMDEqUa6laH/VJkDmQqk1eUdJBE9z0oidj /wXc+1KkC9KkM0gAcsEjvxKtDuyUsoPPar7tJhETGP7f50Mzw8vt2UTWT9IX3+itYcYh edUQ== X-Gm-Message-State: ALoCoQnYwS4cUiDYNRKqsd3B/9Xu6Tuhe+k1dleXFgFLm3b+y4Wr26SoRlOYYhEEHeL2ihJI4Vqa MIME-Version: 1.0 X-Received: by 10.180.102.73 with SMTP id fm9mr3783103wib.1.1379444969900; Tue, 17 Sep 2013 12:09:29 -0700 (PDT) Received: by 10.216.193.72 with HTTP; Tue, 17 Sep 2013 12:09:29 -0700 (PDT) In-Reply-To: References: Date: Tue, 17 Sep 2013 12:09:29 -0700 Message-ID: Subject: Re: Bloodhound installation issue(s)? From: Jared Duncan To: user@bloodhound.apache.org Content-Type: multipart/alternative; boundary=f46d0444e8ed6b301e04e6990f06 X-Virus-Checked: Checked by ClamAV on apache.org --f46d0444e8ed6b301e04e6990f06 Content-Type: text/plain; charset=UTF-8 > > I'm glad to see like all the functionality is in place Sorry, I have no idea how that extra "like" got in there. (I am not a valley girl, I swear!) I think I meant to say "that" or "how". On Tue, Sep 17, 2013 at 12:05 PM, Jared Duncan wrote: > Thanks Olemis. Things are quite a bit clearer now. The reason I had this > impression (that all permissions are global) was that I would choose > product A from the "Tickets" Dashboard and then click on "Admin" then > "Permissions" and then add a permission and then choose product B and then > go back to permissions and see if the one I added for product A was still > there and it was. I see now that there is a drop down at the very top to > switch between the different levels, which due to its isolated and distant > placement/location/position didn't scream to me it was related to the > particular page/section I was on/in. Seemed to be more a part of the > global nav to me. > > afaict , I'd never design (use) a multi-product system as complex as >> such approach you describe . Bloodhound MP architecture is aimed at >> encouraging sharing (when appropriate) and isolation (again when >> appropriate ;) > > > That's a great point and I agree, of course. The user flow in the UI in > general--when it comes to jumping between products--does seem a little > bumpy/disjointed to me given one can't globally select a product and then > just be "in that product", ie it's stored in the session, until he/she logs > out or switches to another product. I imagine that users switch between > admin/tickets/wiki for a particular product far more than they switch > between products -- I could be wrong, of course. Usage stats would > probably be pretty telling. > > I understand Bloodhound is very new though and so I'm glad to see like all > the functionality is in place and working pretty well; that's the important > part. Looks like everyone has worked really hard and done a great job. I > look forward to its continued adoption and improvement so that the odds of > it being accepted by other people climb higher every day. :) > > > On Tue, Sep 17, 2013 at 11:29 AM, Olemis Lang wrote: > >> On 9/17/13, Olemis Lang wrote: >> > On 9/17/13, Jared Duncan wrote: >> [...] >> >> i.e. if Joe >> >> has "ticket_admin" permission, he does so for all products under the >> >> project/environment/site. >> > >> > at least not by design ... if that happens , it's a bug . he fact fact >> > is that authenticated users are granted with a set of permissions >> > (including TICKET_ADMIN ;) immediately after it's created . >> > >> >> ... immediately after a new product is created ... >> >> [...] >> >> -- >> Regards, >> >> Olemis - @olemislc >> > > --f46d0444e8ed6b301e04e6990f06 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm glad to see like all the functionality is in pla= ce

Sorry, I have no idea how that extra "like" g= ot in there. =C2=A0(I am not a valley girl, I swear!) =C2=A0I think I meant= to say "that" or "how".=C2=A0


On Tue, Sep 17, 2013 at 12:05 PM, Jared = Duncan <j@jdunk.com> wrote:
Thanks Olemis. =C2=A0Things are quite a bit clearer now. = =C2=A0The reason I had this impression (that all permissions are global) wa= s that I would choose product A from the "Tickets" Dashboard and = then click on "Admin" then "Permissions" and then add a= permission and then choose product B and then go back to permissions and s= ee if the one I added for product A was still there and it was. =C2=A0I see= now that there is a drop down at the very top to switch between the differ= ent levels, which due to its isolated and distant placement/location/positi= on didn't scream to me it was related to the particular page/section I = was on/in. =C2=A0Seemed to be more a part of the global nav to me.

afaict , I'd never design (use) a multi-product system as c= omplex as
such approach y= ou describe . Bloodhound MP architecture is aimed at
encouraging sharing (when appropriate) and isola= tion (again when
appropriate ;)<= /span>

That's a great point and I= agree, of course. =C2=A0The user flow in the UI in general--when it comes = to jumping between products--does seem a little bumpy/disjointed to me give= n one can't globally select a product and then just be "in that pr= oduct", ie it's stored in the session, until he/she logs out or sw= itches to another product. =C2=A0I imagine that users switch between admin/= tickets/wiki for a particular product far more than they switch between pro= ducts -- I could be wrong, of course. =C2=A0Usage stats would probably be p= retty telling.

I understand Bloodhound is very new though and so I'= ;m glad to see like all the functionality is in place and working pretty we= ll; that's the important part. =C2=A0Looks like everyone has worked rea= lly hard and done a great job. =C2=A0I look forward to its continued adopti= on and improvement so that the odds of it being accepted by other people cl= imb higher every day. =C2=A0:)

On Tue, Sep 17, 2013 at 11:29 AM, Olemis L= ang <olemis@gmail.com> wrote:
On 9/17/13, Olemis Lang <olemis@gmail.com> wrote:<= br> > On 9/17/13, Jared Duncan <j@jdunk.com> wrote:
[...]
>> i.e. if Joe
>> has "ticket_admin" permission, he does so for all produc= ts under the
>> project/environment/site.
>
> at least not by design ... if that happens , it's a bug . he fact = fact
> is that authenticated users are granted with a set of permissions
> (including TICKET_ADMIN ;) immediately after it's created .
>

... immediately after a new product is created ...

[...]

--
Regards,

Olemis - @olemislc


--f46d0444e8ed6b301e04e6990f06--